Community
OpenEnergyMonitor

OpenEnergyMonitor Community

New installation of EmonCMS - no inputs from EmonTX on EmonPi

Hi,
Several months ago we had a powercut and my EmonPi failed to boot after the power came back. This is the second time this happened. I decided to buy a new SD card, install a fresh installation of EmonCMS (Version: low-write 10.8.5), and put the emonPi onto a UPS. The 5V power supply is on the UPS while the AC voltage measuring thingamy is in a conventional plug socket.
After the EmonPi booted up, all seems to be ok, but I’m not getting any data from my EmonTx.

Any ideas of how to fix this?

This is rather puzzling. The a.c. adapter doesn’t supply any power at all to the emonPi, I find it hard to believe that is the source of the problem.

What sort of UPS is it? Does it include filtering as well? My colleague @borpin usually advises, based on his experience, a mains conditioner/filter in preference to or as well as a UPS.

There are generally two types of UPS - one that runs the equipment off the mains and takes over when the power fails, the other is one that runs the equipment off an inverter (if mains output) or powered directly by the battery, and the battery is kept charged by the mains. The distinction is the former will allow disturbances through, while the latter is more likely to provide a ‘clean’ supply.

To your immediate problem - I doubt I can help because my knowledge of the internal workings of the emonPi is limited. What I would check is, can you see anything in the emonHub log from the emonTx? Is there absolutely nothing from it, or are there messages being rejected? Is the emonPi itself recording data, do emonHub and emonCMS appear to be running properly - there is data from Node 5 and it’s appearing on the Inputs page?

Thanks for your reply Robert.
The UPS is a Cyberpower BR700ELCD. As far as I can tell it is of the first type you mentioned, i.e. it runs the equipment off the mains directly and switches over to battery (within 4ms) if the main power fails.
It has ‘surge protection’ and overload protection (circuit breaker and internal current limiting) but I’m not that it has any conditioning or filtering.

Looking at the emonhub log It doesn’t look like there is anything coming in from the emonTX. I’ll post the log file if it helps.

Is node 5 the data coming in from sensors attached directly to the emonPi? If so, then yes it is recieving and logging data from CT clamps directly plugged into the emonPi.

2021-11-15 15:17:03,818 DEBUG    RFM2Pi     317055 Timestamp : 1636989423.815020
2021-11-15 15:17:03,818 DEBUG    RFM2Pi     317055 From Node : 5
2021-11-15 15:17:03,819 DEBUG    RFM2Pi     317055    Values : [3931, 0, 3931, 235.82, 0, 0, 0, 0, 0, 0, 0]
2021-11-15 15:17:03,820 DEBUG    RFM2Pi     317055 Sent to channel(start)' : ToEmonCMS
2021-11-15 15:17:03,820 DEBUG    RFM2Pi     317055 Sent to channel(end)' : ToEmonCMS
2021-11-15 15:17:03,935 DEBUG    RFM2Pi     317056 NEW FRAME : OK 15 251 19 85 85 74 53 113 83 67 85 85 85 85 85 206 36 85 85 141 86 85 85 85 85 85 85 85 85 85 85 101 32 101 32 101 32 101 32 101 32 101 32 0 56 85 85 (-61)
2021-11-15 15:17:03,937 WARNING  RFM2Pi     317056 RX data length: 46 is not valid for datacodes ['L', 'h', 'h', 'h', 'h', 'h', 'l', 'l', 'l', 'l', 'h', 'h', 'h', 'L']
2021-11-15 15:17:03,943 DEBUG    MQTT       Publishing: emon/emonpi/power1 3931
2021-11-15 15:17:03,944 DEBUG    MQTT       Publishing: emon/emonpi/power2 0
2021-11-15 15:17:03,946 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3931
2021-11-15 15:17:03,947 DEBUG    MQTT       Publishing: emon/emonpi/vrms 235.82
2021-11-15 15:17:03,948 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2021-11-15 15:17:03,950 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2021-11-15 15:17:03,951 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2021-11-15 15:17:03,952 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2021-11-15 15:17:03,953 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2021-11-15 15:17:03,955 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2021-11-15 15:17:03,956 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2021-11-15 15:17:03,958 INFO     MQTT       Publishing 'node' formatted msg
2021-11-15 15:17:03,959 DEBUG    MQTT       Publishing: emonhub/rx/5/values 3931,0,3931,235.82,0,0,0,0,0,0,0
2021-11-15 15:17:08,818 DEBUG    RFM2Pi     317057 NEW FRAME : OK 5 38 15 255 255 37 15 91 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2021-11-15 15:17:08,820 DEBUG    RFM2Pi     317057 Timestamp : 1636989428.818140
2021-11-15 15:17:08,821 DEBUG    RFM2Pi     317057 From Node : 5
2021-11-15 15:17:08,822 DEBUG    RFM2Pi     317057    Values : [3878, -1, 3877, 236.43, 0, 0, 0, 0, 0, 0, 0]
2021-11-15 15:17:08,822 DEBUG    RFM2Pi     317057 Sent to channel(start)' : ToEmonCMS
2021-11-15 15:17:08,823 DEBUG    RFM2Pi     317057 Sent to channel(end)' : ToEmonCMS
2021-11-15 15:17:09,015 DEBUG    MQTT       Publishing: emon/emonpi/power1 3878
2021-11-15 15:17:09,017 DEBUG    MQTT       Publishing: emon/emonpi/power2 -1
2021-11-15 15:17:09,018 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3877
2021-11-15 15:17:09,019 DEBUG    MQTT       Publishing: emon/emonpi/vrms 236.43
2021-11-15 15:17:09,021 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2021-11-15 15:17:09,022 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2021-11-15 15:17:09,023 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2021-11-15 15:17:09,025 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2021-11-15 15:17:09,026 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2021-11-15 15:17:09,027 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2021-11-15 15:17:09,029 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2021-11-15 15:17:09,030 INFO     MQTT       Publishing 'node' formatted msg
2021-11-15 15:17:09,031 DEBUG    MQTT       Publishing: emonhub/rx/5/values 3878,-1,3877,236.43,0,0,0,0,0,0,0
2021-11-15 15:17:11,892 DEBUG    emoncmsorg Buffer size: 6
2021-11-15 15:17:13,851 DEBUG    RFM2Pi     317058 NEW FRAME : OK 5 11 15 255 255 10 15 57 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)

Yes there is. Your Mk1 eye missed it. My Mk2 (the difference - it knows what to look for) spotted this.

That tells me that the entry in emonhub.conf doesn’t match the data coming from Node 15, which is an emonTx (unless you changed it). Luckily, I remembered you changed the sketch in your emonTx Missing temperature feeds on emonTX and emonCMS setup - #14 by Robert.Wall

What’s happened is your custom emonhub.conf has been overwritten by the standard one, and the change you did has been lost. Reapply that change, and it should work.

Brilliant, thanks once again Robert.
Thats solved it. The feeds have come to back to life.