Added EmonTx4, inputs not showing

Hardware emonTx
1

So, new EmonTX with ID 7 added, and it shows as EmonTX 4 as expected, but I do not see any inputs, just RSSI:

emontx3_4
emontx3_41212×354 13.6 KB

My EmonPi is up to date, and emonCM configuration has the expected entries present for all inputs:

[[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

Not sure if I need to do something else to get the new inputs showing, I did a search but I can’t see anyone else having this issue most are about changing node ID etc - but I am just running two EmonTX v3 with the dip switch on the new one for Node 7.

2

You have changed the NodeID successfully. It is appearing, but with no data. I can’t understand why the data isn’t being seen, and I can’t recollect seeing the same problem either. What does the emonhub log tell you?

3

Try rebooting the emonPi. Sounds like the longstanding known issue with the emoncms mqtt inputs PHP script not recognizing newly created inputs. Restarting the emoncms mqtt service might also work but I haven’t tried that myself. There are many threads on this issue but no advances on a fix yet AFAIK.

4

Actually I ordered the EmonTX from the shop as ID 7 so I didn’t even have to do that!

emonhub log shows MQTT feed:

2017-09-19 07:01:02,922 DEBUG MQTT Publishing: emon/emontx4/power1 0
2017-09-19 07:01:02,924 DEBUG MQTT Publishing: emon/emontx4/power2 0
2017-09-19 07:01:02,926 DEBUG MQTT Publishing: emon/emontx4/power3 0
2017-09-19 07:01:02,927 DEBUG MQTT Publishing: emon/emontx4/power4 0
2017-09-19 07:01:02,929 DEBUG MQTT Publishing: emon/emontx4/vrms 4.29
2017-09-19 07:01:02,930 DEBUG MQTT Publishing: emon/emontx4/temp1 300
2017-09-19 07:01:02,931 DEBUG MQTT Publishing: emon/emontx4/temp2 300
2017-09-19 07:01:02,933 DEBUG MQTT Publishing: emon/emontx4/temp3 300
2017-09-19 07:01:02,934 DEBUG MQTT Publishing: emon/emontx4/temp4 300
2017-09-19 07:01:02,935 DEBUG MQTT Publishing: emon/emontx4/temp5 300
2017-09-19 07:01:02,937 DEBUG MQTT Publishing: emon/emontx4/temp6 300
2017-09-19 07:01:02,938 DEBUG MQTT Publishing: emon/emontx4/pulse 0
2017-09-19 07:01:02,940 INFO MQTT Publishing: emon/emontx4/rssi -52
2017-09-19 07:01:02,941 INFO MQTT Publishing: emonhub/rx/7/values 0,0,0,0,4.29,300,300,300,300,300,300,0
2017-09-19 07:01:02,943 INFO MQTT Publishing: emonhub/rx/7/rssi -52

@ph66 thanks I will try a restart of mqtt and see if that helps.

I was confused, hence the post…

5

ok mqtt restart solved the issue and I now have all the feeds on EmonTX4, thanks for help!

For future reference of anyone with the same issue exact command needed is:
sudo service mqtt_input restart

6

Thanks for coming back and confirming a restart of the mqtt service worked, that will be useful to others.

For clarity for future readers, it’s just the dedicated emoncms mqtt_input service that needs restarting, not the Mosquitto MQTT broker.