OK I understand it now, re sitting and cleaning didn’t solved it.
Unfortunately, that part, I don’t know. 
I’ve had a look at the shop, looks like the emonbase was ordered in September, 2016.
1 Like
Thanks @emontxv3, could you try uploading the firmware to the RFM69Pi again from the Emoncms admin interface, select the RFM69Pi firmware and then click “Update Firmware”
1 Like
YES, GREAT.
All is working again.
Even the backup is accepted and the history is restored.
Thank you very much to all.
1 Like
Great to hear!
1 Like
I had a similar issue today on my emonPi - all feeds stopped around 17:35 from the emonPi and 2 emonTH.
Looking at emonhub.log after a reboot, I saw that communication with /dev/ttyAMA0 was not ok:
2020-09-11 19:38:24,631 INFO MainThread Creating EmonHubJeeInterfacer 'RFM2Pi'
2020-09-11 19:38:24,633 DEBUG MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2020-09-11 19:38:26,636 WARNING MainThread Device communication error - check settings
2020-09-11 19:38:26,637 INFO MainThread Setting RFM2Pi baseid: 5 (5i)
2020-09-11 19:38:28,866 INFO MainThread EmonHub emonHub (emon-pi variant) v2.1.5
2020-09-11 19:38:28,867 INFO MainThread Opening hub...
2020-09-11 19:38:28,867 INFO MainThread Logging level set to DEBUG
2020-09-11 19:38:28,868 INFO MainThread Creating EmonHubJeeInterfacer 'RFM2Pi'
2020-09-11 19:38:28,871 DEBUG MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2020-09-11 19:38:30,874 WARNING MainThread Device communication error - check settings
2020-09-11 19:38:30,874 INFO MainThread Setting RFM2Pi baseid: 5 (5i)
2020-09-11 19:38:31,876 INFO MainThread Setting RFM2Pi frequency: 433 (4b)
2020-09-11 19:38:32,878 INFO MainThread Setting RFM2Pi group: 210 (210g)
2020-09-11 19:38:33,880 INFO MainThread Setting RFM2Pi quiet: 1 (1q)
2020-09-11 19:38:34,882 INFO MainThread Setting RFM2Pi calibration: 230V (1p)
Got it back to a working state by doing a UPDATE FIRMWARE ONLY from the Admin page, selecting ttyAMA0 and EmonPi.
Here is the update log:
Starting update via service-runner-update.sh (v3.0) >
- emonSD version: emonSD-17Oct19
- supported images: emonSD-24Jul20 emonSD-02Oct19 emonSD-17Oct19
- emonSD base image check passed...continue update
git pull /opt/openenergymonitor/EmonScripts
master
* stable
On branch stable
Your branch is up to date with 'origin/stable'.
nothing to commit, working tree clean
Already up to date.
-------------------------------------------------------------
Main Update Script
-------------------------------------------------------------
Date: Fri 11 Sep 20:23:05 EEST 2020
EUID: 1000
openenergymonitor_dir: /opt/openenergymonitor
type: firmware
firmware: emonpi
Hardware detected: EmonPi
Stopping emonPiLCD service
Display update message on LCD
-------------------------------------------------------------
EmonPi Firmware Update (Discrete Sampling)
-------------------------------------------------------------
Start ATmega328 serial upload using avrdude with latest.hex
Attempt: 1
avrdude -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 115200 -U flash:w:/opt/openenergymonitor/emonpi/firmware/compiled/latest.hex
Note: progress written to logfile /var/log/emoncms/firmware.log
avrdude-original: Using autoreset DTR on GPIO Pin 7
strace: |autoreset: Broken pipe
ERROR: Not in sync
Attempt: 2
avrdude -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 115200 -U flash:w:/opt/openenergymonitor/emonpi/firmware/compiled/latest.hex
Note: progress written to logfile /var/log/emoncms/firmware.log
avrdude-original: Using autoreset DTR on GPIO Pin 7
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
strace: |autoreset: Broken pipe
avrdude-original: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
avrdude-original: Device signature = 0x1e950f (probably m328p)
avrdude-original: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude-original: erasing chip
avrdude-original: reading input file "/opt/openenergymonitor/emonpi/firmware/compiled/latest.hex"
avrdude-original: input file /opt/openenergymonitor/emonpi/firmware/compiled/latest.hex auto detected as Intel Hex
avrdude-original: writing flash (18526 bytes):
Writing | ################################################## | 100% 2.63s
avrdude-original: 18526 bytes of flash written
avrdude-original: verifying flash memory against /opt/openenergymonitor/emonpi/firmware/compiled/latest.hex:
avrdude-original: load data flash data from input file /opt/openenergymonitor/emonpi/firmware/compiled/latest.hex:
avrdude-original: input file /opt/openenergymonitor/emonpi/firmware/compiled/latest.hex auto detected as Intel Hex
avrdude-original: input file /opt/openenergymonitor/emonpi/firmware/compiled/latest.hex contains 18526 bytes
avrdude-original: reading on-chip flash data:
Reading | ################################################## | 100% 1.98s
avrdude-original: verifying ...
avrdude-original: 18526 bytes of flash verified
avrdude-original done. Thank you.
SUCCESS: flash verifed
waiting for emonpi to stop controlling LCD
Starting emonPi LCD service..
-------------------------------------------------------------
emonPi update done: Fri 11 Sep 20:23:23 EEST 2020
-------------------------------------------------------------
I was wondering if there is an explanation for this issue. In my case it just happened. I didn’t reflash the SD card, didn’t do any upgrades or anything else hours before it happened.