fixed emailer function to support swiftmailer v5.4.8 and different installation location
improved error reporting on password reset
improved feed unit filter to allow special chars, thanks @emrys
updated Italian language files, thanks @gablau
Virtual feed user identification fix for public dashboards (Needs further review).
Disable logging of invalid apikeys, thanks @MyForest
Fix to issue with empty values in vis/realtime, thanks @emrys
urlencode referer parameter user for user/login, thanks @emrys
*BREAKING CHANGE: The new MQTT topic filter provides better support for a larger variety of topic formats but it can result in broken inputs which will need re-mapping. See Emoncms v10.2.1 New MQTT Topic Filter Issue - #8 by borpin.
I noticed a bug in the Sync module upload function that I’ve now fixed. I’ve also added a ‘Download All’ and ‘Upload All’ button to make this easier. I’ve merged this feature into stable and tagged v2.0.5.
I use the Sync module to backup the feeds on my home pi to an instance of emoncms running on my Ubuntu laptop. Using the upload feature to do this from the pi means I don’t have to have any emoncms services running on my main computer, it just needs to be a basic emoncms installation.
What’s the easiest way to manually update - I’m running on a Debian PC and get this message after clicking the update button
Starting update via service-runner-update.sh (v3.0) ><br />
- emonSD version: emonSD-15Jan2018<br />
emonSD-17Jun2015<br />
ERROR: emonSD base image old or undefined...update will not continue<br />
See latest verson: https://github.com/openenergymonitor/emonpi/wiki/emonSD-pre-built-SD-card-Download-&-Change-Log<br />
Stopping update</details><br />
I think that might be unlikely, that would raise a question over where the 2 image dates of emonSD-15Jan2018 and emonSD-17Jun2015 come from in the error message.
I suspect the version file may have been corrupted or edit to facilitate a previous update and perhaps there are 2 images listed in the file, hence the content doesn’t match any single date and doesn’t proceed.
I don’t doubt that, but where would a date of 2015 spring up from on a install created via a script born in 2019? Maybe it isn’t an emonScript install?
Where is the version kept on a Debian based “emonScript” install? Is it still a emonSDxxxx? Why isn’t it kept in the boot dir for consistency?
and from memory I had quite a game trying to get the backup script to do a restore so I likely had to create at least one of them for that. In this case should I delete them both? Whats the route it takes to do an update? Its late here so I’ll get onto it tomorrow
Deleting both emonSD files allowed the update to work. Thanks for your help.
By way of a little background this was a V9 system that was migrated from a Pi some time ago. When moving to V10 I backed up and deleted everything to do with emoncms, then updated the OS before installing, emoncms V10, then manually restoring as the restore function didn’t work on my system. The emonSD files must have remained from the original Pi and inside one of them I’d left a comment about it being needed to enable backup to work.
.