I will be upgrading the emoncms.org server’s at around 4pm UK time today. All being well the process should not take too long.
The user interface will be in read-only mode during this period, it will still be possible to login, view feeds, graphs, dashboards and apps but it wont be possible to change configuration such as adding or changing input processing configurations and adding new feeds.
Data posted from devices will be stored in temporary queues to avoid data loss. You may notice the last updated time increase but there’s no need to check your device, the data will still be being received by the server, it will just be that queue processing has been paused.
I will update this thread as the upgrade progresses.
Note: the server IP address has now changed from 109.169.55.159 to 78.129.241.20. It looks like 96% of devices posting to emoncms.org have automatically transferred to the new IP address but there are as has always been the case in the past some stragglers..
emoncms_sync: I’ve had to restart the emoncms_sync process on two emonPi systems that I’ve checked, there seems to be an issue there. A quick restart seems to fix.
A couple of users have highlighted dashboard charset issues. I should have a solution for these tomorrow. If anyone finds charset issues elsewhere outside of dashboards please let me know.
@TrystanLea Trystan - Following the update I’m getting an error when I try and load the solar app - screen shot below. When I close the error box, the app still doesn’t load - it just shows the rotating loading symbol.
We’ve got one ongoing known issue with data not being received from users using solar/battery software http://www.multisibcontrol.net/ to upload data to emoncms.org. If anyone using this software can provide any debug info that would be very useful, I’ve emailed the software authors.
There was also an issue that’s now been fixed with inputs that had a leading white space before input names, due to the way the custom json decoder in emoncms was handling white spaces in the json data. Emoncms.org now trims these white spaces and existing inputs have been fixed to match this change.
The implications of that change however will cause duplicate inputs where inputs had a leading white space previously. This is likely the main reason for a lot of the duplicate input issues we’ve had over the years as data is passed to emoncms sometimes with and sometimes without leading white spaces.
The easiest solution in the mean time to get around it is to post data using parameter fulljson= rather than data= or json=.
I’ve lost some data since this change. My emoncms has some inputs from MQTT (this is an ESPAltherma running on an m5stack). These feeds have not updated since the change. I’ve restarted both systems but the feeds aren’t updating.
Hello @scanfer , did you set the SSL fingerprint manually on the ESPAltherma?. @boydo just reminded me of this as it’s affected a couple of his devices. I’m looking into it.
Full switch over to new upgraded server complete!
User interface write access enabled again.
