EmonTx not updating emonPi

[glyn.hudson]

It would be useful to keep a log of the MQTT traffic to determine if the data is getting as far as MQTT. A while back a published an example nodeRED flow to do this:

See bottom of this post:

Phantom Duplicated MQTT Topics after reboot

It’s hard to debug something that happens so rarely. I’ve only seen this happen once in 100’s of reboots on many emonPi’s! Just to summarise where we are at: ISSUE A new set of Emoncms Inputs for the same node are created by the Emoncms MQTT input script. These inputs have exactly the same names as the old ones. The MQTT input script obtains the names of the inputs from the MQTT topic names. e.g The MQTT topic emon/emontx/power1 results in an Emoncms Input called power1 from emontx node. An…

NodeRED is pre installed on your emonPi, just browser to http:///emonpi:1880 then login with ‘emonpi’ and ‘emonpi2016’ . Select import then paste in my example flow. You will need to change the save log file location to /home/pi/data instead of the external HDD I was using for the example.