Be aware that you might run into problems if you update your emonPi.
As @pb66 wrote about the sketch in the Atmel328P (the ‘emon’ part):
If you use the “update RFM69Pi” button rather than the “update emonPi” button it will update in exactly more or less 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.
See Update EmonPi Button or Update EmonBase Button? for more info.