Tx4 data not being processed into Emoncms

I am running an EmonPi,… with a Tx4 ( 12 CTs )… and a couple of radio temp sensors…

All s/w is at latest… with new backup processes running…

I have just had to hard reset,. Power off/On… for the second time in a few days… Normally my system runs for Months without issue.

The problem I am seeing is that Tx4 data does not seem to be being processed.

I can go into the serial monitor,.. and observe the 10 second data updates being received,.. ( so not a connection problem IMHO ) However, if I go to my inputs or feeds data ( serial monitor restarted ), data is more than 15hrs old…

My Tx4 data is received via USB connection, ( Not radio ). The log file albeit small shows a couple of errors, but not sure if these are related.

Wireless data from my EV charger, seems to be processed,. but temperature and Humidity (x2) sensors seem to drop off recording.

Does anyone have any thoughts… on what the issue maybe…

Many tx

2026-09-14 07:03:08.469|WARN|emoncms_mqtt.php|Starting MQTT Input script
2026-09-14 07:03:08.527|WARN|emoncms_mqtt.php|Not connected, retrying connection
2026-09-14 07:03:08.538|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2026-09-14 07:06:10.455|WARN|emoncms_mqtt.php|Unable to unpack JSON, not recording mqtt_supported_protocols : ["mqtt","mqtts"]
2026-09-14 07:06:10.456|WARN|emoncms_mqtt.php|Unable to unpack JSON, not recording http_supported_protocols : ["http"]
2026-09-14 07:07:32.428|ERROR|index.php|Not Authenticated|admin/shutdown
2026-09-14 07:07:35.760|ERROR|index.php|Not Authenticated|admin/info
2026-09-14 07:07:41.941|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-14 21:16:03.982|ERROR|index.php|Not Authenticated|graph/3
2026-09-15 07:16:44.952|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-17 11:52:42.145|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-17 21:04:02.054|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-18 07:48:58.750|WARN|emoncms_mqtt.php|Starting MQTT Input script
2026-09-18 07:48:58.813|WARN|emoncms_mqtt.php|Not connected, retrying connection
2026-09-18 07:48:58.825|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2026-09-18 07:55:34.553|WARN|emoncms_mqtt.php|Unable to unpack JSON, not recording mqtt_supported_protocols : ["mqtt","mqtts"]
2026-09-18 07:55:34.554|WARN|emoncms_mqtt.php|Unable to unpack JSON, not recording http_supported_protocols : ["http"]
2026-09-18 07:58:13.230|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'

Well the gremlins are back,.. some 3 and a bit days later,.. my EmonTx4 stopped transmitting,.. AFAIK,…this time,.. there seems to be no Tx4 data packets being transmitted to the EmonPi2…

As far as I can see,. from the serial logging,.. a soft reboot,.. changes nothing,.. still no data received,..

So in an attempt to resolve long term,.. removed EmonPi,… cleaned connections between boards, ( as well as removing interconnect extension ) with some WD40,… and reassembled.

Plugged back in,.. normal service has been resumed,.. we will see if this is a long term fix.

My saving grace here is my Home Assistant script,.. which emails me should reading fail,.. or repeat,… Included below should anyone be interested.

alias: 'Alert: Electricity Feed Stopped'
description: ''
triggers:
  - hours: /1
    trigger: time_pattern
conditions:
  - condition: template
    value_template: |
      {{
        (as_timestamp(now()) -
        as_timestamp(states.sensor.energy_emonpi_hse_power_kwh.last_changed))
        > 7200
      }}
actions:
  - action: smtp.send_message
    metadata: {}
    target:
      device_id: 280a29fc349f16878f304e1ab311
    data:
      title: Home Assistant
      message: EmonPi  Power Data Missing
  - action: notify.mobile_app_sm_s948b
    metadata: {}
    data:
      message: EmonPi  Power Data Missing
      title: EmonPi  Power Data Missing
  - action: notify.persistent_notification
    metadata: {}
    data:
      message: EmonPi  Power Data Missing
mode: single

I don’t know if this is an issue, or whether it means something… but my emoncms log file contains the following,… and I am still getting some warnings,.. as well as authentication errors, even after hard reset etc.

And for info:,.. none of my filesystems are full, ( root @ 48% )

Many Tx

2026-09-20 16:12:52.122|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-21 16:36:45.685|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 07:04:34.073|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 07:06:53.320|WARN|emoncms_mqtt.php|Starting MQTT Input script
2026-09-22 07:06:53.381|WARN|emoncms_mqtt.php|Not connected, retrying connection
2026-09-22 07:06:53.393|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2026-09-22 07:06:55.340|ERROR|index.php|Not Authenticated|admin/info
2026-09-22 07:07:00.288|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 07:41:14.215|WARN|emoncms_mqtt.php|Starting MQTT Input script
2026-09-22 07:41:14.273|WARN|emoncms_mqtt.php|Not connected, retrying connection
2026-09-22 07:41:14.285|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2026-09-22 08:18:43.392|ERROR|index.php|Not Authenticated|feed/list
2026-09-22 08:18:55.016|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 08:24:21.109|ERROR|index.php|Not Authenticated|feed/view
2026-09-22 08:24:25.333|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 14:42:58.472|ERROR|index.php|Not Authenticated|feed/view
2026-09-22 14:43:04.605|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 20:11:36.201|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'
2026-09-22 20:46:50.419|ERROR|index.php|Not Authenticated|admin/info
2026-09-22 20:46:53.882|WARN|user_model.php|clear_password_reset_token failed userid:1 Unknown column 'password_reset_hash' in 'where clause'

I’m having the same behaviour. Did you get a permanent solution?

No unfortunately,.. my system died again last night.. and I cannot reset it for a few days as I am away.

I was hoping the WD40 clean etc would resolve things for me but this clearly has not worked.

One thing I have noticed is ‘failures’ are occurring at the end of the day.. say around 10pm onwards… what do you see?

Are you running Trystans new back process.. as that is the only ‘big’ thing I have changed in recent weeks,.. apart from the new CMS update.

Hello @diyhouse

This looks related to recent security improvements in emoncms, a more secure way of storing passwords. It looks like the database update might not have run. Can you try a database update via Admin > Update > Database Update, does it report any database modifications?

When this issue pops up the first place to look is the emonhub log, if the data is coming in there and publishing to MQTT then we know the data is getting that far and the next place to look will be the emoncms_mqtt service, is it running/exited - that can be found towards the top of the Admin > Info page.

Example here shows emoncms_mqtt and emonhub both running, if they report anything other than that it’s a clue at least that we can work with:

Hi Trystan,.. Just got back,.. to investigate my issues,.. and looking at the EmonHub logs,.. I get this when things seem to go pear shaped…

This then continues,.. to current time,… pls note I recieve my Tx4 data via USB,.. which shows a similiar story,..

I do use ‘Radio’ to receive temperature and Hum. data from two remote sensors.. although EVSE data is being received via WiFi…

Not sure why I am seeing ‘stat/Tas_One’… as MQTT data,.. This is a Tasmota device tied into HA,.. why it appears as serial data at my EmonPi I do not know…

I do plug it into my EmonPi2 for power,… but this does seem to be sending rogue data,.. what ever,.. I have now disconnected it,.. and powered it down…

I have applied the database UPdate,… and got this:-

Having applied the database update,.. and I have now rebooted,.. and things seem to be OK for now…

I will monitor to see how things go.

Many Tx..

The emonhub error with the RFM69 connectivity issue is interesting, let me know if that happens again! What emonSD image version are you running? Can you copy the output of the Admin > Info page here

Let me just confirm I am running an EmonPi PV,.. yes an old unit,.. my info page is as follows

Not sure my original image but it was the ‘current one’ at the time… I have not rebuilt the system since.

Ah thanks! that makes sense, no SPI RFM69 on the emonPi v1 for emonhub to connect to and hence the error, you can ignore that or remove the interfacer config for the SPI from emonhub.conf if you prefer. I dont think this is related to the real issue that you have.

Did you say that both the emonPi v1 and emonTx4 data both stop at the same time?

I wonder if it’s an MQTT mosquitto server issue or perhaps a crashing emoncms_mqtt.service.. when this happens does emoncms_mqtt show as stopped?

This should only happen if you used the base MQTT topic of emon.

Something has changed @TrystanLea as for some reason the LOG says MQT rather than MQTT.

At the very top there is a ‘Copy as Markdown’ that you can just paste into a message here.

Ah the MQT is what the interfacer in emonhub has been named.

@diyhouse - can you paste your emonhub.conf file contents, please?

Do this by copying it and use CTL-E before pasting it so it come in preformatted. This is also a better way for any log outputs in preference to an image.

Aha perhaps emonhub.conf has a corrupted entry? I’ve had this happen to me a few times recently when editing over a slow dataplicity connection..

Interesting,.. well hope this ‘pasted ok’

here is my emonhub.conf… ready for inspection,…

BTW,.. my Tasmota node is currently switched off,.. ie not plugged in… I have certianly not ‘intentionally’ given it a base of emon,…

This config,.. has been running for some 2+yrs without issue,.. I have ( not that I recall ) edited or changed anything,.. ( if it ain’t broken don’t fix-it )

My current emonPi input is against emonpi_5,… when I was setting up I ended creating ‘new’ nodes.

Hope this makes sense.

Thankyou Guys…

pi@emonpi:/opt/openenergymonitor/emonhub/conf $ cat emonhub.conf 
#######################################################################
#######################      emonhub.conf     #########################
#######################################################################

## **LEGACY CONFIG: For use with 17thJune2015 emonPi/emonBase image and older **
## (check image version by looking for file in /boot)
## Uses old CSV MQTT topic structure compatible with Emoncms Nodes
## Does not use MQTT server authentication

### emonHub configuration file, for info see documentation:
### https://docs.openenergymonitor.org/emonhub/configuration.html
#######################################################################
#######################    emonHub  settings    #######################
#######################################################################

[hub]
### loglevel must be one of DEBUG, INFO, WARNING, ERROR, and CRITICAL
loglevel = DEBUG #(default:WARNING)
### Uncomment this to also send to syslog
# use_syslog = yes

#######################################################################
#######################       Interfacers       #######################
#######################################################################

[interfacers]
### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
[[RFM2Pi]]
   Type = EmonHubJeeInterfacer
   [[[init_settings]]]
      com_port = /dev/ttyAMA0
      com_baud = 38400                      # 9600 for old RFM12Pi modules
   [[[runtimesettings]]]
      pubchannels = ToEmonCMS,
      subchannels = ToRFM12,

      group = 210
      frequency = 433
      baseid = 5                              # emonPi / emonBase nodeID
      quiet = true                            # Report incomplete RF packets (no implemented on emonPi)
      calibration = 230V                      # (UK/EU: 230V, US: 110V)
      # interval =  0                         # Interval to transmit time to emonGLCD (seconds)

[[MQTT]]

   Type = EmonHubMqttInterfacer
   [[[init_settings]]]
      mqtt_host = 127.0.0.1
      mqtt_port = 1883
      mqtt_user = ''
      mqtt_passwd = ''

   [[[runtimesettings]]]
      pubchannels = ToRFM12,
      subchannels = ToEmonCMS,

      # emonhub/rx/10/values format
      # Use with emoncms Nodes module
      node_format_enable = 1
      node_format_basetopic = emonhub/

      # emon/emontx/power1 format - use with Emoncms MQTT input
      # http://github.com/emoncms/emoncms/blob/master/docs/RaspberryPi/MQTT.md
      nodevar_format_enable = 1
      nodevar_format_basetopic = emon/

      # Single JSON payload published  - use with Emoncms MQTT
      node_JSON_enable = 0
      node_JSON_basetopic = emon/

[[emoncmsorg]]
   Type = EmonHubEmoncmsHTTPInterfacer
   [[[init_settings]]]
   [[[runtimesettings]]]
      pubchannels = ToRFM12,
      subchannels = ToEmonCMS,
      url = https://emoncms.org
      apikey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
      senddata = 0                    # Enable sending data to Emoncms.org
      sendstatus = 1                  # Enable sending WAN IP to Emoncms.org MyIP > https://emoncms.org/myip/list
      interval = 30                   # Bulk send interval to Emoncms.org in seconds

#######################################################################
#######################          Nodes          #######################
#######################################################################

[nodes]

## See config user guide: https://docs.openenergymonitor.org/emonhub/configuration.html

[[5]]
   nodename = emonpi
   [[[rx]]]
      names = power1,power2,power1pluspower2,vrms,t1,t2,t3,t4,t5,t6,pulsecount
      datacodes = h, h, h, h, h, h, h, h, h, h, L
      scales = 1,1,1,0.01,0.1,0.1,0.1,0.1,0.1,0.1,1
      units = W,W,W,V,C,C,C,C,C,C,p

[[6]]
   nodename = emontxshield
   [[[rx]]]
      names = power1, power2, power3, power4, vrms
      datacode = h
      scales = 1,1,1,1,0.01
      units =W,W,W,W,V

[[7]]
   nodename = emontx4
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[8]]
   nodename = emontx3
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[9]]
   nodename = emontx2
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacode = h
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[10]]
   nodename = emontx1
   [[[rx]]]
      names = power1, power2, power3, power4, vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacode = h
      scales = 1,1,1,1,0.01,0.1,0.1, 0.1,0.1,0.1,0.1,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[11]]
   nodename = 3phase
   [[[rx]]]
      names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[12]]
   nodename = 3phase2
   [[[rx]]]
      names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[13]]
   nodename = 3phase3
   [[[rx]]]
      names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[14]]
   nodename = 3phase4
   [[[rx]]]
      names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
      datacodes = h,h,h,h,h,h,h,h,h,h,h,L
      scales = 1,1,1,1,0.01,0.01,0.01,0.01,0.01,0.01,0.01,1
      units =W,W,W,W,V,C,C,C,C,C,C,p

[[19]]
   nodename = emonth1
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[20]]
   nodename = emonth2
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[21]]
   nodename = emonth3
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[22]]
   nodename = emonth4
   [[[rx]]]
      names = temperature, external temperature, humidity, battery
      datacode = h
      scales = 0.1,0.1,0.1,0.1
      units = C,C,%,V

[[23]]
   nodename = emonth5
   [[[rx]]]
      names = temperature, external temperature, humidity, battery, pulsecount
      datacodes = h,h,h,h,L
      scales = 0.1,0.1,0.1,0.1,1
      units = C,C,%,V,p

[[24]]
   nodename = emonth6
   [[[rx]]]
      names = temperature, external temperature, humidity, battery, pulsecount
      datacodes = h,h,h,h,L
      scales = 0.1,0.1,0.1,0.1,1
      units = C,C,%,V,p

[[25]]
   nodename = emonth7
   [[[rx]]]
      names = temperature, external temperature, humidity, battery, pulsecount
      datacodes = h,h,h,h,L
      scales = 0.1,0.1,0.1,0.1,1
      units = C,C,%,V,p

[[26]]
   nodename = emonth8
   [[[rx]]]
      names = temperature, external temperature, humidity, battery, pulsecount
      datacodes = h,h,h,h,L
      scales = 0.1,0.1,0.1,0.1,1
      units = C,C,%,V,p

pi@emonpi:/opt/openenergymonitor/emonhub/conf $ 


and typical EmonHub output is as follows.

ah sorry that was a red herring, the MQT is in the serial window not the emonhub.log window, from your earlier screenshot.

The emonhub log looks fine.

The emonhub.conf you have shared there is just an example conf file in the emonhub directory. The actual configuration file running on your system can be found at:

cat /etc/emonhub/emonhub.conf

Let us know what you see in that one

Since disconnecting it have you had this issue again?

Two other possibilities here:

  • The emonPi v1 power supply may not be sufficient to power all 3 devices: the emonPi + emonTx4 + Tasmota, power supply issues have often caused radio issues in the past.
  • It looks like the Tasmota does connect as a serial device and so it may have taken over /dev/ttyUSB0 from the emonTx4 causing the emonTx4 to stop reading. If you have two USB serial devices plugged in they can often swap ports, there is a way to fix the ports by id but it’s perhaps simpler given possible power issues could be to power the tasmota separately.

Thanks for responding Trystan,…

Since disconnecting my Tas device,.. normal service has continued,… However it can take 2 or 3 days before Comms are lost,.. so still sort of early days…

power the tasmota separately.

Yes I have been giving this some thought myself how I might best derive a 5volt USB supply for my Tasmota device,…

For now I will leave it disconnected,.. and see how the EmonPi / Tx4 continue perform,…

many Tx