Iām currently moving towards a test of the DietPi solution because it allows me to work with the hardware I have at hand. Getting a new Pi is not so much an issue of cost as one of need and a commitment to not throwing away something simply because itās a little old. The original Pi 1 Model B has more than enough processing power to manage a house (if we could put a man on the moon with less processing power than a modern phone, I feel I ought to be able to turn on and off a few switches and track the power consumption with an SBC running at 700MHz.
Since power consumption tracking is a relatively small part of my usage, Iām probably now going to drop a local EmonCMS installation in favour of storing the data in some other system using MQTT. Prior to the crash which took out my old SD card about 1 year ago, my original installation of EmonCMS based on a vanilla install of the EmonSD, had run for about 12 months with no unplanned downtime. Sadly for most of that time it had just been logging temperature data and not electricity so it was somewhat pointless!
Edit to add: Having pulled the Flash drive that was running the OS I can confirm that it was the May16 release of EmonSD and that it worked flawlessly on the Pi1.
Thatās good to hear. If you just want to run emonHub and not a local version of Emoncms then maybe DietPi could be a good solution. Iāve split out the DietPi discussion to a new topic.
I just installed this image to work with my own custom version of the emonBase (some pins swapped, some features added/removed). Nice work!
One thing I noticed though is that there is an automatic firmware flasher. I donāt want my firmware flashed because emonPiās firmware is not compatible with my custom board. Is there a way to stop the automatic updates from happening in the future?
I upgraded my emoncms to version 9.9.4 successfully with emonSD-26Oct17 image on my emonPi. Iām now wondering if it is possible to migrate to the emonSD-30Oct18 image directly from my computer through my wifi network, or if it is necessary to open the case of my emonPi to flash the SDcard with Etcher.
Thank you for the is list - I need to run through this listā¦
āFirst update the existing setup to 9.9.4.ā - I have Version low-write 9.8.31 | 2018.06.21 - so I need to update. Should I use āemonpi Updateā or āemonBase Updateā button? Iām not clear what each does this instance. Alternative I could ssh and then a ā.shā?
Similarly the line āUpdate EmonCMS system (image is not on latest).ā - does that also use āemonpi Updateā or āemonBase Updateā button? etcā¦
Updating emonPi sketch:
If you do want to change the firmware, itās best to compile the Arduino sketch on your PC then transfer the .hex to the emonPi and upload directly from the RaspberryPi using avrdude. Emonhub will need to be stopped to free up the serial port. See example script to upload .hex emonpi/update at master Ā· openenergymonitor/emonpi Ā· GitHub
Not updating the emonPi sketch: EmonPi AC-AC input - #13 by pb66
āIf you use the āupdate RFM69Piā button rather than the āupdate emonPiā button it will update in exactly the same way but when it tries to upload the firmware at the wrong upload baud it will fail and the existing firmware will remain intact. This works as the 16MHz emonPi has a different bootloader to all the 8MHz RFM2Pi type devices.ā
If you have an emonPi with a totally stock sketch you are best using āupdate emonpiā to keep up to date.
If you have an emonPi with a modified sketch you are best using āupdate emonbaseā to avoid overwriting.
If you have an emonBase and you know your RFM2Pi or RFM69Pi is rfm69 based and has a totally stock sketch you are best using āupdate emonBaseā to keep it updated
If you have an emonBase with a rfm69 based RFM2Pi or RFM69Pi running a modified sketch OR if you have a rfm12 based RFM2Pi OR you are unsure what RFM2Pi you have you should use āupdate emonpiā to avoid over-writing the firmware.
Aside from the firmware differences, there is no difference, both buttons fully update the emonSD used in both the emonPi and emonBases. There is no emonHub update button, emonhub is updated along with emoncms and other softwares in that same emonSD update.
This was discussed in great length already, and thereās a link to the discussion in Glynās first post in this thread. Have a read through that discussion - the argument has already been lost
Iāve not been able to revive a couple of inputs - i.e. those from Robinās Mk2 pv diverter. The standard emontx and emonth nodes have been picked up and are updating, but not these additional ones. The imported backup file has these nodes (basically node ā12ā and ā13ā) listed in inputs, but null values. The log file shows an error:
2018-11-14 00:44:16.296|ERROR|phpmqtt_input.php|ErrorException: Undefined index: nodeid in /var/www/emoncms/Modules/input/input_model.php:206
but Iām on the edge of my knowledge hereā¦do I need to edit the script on the diverter (which I presume is still transmitting the data with the same format) or do I need to try and find these nodes in the php script?
I think that error just means that the firmware upload tool could not connect to the emonpi board, did you share the details of your system? Is it an emonpi?
Thatās nothing to worry about. The FW updated successfully this strace error happens when avrdude finishes. Itās due to our modified avrdude with āauto resetā to auto toggle a GPIO pin on a RasPi to reset the AVR controller.:
I did try and track this message down in the past but didnāt manage to fix it. Agree it would be best if the error wasnāt there! But nothing to worry about.