emonTX reporting odd values in emonCMS

Emoncms
21

Confirmed. I have done a “Full update” from 11.3.22 and the pushbutton was working, now it is not. (Not even turns the backlight on.)
Emonhub will not start: shows “emonhub: Inactive loaded inactive dead”, however the Serial Monitor shows data from the front end being received.
Obviously, it’s not possible to do a shutdown with the pushbutton. I resorted to Remmina.

Emonhub started on power-up.

On investigation:
Start the Serial Monitor at 115200 baud on the Serial Monitor page, don’t stop emonHub. The display lights and shows “Booting…” Serial data appears.
Issue the command ‘l’ and the appropriate display appears, with normal front-end output interleaved as expected.
Issue the command “c1” The backlight turned on and showed the correct display,
Issue the command “c0” The backlight turned off promptly and the display returned to “WiFi: YES etc” although almost impossible to read without the backlight.

Stop the Serial Monitor, start emonHub via the Serial Monitor page. Admin System Information shows it started, but the emonHub log is showing no updates. neither is the Inputs page.
Emonhub starts from the Admin System Information page.

@TrystanLea It looks as if other things have got tangled in this area. It’s not just the pushbutton.

22

I don’t know if this is directly relevant, but …

I am just trying out a new emonTx4, with one 50A CT on input 2, no emonVs, no temperature sensors.

From the serial port:

emonTx V4 CM Continuous Monitoring V1.5.7
OpenEnergyMonitor.org
No EEPROM config
Settings:
Band 433 MHz, Group 210, Node 17, 7 dBm
Calibration:
vCal = 807.86
assumedV = 240.00
i1Cal = 300.30
i1Lead = 3.20
i2Cal = 150.15
i2Lead = 3.20
i3Cal = 150.15
i3Lead = 3.20
i4Cal = 60.06
i4Lead = 3.20
i5Cal = 60.06
i5Lead = 3.20
i6Cal = 60.06
i6Lead = 3.20
datalog = 9.80
pulses = 1
pulse period = 100
RF on
temp_enable = 1
JSON Format Off
RFM69CW  Freq: 433MHz Group: 210 Node: 17
RadioFormat: LowPowerLabs
Reference voltage calibration: 1.0256
Temperature Sensors found = 0 of 3
Temperature measurement is enabled.

No temperature sensors detected, disabling temperature
AC missing - Apparent Power calc enabled, assuming 240.00 V
MSG:1,Vrms:240.00,P1:432,P2:216,P3:217,P4:86,P5:87,P6:87,E1:0,E2:0,E3:0,E4:0,E5:0,E6:0,pulse:0
MSG:2,Vrms:240.00,P1:11,P2:5,P3:5,P4:2,P5:3,P6:2,E1:0,E2:0,E3:0,E4:0,E5:0,E6:0,pulse:0
MSG:3,Vrms:240.00,P1:11,P2:5,P3:5,P4:2,P5:2,P6:2,E1:0,E2:0,E3:0,E4:0,E5:0,E6:0,pulse:0

I am receiving the data on a home built emonBase (old RFM69Pi version), emonCMS Version
low-write 11.4.1. I am getting odd results for temperature. As I don’t have any temperature sensors attached, I believe that I should get the error value of 300 for T1, T2 and T3. Instead I get 300, 30000, 30000, even though I have the 0.01 multiplier in emonHub for all three temperatures.
emonHub config (taken from emonTx4.ino V1.5.7) is

[[17]]
  nodename = emonTx4_17
  [[[rx]]]
    names = MSG, Vrms, P1, P2, P3, P4, P5, P6, E1, E2, E3, E4, E5, E6, T1, T2, T3, pulse
    datacodes = L,h,h,h,h,h,h,h,l,l,l,l,l,l,h,h,h,L
    scales = 1,0.01,1,1,1,1,1,1,1,1,1,1,0.01,0.01,0.01,1
    units = n,V,W,W,W,W,W,W,Wh,Wh,Wh,Wh,Wh,Wh,C,C,C,p

Here is a relevant section of the emonHub log

2023-12-08 15:41:15,777 DEBUG    RFM69Pi    1230 NEW FRAME : OK 17 241 0 0 0 192 93 11 0 5 0 6 0 2 0 2 0 2 0 7 0 0 0 3 0 0 0 3 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 48 117 48 117 48 117 0 0 0 0 (-72)
2023-12-08 15:41:15,781 DEBUG    RFM69Pi    1230 Timestamp : 1702050075.777298
2023-12-08 15:41:15,782 DEBUG    RFM69Pi    1230 From Node : 17
2023-12-08 15:41:15,782 DEBUG    RFM69Pi    1230    Values : [241, 240, 11, 5, 6, 2, 2, 2, 7, 3, 3, 1, 0.01, 0.01, 300, 30000, 30000, 0, 0, 0.0]
2023-12-08 15:41:15,783 DEBUG    RFM69Pi    1230      RSSI : -72
2023-12-08 15:41:15,784 DEBUG    RFM69Pi    1230 Sent to channel(start)' : ToEmonCMS
2023-12-08 15:41:15,784 DEBUG    RFM69Pi    1230 Sent to channel(end)' : ToEmonCMS
2023-12-08 15:41:15,882 DEBUG    MQTT       Publishing: emon/emonTx4_17/MSG 241
2023-12-08 15:41:15,884 DEBUG    MQTT       Publishing: emon/emonTx4_17/Vrms 240
2023-12-08 15:41:15,885 DEBUG    MQTT       Publishing: emon/emonTx4_17/P1 11
2023-12-08 15:41:15,886 DEBUG    MQTT       Publishing: emon/emonTx4_17/P2 5
2023-12-08 15:41:15,888 DEBUG    MQTT       Publishing: emon/emonTx4_17/P3 6
2023-12-08 15:41:15,889 DEBUG    MQTT       Publishing: emon/emonTx4_17/P4 2
2023-12-08 15:41:15,891 DEBUG    MQTT       Publishing: emon/emonTx4_17/P5 2
2023-12-08 15:41:15,892 DEBUG    MQTT       Publishing: emon/emonTx4_17/P6 2
2023-12-08 15:41:15,893 DEBUG    MQTT       Publishing: emon/emonTx4_17/E1 7
2023-12-08 15:41:15,894 DEBUG    MQTT       Publishing: emon/emonTx4_17/E2 3
2023-12-08 15:41:15,895 DEBUG    MQTT       Publishing: emon/emonTx4_17/E3 3
2023-12-08 15:41:15,897 DEBUG    MQTT       Publishing: emon/emonTx4_17/E4 1
2023-12-08 15:41:15,898 DEBUG    MQTT       Publishing: emon/emonTx4_17/E5 0.01
2023-12-08 15:41:15,899 DEBUG    MQTT       Publishing: emon/emonTx4_17/E6 0.01
2023-12-08 15:41:15,900 DEBUG    MQTT       Publishing: emon/emonTx4_17/T1 300
2023-12-08 15:41:15,902 DEBUG    MQTT       Publishing: emon/emonTx4_17/T2 30000
2023-12-08 15:41:15,903 DEBUG    MQTT       Publishing: emon/emonTx4_17/T3 30000
2023-12-08 15:41:15,904 DEBUG    MQTT       Publishing: emon/emonTx4_17/pulse 0
2023-12-08 15:41:15,905 DEBUG    MQTT       Publishing: emon/emonTx4_17/missed 0
2023-12-08 15:41:15,906 DEBUG    MQTT       Publishing: emon/emonTx4_17/missedprc 0.0
2023-12-08 15:41:15,908 DEBUG    MQTT       Publishing: emon/emonTx4_17/rssi -72
2023-12-08 15:41:15,909 INFO     MQTT       Publishing 'node' formatted msg
2023-12-08 15:41:15,909 DEBUG    MQTT       Publishing: emonhub/rx/17/values 241,240,11,5,6,2,2,2,7,3,3,1,0.01,0.01,300,30000,30000,0,0,0.0,-72

This shows the three temperature data all being received as two hex bytes of 48 117 which translates to 117*256+48=30000. However, the first is published as 300, but the second and third are published as 30000?

@TrystanLea Any thoughts?

23

Apologies. looks like I made a mistake in enabling a pull up resistor (the script should have been identical to the original). I’ve pushed up a fix, the script is now identical to the original.

24

I have fixed the temperature problem that I had. :blush:

The emonHub config that I copied from the github emonTx4.ino V1.5.7 is not correct.

The “scales” line has a run of ten “1’s”, whereas it should be twelve, to cover the six powers and 6 energies.

Sorry for the disturbance!

25

Just one thing, enabling JSON in emonhub would be a good idea so the data gets sent as a single topic. It is possible to overload the incoming mqtt PHP process if you send too many and theoretically possible that some data could end up in a different timeseries window as well for the same set of readings. @TrystanLea - might be better as the default.