After updating both of my flukso devices I been having issues with them...
They are reporting data just fine (at least it seems too) but when I login to the interface I keep seen:
"synchronize with flukso server failed" Make sure the FLM is connected to the internet before saving the sensors.
"The last synchronization was on Wed, Dec, 31st 1969"
"Serial: unknown"
This is on both of them...
Any ideas what is going on?
TIA.
There is a fix for this that several others have used https://www.flukso.net/content/webui-errors-after-upgrade
However Icarus75 has asked that if someone experiences this fault that they leave the FLM in it's current state so that he is able to diagnose the root cause remotely.
If your FLM's are still reporting data to Flukso and you can wait a while then i am sure Icarus75 would appreciate the chance to get some additional information on this upgrade issue.
I indeed would like to extract some more info from these FLMs. Could you let me know whether they are still in this state?
Icarus75,
They are still in this state both of them.
You have my consent to login and work with them.
Thank you.
Just finished the remote debugging of your FLM's. Here's my feedback:
1/ When booting for the first time with the new firmware, the FLM will flash the sensor board and then 'synchronise' the sensor settings to the sensor board. This automatically triggers a sync with the Flukso server as well. A sync error will occur when the wifi link is not yet up-and-running when this action takes place. Hence the 'synchronisation with Flukso server failed' error message. Since all sensor settings were already synced before, this causes no operational issues.
2/ If your FLM has a serial in the FL02xxxxxx range, the serial number will not have been burned into the flash at production time. It is therefore impossible for the firmware to obtain its serial number from flash. All FL02xxxxxx with display an 'unknown' serial on the settings page. The serial number is only used for logistics purposes. The Flukso platform does not work with it. So again, no operational impact.
@ffuentes Thanks for letting me perform some remote debugging. While I was at it, I've issued a manual sync to get rid of the error message.