I currently have 232 - is this the latest? Is there a change log for a new version and how do I upgrade please? I tried searching the forum but could only find release notes for 232 in 2013?
Actually there is no "official" firmware than v232; we had some beta testing on v244 and v245 and desperately await the official v24x - this was "promised" already some time ago, but seems to no yet have reached public availability...
Hopefully Bart stays with the habit to not change too many things at the same time.
An official r24x is just around the corner. If you would like to have your FLM upgraded to the latest beta, i.e. r245, just reply to this forum thread.
vk2him |
Yes please, can I get the update? Thanks
icarus75 |
Your FLM should be running r245 within an hour from now.
voogt |
Please put me on the list for 2.4x firmware, running now 2.32 without problems..... but curios about the improvements.
thanxs
icarus75 |
@voogt Your FLM is scheduled for an upgrade as well.
adamcowin |
Yes please, can i also get the update :)
Thanks
Adam
vk2him |
Thanks Bart - I now have mqtt graph scripts working well
icarus75 |
@adamcowin Ditto
adamcowin |
Thanks Bart - Upgrade went through successfully and without any issues :)
bazzle |
Hi Bart
Please give mine a Go :)
Bazzle
gebhardm |
See https://www.flukso.net/blog - you can trigger the update to r247 yourself; there is no central intervention (needed).
"If you have a Fluksometer serial in the FL02xxxxxx or FL03xxxxxx range, you can now upgrade your FLM via a simple click on the settings (cogwheels in the top right corner) > devices page. The actual upgrade will take place on the next hourly FLM heartbeat. Make sure to keep your FLM humming during a scheduled upgrade."
bazzle |
I tried that the other day. There is no upgrade tab or settings
vk2him |
Bazzle - click the gear icon in the top right corner on this page - then click Devices ... you will then see Operations on the far right side and one option will be to update - click that.
bazzle |
All I see is ,remove upgrade,
mines at 232
vk2him |
Press Upgrade ...
vk2him |
Remove is one option and Upgrade in another option - there isn't one option called "REMOVE UPGRADE" if you follow ..
gebhardm |
So there is a dear forum participant who does not read the answers to an own thread:
It should have been utterly discussed there that this MAY be seen as an UI design flaw.
michi |
Well, not wanting to be argumentative, but I think it is indeed a UI design flaw. That's because there is no affordance (visual indication) that
remove upgrade
is actually two separate links. A two-word link "remove upgrade" would look exactly the same. The ambiguity arises because the words can be parsed as a single command "remove upgrade", or as two separate verbs "remove" and "upgrade". So, I don't think there can be any argument as to whether this is a UI design flaw. Removing the ambiguity is really simple by making the links buttons instead. That way, I'd see a single button "remove", or a single button "upgrade", or two buttons "remove" and "upgrade".
As to people not reading answers to their own threads, I shall remain silent ;-)
BTW, let's take this in the right spirit, please. I'm not pointing fingers at anyone. I've spent decades thinking about design flaws, and the places where they pop up can be most surprising (such as the one we've been discussing; when writing the code, it is totally non-obvious that the ambiguity can ever arise).
Every time I come across something like this, I learn something that I can apply elsewhere.
Brilliant, thank you! That definitely fixes it for good.
Cheers,
Michi.
bazzle |
Thanks Gebhardm for your cryptic repy,
Sadly I don't have time to be able to go back to ALL the posted items and follow them thru like you seem to do.
Work seems to get in the way.
A simple reply like.
They are 2 separate buttons .....would of been more helpful and would help others who "stumble" across this thread and are too afraid to post due to the condescending way you often seem to reply in other threads.
"Picard Out" :)
Any way I followed the link read the replies and NOW found out there are 2 buttons,
Fancy that,
Thanks all
Bazzle
JAANSSPUL |
My Flukse FL03001640 with v232, wil not update to v250.
I tried several tymes, but it returns back to v232.
Thanks Jaan
ksofluk |
I have a similar problem - wont upgrade from 247 to 250
B-Man |
i had the same issue bart fixed it by changing the script it was loading too fast or something
ksofluk |
Thanks. Do you have any pointers to further debug? Now it has been stuck at "250**" for the last two days on the flukso.net interface (indicating it will upgrade on the next heartbeat I believe). Locally it still reports that it is on 247.
Kuusamo |
Same issue version 247 to 250 got stuck ...
Now it has been stuck at "250**" for the last two days on the flukso.net interface (indicating it will upgrade on the next heartbeat I believe). Locally it still reports that it is on 247.
Manual reading MQTT works like a charme but no updates to dash ...
local Status all OK
( it's a secondhand so maybe reflash is a good option ??)
ksofluk |
In my case it was my own fault - I had disabled remote upgrades in the "services" tab :$
Enabling remote upgrades, and retriggering the upgrade worked flawlessly.
Sorry for the noise.
zmj |
Hi my last heartbeat was "11 Oct 2016 09:01:13". The unit is currently running firmware 216, I've selected upgrade on the devices tab/page. It reports "The FLM with serial FL03001763 will be upgraded to firmware version 250 at the next FLM heartbeat.", next heartbeat comes around and it stays resolutely on firmware 216.
Actually there is no "official" firmware than v232; we had some beta testing on v244 and v245 and desperately await the official v24x - this was "promised" already some time ago, but seems to no yet have reached public availability...
Hopefully Bart stays with the habit to not change too many things at the same time.
See also https://www.flukso.net/content/eta-244-firmware
An official r24x is just around the corner. If you would like to have your FLM upgraded to the latest beta, i.e. r245, just reply to this forum thread.
Yes please, can I get the update? Thanks
Your FLM should be running r245 within an hour from now.
Please put me on the list for 2.4x firmware, running now 2.32 without problems..... but curios about the improvements.
thanxs
@voogt Your FLM is scheduled for an upgrade as well.
Yes please, can i also get the update :)
Thanks
Adam
Thanks Bart - I now have mqtt graph scripts working well
@adamcowin Ditto
Thanks Bart - Upgrade went through successfully and without any issues :)
Hi Bart
Please give mine a Go :)
Bazzle
See https://www.flukso.net/blog - you can trigger the update to r247 yourself; there is no central intervention (needed).
"If you have a Fluksometer serial in the FL02xxxxxx or FL03xxxxxx range, you can now upgrade your FLM via a simple click on the settings (cogwheels in the top right corner) > devices page. The actual upgrade will take place on the next hourly FLM heartbeat. Make sure to keep your FLM humming during a scheduled upgrade."
I tried that the other day. There is no upgrade tab or settings
Bazzle - click the gear icon in the top right corner on this page - then click Devices ... you will then see Operations on the far right side and one option will be to update - click that.
All I see is ,remove upgrade,
mines at 232
Press Upgrade ...
Remove is one option and Upgrade in another option - there isn't one option called "REMOVE UPGRADE" if you follow ..
So there is a dear forum participant who does not read the answers to an own thread:
https://www.flukso.net/content/new-firmware-and-upgrade-descriptions-dum...
It should have been utterly discussed there that this MAY be seen as an UI design flaw.
Well, not wanting to be argumentative, but I think it is indeed a UI design flaw. That's because there is no affordance (visual indication) that
remove upgrade
is actually two separate links. A two-word link "remove upgrade" would look exactly the same. The ambiguity arises because the words can be parsed as a single command "remove upgrade", or as two separate verbs "remove" and "upgrade". So, I don't think there can be any argument as to whether this is a UI design flaw. Removing the ambiguity is really simple by making the links buttons instead. That way, I'd see a single button "remove", or a single button "upgrade", or two buttons "remove" and "upgrade".
As to people not reading answers to their own threads, I shall remain silent ;-)
BTW, let's take this in the right spirit, please. I'm not pointing fingers at anyone. I've spent decades thinking about design flaws, and the places where they pop up can be most surprising (such as the one we've been discussing; when writing the code, it is totally non-obvious that the ambiguity can ever arise).
Every time I come across something like this, I learn something that I can apply elsewhere.
Cheers,
Michi.
Ref to https://www.flukso.net/content/device-settings-better-visualize-device-o... and hopefully solved (has to be added to the drupal template on server side)
Brilliant, thank you! That definitely fixes it for good.
Cheers,
Michi.
Thanks Gebhardm for your cryptic repy,
Sadly I don't have time to be able to go back to ALL the posted items and follow them thru like you seem to do.
Work seems to get in the way.
A simple reply like.
They are 2 separate buttons .....would of been more helpful and would help others who "stumble" across this thread and are too afraid to post due to the condescending way you often seem to reply in other threads.
"Picard Out" :)
Any way I followed the link read the replies and NOW found out there are 2 buttons,
Fancy that,
Thanks all
Bazzle
My Flukse FL03001640 with v232, wil not update to v250.
I tried several tymes, but it returns back to v232.
Thanks Jaan
I have a similar problem - wont upgrade from 247 to 250
i had the same issue bart fixed it by changing the script it was loading too fast or something
Thanks. Do you have any pointers to further debug? Now it has been stuck at "250**" for the last two days on the flukso.net interface (indicating it will upgrade on the next heartbeat I believe). Locally it still reports that it is on 247.
Same issue version 247 to 250 got stuck ...
Now it has been stuck at "250**" for the last two days on the flukso.net interface (indicating it will upgrade on the next heartbeat I believe). Locally it still reports that it is on 247.
Manual reading MQTT works like a charme but no updates to dash ...
local Status all OK
@ www.flukso.net
Last hartbeat seen 2 days ago ?!
Is there a easy way to manualy install 250 ?
( it's a secondhand so maybe reflash is a good option ??)
In my case it was my own fault - I had disabled remote upgrades in the "services" tab :$
Enabling remote upgrades, and retriggering the upgrade worked flawlessly.
Sorry for the noise.
Hi my last heartbeat was "11 Oct 2016 09:01:13". The unit is currently running firmware 216, I've selected upgrade on the devices tab/page. It reports "The FLM with serial FL03001763 will be upgraded to firmware version 250 at the next FLM heartbeat.", next heartbeat comes around and it stays resolutely on firmware 216.
What step am I missing ?
Thanks