I’ve just got my 3 emonTHs, and put batteries in them. But I don’t see any data for them on the inputs page on my emonPi. I see ‘emonth6’ appear, just after that send data I assume, but it just has ‘rssi’ and no temp, humidity and battery level data. Then when the emonth7 sends, the emonth6 input goes and emonth7 appears. Then the same for emonth8. But all have just ‘rssi’ and no other data.
Any ideas what I’m doing wrong?!
Pease run emoniupdate from local Emoncms to make sure you have the latest emonPi firmware (Setup > Admin > emonpiupdate).
Does the LED on the emonTH light up when you insert the batteries? Are these the new emonTH V2 with the si7021 sensors instead of DHT22?
Are the DIP switches differently on each emonTH to set different RF node ID’s?
Done - but nothing needed updating and hasn’t affected anything - still not working.
Yep. Green light comes on, then goes off.
Yep.
Oh, weird?! It’s now working?! I’ll keep monitoring…
that’s strange, let me know if you have any further issues.
I got similar problem, I trying but two new emonTh to my system,
first one the LED don’t light 
but the second one LED works and from time to time shows new emonth8 in system, but only rssi, and disappears again.
When look from EmohHub log , then there is all parameters is shown like in emonth7 and emonth5 which already works in system like must work.
Any ideas ?
emnPi firmware updated just a two days ago.
If the LED on the emonTH does not light at all this could indicate a hardware failure. The LED should light for a few seconds when the batteries are inserted. Can you confirm the LED on the emonTH does not light at all even with fresh batteries?
Do all the battery terminal contacts look ok?
can you post some emonhub.log?
It sounds like 2 issues at play
2 might be overcome with a reboot (known bug) and to debug 1 there may be useful info in the emonhub.log
Yes I confirm, that the LED light does nothing at all - I got from emon.Shop this some days ago - sticker “Func Pass” on it 
But I got two of them, and second one lights ok and I see the information from emonHub log - but I don’t see this from “inputs” list
here some of log
emonth8 is this what don’t show’s on input list
2017-01-17 21:22:05,453 DEBUG RFM2Pi 42736 NEW FRAME : OK 5 0 0 0 0 0 0 0 0 238 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-01-17 21:22:05,454 DEBUG RFM2Pi 42736 Timestamp : 1484688125.45
2017-01-17 21:22:05,455 DEBUG RFM2Pi 42736 From Node : 5
2017-01-17 21:22:05,455 DEBUG RFM2Pi 42736 Values : [0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:05,455 DEBUG RFM2Pi 42736 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:05,456 INFO RFM2Pi Publishing: emon/emonpi/power1 0
2017-01-17 21:22:05,456 INFO RFM2Pi Publishing: emon/emonpi/power2 0
2017-01-17 21:22:05,457 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 0
2017-01-17 21:22:05,458 INFO RFM2Pi Publishing: emon/emonpi/vrms 0
2017-01-17 21:22:05,472 INFO RFM2Pi Publishing: emon/emonpi/t1 23.8
2017-01-17 21:22:05,473 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2017-01-17 21:22:05,474 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2017-01-17 21:22:05,475 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2017-01-17 21:22:05,475 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2017-01-17 21:22:05,476 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2017-01-17 21:22:05,477 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2017-01-17 21:22:05,477 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2017-01-17 21:22:05,478 INFO RFM2Pi Publishing: emonhub/rx/5/values 0,0,0,0,23.8,0,0,0,0,0,0
2017-01-17 21:22:05,479 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2017-01-17 21:22:05,480 DEBUG RFM2Pi 42736 adding frame to buffer => [1484688125.453059, 5, 0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:05,480 DEBUG RFM2Pi 42736 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:05,583 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 29 5 149 192 8 108 96 3 185 32 159 28 168 160 51 129 48 161 82 64 64 (-97)
2017-01-17 21:22:05,687 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 25 130 0 74 29 65 0 38 20 0 224 97 168 160 51 129 48 161 82 64 64 (-94)
2017-01-17 21:22:06,402 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 24 97 40 45 156 72 32 160 32 89 32 96 5 0 32 22 32 128 49 2 145 (-97)
2017-01-17 21:22:06,606 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 8 0 128 32 59 72 32 160 32 89 32 96 5 0 32 22 32 128 49 2 145 (-97)
2017-01-17 21:22:07,110 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 14 236 150 128 128 96 193 165 93 64 66 1 224 54 9 16 135 234 137 99 161 (-95)
2017-01-17 21:22:08,019 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 8 16 17 138 129 32 7 32 89 160 22 96 113 32 208 244 133 48 156 47 46 (-95)
2017-01-17 21:22:08,825 DEBUG RFM2Pi 42737 NEW FRAME : OK 8 236 2 248 0 231 1 0 0 50 96 212 0 184 11 184 11 184 11 184 11 184 11 1 0 0 0 (-51)
2017-01-17 21:22:08,827 DEBUG RFM2Pi 42737 Timestamp : 1484688128.83
2017-01-17 21:22:08,827 DEBUG RFM2Pi 42737 From Node : 8
2017-01-17 21:22:08,828 DEBUG RFM2Pi 42737 Values : [748, 248, 487, 0, 246.26000000000002, 21.200000000000003, 300, 300, 300, 300, 300, 1]
2017-01-17 21:22:08,828 DEBUG RFM2Pi 42737 RSSI : -51
2017-01-17 21:22:08,828 DEBUG RFM2Pi 42737 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:08,829 INFO RFM2Pi Publishing: emon/emontx3/power1 748
2017-01-17 21:22:08,829 INFO RFM2Pi Publishing: emon/emontx3/power2 248
2017-01-17 21:22:08,830 INFO RFM2Pi Publishing: emon/emontx3/power3 487
2017-01-17 21:22:08,831 INFO RFM2Pi Publishing: emon/emontx3/power4 0
2017-01-17 21:22:08,831 INFO RFM2Pi Publishing: emon/emontx3/vrms 246.26
2017-01-17 21:22:08,832 INFO RFM2Pi Publishing: emon/emontx3/temp1 21.2
2017-01-17 21:22:08,833 INFO RFM2Pi Publishing: emon/emontx3/temp2 300
2017-01-17 21:22:08,834 INFO RFM2Pi Publishing: emon/emontx3/temp3 300
2017-01-17 21:22:08,834 INFO RFM2Pi Publishing: emon/emontx3/temp4 300
2017-01-17 21:22:08,835 INFO RFM2Pi Publishing: emon/emontx3/temp5 300
2017-01-17 21:22:08,836 INFO RFM2Pi Publishing: emon/emontx3/temp6 300
2017-01-17 21:22:08,836 INFO RFM2Pi Publishing: emon/emontx3/pulse 1
2017-01-17 21:22:08,837 INFO RFM2Pi Publishing: emon/emontx3/rssi -51
2017-01-17 21:22:08,838 INFO RFM2Pi Publishing: emonhub/rx/8/values 748,248,487,0,246.26,21.2,300,300,300,300,300,1
2017-01-17 21:22:08,838 INFO RFM2Pi Publishing: emonhub/rx/8/rssi -51
2017-01-17 21:22:08,839 DEBUG RFM2Pi 42737 adding frame to buffer => [1484688128.825569, 8, 748, 248, 487, 0, 246.26000000000002, 21.200000000000003, 300, 300, 300, 300, 300, 1, -51]
2017-01-17 21:22:08,840 DEBUG RFM2Pi 42737 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:08,943 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 6 130 180 163 112 68 8 128 132 228 168 82 0 5 10 168 33 64 0 35 0 (-96)
2017-01-17 21:22:09,454 DEBUG RFM2Pi 42738 NEW FRAME : OK 23 205 0 0 0 60 1 31 0 1 0 0 0 (-61)
2017-01-17 21:22:09,456 DEBUG RFM2Pi 42738 Timestamp : 1484688129.45
2017-01-17 21:22:09,456 DEBUG RFM2Pi 42738 From Node : 23
2017-01-17 21:22:09,457 DEBUG RFM2Pi 42738 Values : [20.5, 0, 31.6, 3.1, 1]
2017-01-17 21:22:09,457 DEBUG RFM2Pi 42738 RSSI : -61
2017-01-17 21:22:09,458 DEBUG RFM2Pi 42738 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:09,459 INFO RFM2Pi Publishing: emon/emonth5/temperature 20.5
2017-01-17 21:22:09,461 INFO RFM2Pi Publishing: emon/emonth5/external temperature 0
2017-01-17 21:22:09,462 INFO RFM2Pi Publishing: emon/emonth5/humidity 31.6
2017-01-17 21:22:09,468 INFO RFM2Pi Publishing: emon/emonth5/battery 3.1
2017-01-17 21:22:09,472 INFO RFM2Pi Publishing: emon/emonth5/pulsecount 1
2017-01-17 21:22:09,476 INFO RFM2Pi Publishing: emon/emonth5/rssi -61
2017-01-17 21:22:09,478 INFO RFM2Pi Publishing: emonhub/rx/23/values 20.5,0,31.6,3.1,1
2017-01-17 21:22:09,479 INFO RFM2Pi Publishing: emonhub/rx/23/rssi -61
2017-01-17 21:22:09,481 DEBUG RFM2Pi 42738 adding frame to buffer => [1484688129.453805, 23, 20.5, 0, 31.6, 3.1, 1, -61]
2017-01-17 21:22:09,482 DEBUG RFM2Pi 42738 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:10,487 DEBUG RFM2Pi 42739 NEW FRAME : OK 5 0 0 0 0 0 0 0 0 238 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-01-17 21:22:10,489 DEBUG RFM2Pi 42739 Timestamp : 1484688130.49
2017-01-17 21:22:10,489 DEBUG RFM2Pi 42739 From Node : 5
2017-01-17 21:22:10,490 DEBUG RFM2Pi 42739 Values : [0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:10,490 DEBUG RFM2Pi 42739 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:10,490 INFO RFM2Pi Publishing: emon/emonpi/power1 0
2017-01-17 21:22:10,491 INFO RFM2Pi Publishing: emon/emonpi/power2 0
2017-01-17 21:22:10,492 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 0
2017-01-17 21:22:10,492 INFO RFM2Pi Publishing: emon/emonpi/vrms 0
2017-01-17 21:22:10,493 INFO RFM2Pi Publishing: emon/emonpi/t1 23.8
2017-01-17 21:22:10,494 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2017-01-17 21:22:10,496 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2017-01-17 21:22:10,498 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2017-01-17 21:22:10,500 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2017-01-17 21:22:10,501 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2017-01-17 21:22:10,503 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2017-01-17 21:22:10,506 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2017-01-17 21:22:10,507 INFO RFM2Pi Publishing: emonhub/rx/5/values 0,0,0,0,23.8,0,0,0,0,0,0
2017-01-17 21:22:10,508 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2017-01-17 21:22:10,509 DEBUG RFM2Pi 42739 adding frame to buffer => [1484688130.487609, 5, 0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:10,510 DEBUG RFM2Pi 42739 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:12,318 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 2 33 33 11 168 48 16 230 113 104 91 10 31 93 16 7 189 0 128 0 208 (-95)
2017-01-17 21:22:13,932 DEBUG RFM2Pi 42740 NEW FRAME : OK 26 249 0 0 0 194 0 31 0 1 0 0 0 (-48)
2017-01-17 21:22:13,933 DEBUG RFM2Pi 42740 Timestamp : 1484688133.93
2017-01-17 21:22:13,934 DEBUG RFM2Pi 42740 From Node : 26
2017-01-17 21:22:13,934 DEBUG RFM2Pi 42740 Values : [24.900000000000002, 0, 19.400000000000002, 3.1, 1]
2017-01-17 21:22:13,934 DEBUG RFM2Pi 42740 RSSI : -48
2017-01-17 21:22:13,934 DEBUG RFM2Pi 42740 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:13,935 INFO RFM2Pi Publishing: emon/emonth8/temperature 24.9
2017-01-17 21:22:13,936 INFO RFM2Pi Publishing: emon/emonth8/external temperature 0
2017-01-17 21:22:13,936 INFO RFM2Pi Publishing: emon/emonth8/humidity 19.4
2017-01-17 21:22:13,937 INFO RFM2Pi Publishing: emon/emonth8/battery 3.1
2017-01-17 21:22:13,938 INFO RFM2Pi Publishing: emon/emonth8/pulsecount 1
2017-01-17 21:22:13,939 INFO RFM2Pi Publishing: emon/emonth8/rssi -48
2017-01-17 21:22:13,939 INFO RFM2Pi Publishing: emonhub/rx/26/values 24.9,0,19.4,3.1,1
2017-01-17 21:22:13,940 INFO RFM2Pi Publishing: emonhub/rx/26/rssi -48
2017-01-17 21:22:13,941 DEBUG RFM2Pi 42740 adding frame to buffer => [1484688133.932369, 26, 24.900000000000002, 0, 19.400000000000002, 3.1, 1, -48]
2017-01-17 21:22:13,941 DEBUG RFM2Pi 42740 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:14,248 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 7 185 41 45 225 157 71 242 56 97 251 104 49 184 203 134 114 145 169 178 176 (-102)
2017-01-17 21:22:15,468 DEBUG RFM2Pi 42741 NEW FRAME : OK 5 0 0 0 0 0 0 0 0 238 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-01-17 21:22:15,485 DEBUG RFM2Pi 42741 Timestamp : 1484688135.47
2017-01-17 21:22:15,486 DEBUG RFM2Pi 42741 From Node : 5
2017-01-17 21:22:15,486 DEBUG RFM2Pi 42741 Values : [0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:15,487 DEBUG RFM2Pi 42741 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:15,488 INFO RFM2Pi Publishing: emon/emonpi/power1 0
2017-01-17 21:22:15,490 INFO RFM2Pi Publishing: emon/emonpi/power2 0
2017-01-17 21:22:15,491 INFO RFM2Pi Publishing: emon/emonpi/power1pluspower2 0
2017-01-17 21:22:15,492 INFO RFM2Pi Publishing: emon/emonpi/vrms 0
2017-01-17 21:22:15,494 INFO RFM2Pi Publishing: emon/emonpi/t1 23.8
2017-01-17 21:22:15,495 INFO RFM2Pi Publishing: emon/emonpi/t2 0
2017-01-17 21:22:15,497 INFO RFM2Pi Publishing: emon/emonpi/t3 0
2017-01-17 21:22:15,499 INFO RFM2Pi Publishing: emon/emonpi/t4 0
2017-01-17 21:22:15,500 INFO RFM2Pi Publishing: emon/emonpi/t5 0
2017-01-17 21:22:15,501 INFO RFM2Pi Publishing: emon/emonpi/t6 0
2017-01-17 21:22:15,503 INFO RFM2Pi Publishing: emon/emonpi/pulsecount 0
2017-01-17 21:22:15,504 INFO RFM2Pi Publishing: emon/emonpi/rssi 0
2017-01-17 21:22:15,507 INFO RFM2Pi Publishing: emonhub/rx/5/values 0,0,0,0,23.8,0,0,0,0,0,0
2017-01-17 21:22:15,509 INFO RFM2Pi Publishing: emonhub/rx/5/rssi 0
2017-01-17 21:22:15,510 DEBUG RFM2Pi 42741 adding frame to buffer => [1484688135.468536, 5, 0, 0, 0, 0, 23.8, 0, 0, 0, 0, 0, 0]
2017-01-17 21:22:15,511 DEBUG RFM2Pi 42741 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:15,617 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 4 15 72 0 0 0 1 224 0 136 162 155 1 184 203 134 114 145 169 178 176 (-96)
2017-01-17 21:22:15,922 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 11 76 180 1 16 225 32 2 20 8 224 40 10 128 0 0 2 32 6 178 176 (-95)
2017-01-17 21:22:16,828 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 2 152 0 184 102 34 200 38 162 134 53 40 10 128 0 0 2 32 6 178 176 (-97)
2017-01-17 21:22:18,144 DEBUG RFM2Pi Discarding RX frame 'unreliable content'? 17 17 6 32 0 8 10 0 11 130 18 3 30 129 44 3 27 10 192 48 0 (-93)
2017-01-17 21:22:18,749 DEBUG RFM2Pi 42742 NEW FRAME : OK 8 235 2 250 0 16 2 0 0 117 96 212 0 184 11 184 11 184 11 184 11 184 11 1 0 0 0 (-61)
2017-01-17 21:22:18,751 DEBUG RFM2Pi 42742 Timestamp : 1484688138.75
2017-01-17 21:22:18,751 DEBUG RFM2Pi 42742 From Node : 8
2017-01-17 21:22:18,751 DEBUG RFM2Pi 42742 Values : [747, 250, 528, 0, 246.93, 21.200000000000003, 300, 300, 300, 300, 300, 1]
2017-01-17 21:22:18,751 DEBUG RFM2Pi 42742 RSSI : -61
2017-01-17 21:22:18,752 DEBUG RFM2Pi 42742 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:18,752 INFO RFM2Pi Publishing: emon/emontx3/power1 747
2017-01-17 21:22:18,753 INFO RFM2Pi Publishing: emon/emontx3/power2 250
2017-01-17 21:22:18,754 INFO RFM2Pi Publishing: emon/emontx3/power3 528
2017-01-17 21:22:18,755 INFO RFM2Pi Publishing: emon/emontx3/power4 0
2017-01-17 21:22:18,756 INFO RFM2Pi Publishing: emon/emontx3/vrms 246.93
2017-01-17 21:22:18,756 INFO RFM2Pi Publishing: emon/emontx3/temp1 21.2
2017-01-17 21:22:18,757 INFO RFM2Pi Publishing: emon/emontx3/temp2 300
2017-01-17 21:22:18,758 INFO RFM2Pi Publishing: emon/emontx3/temp3 300
2017-01-17 21:22:18,759 INFO RFM2Pi Publishing: emon/emontx3/temp4 300
2017-01-17 21:22:18,760 INFO RFM2Pi Publishing: emon/emontx3/temp5 300
2017-01-17 21:22:18,760 INFO RFM2Pi Publishing: emon/emontx3/temp6 300
2017-01-17 21:22:18,762 INFO RFM2Pi Publishing: emon/emontx3/pulse 1
2017-01-17 21:22:18,763 INFO RFM2Pi Publishing: emon/emontx3/rssi -61
2017-01-17 21:22:18,764 INFO RFM2Pi Publishing: emonhub/rx/8/values 747,250,528,0,246.93,21.2,300,300,300,300,300,1
2017-01-17 21:22:18,765 INFO RFM2Pi Publishing: emonhub/rx/8/rssi -61
2017-01-17 21:22:18,766 DEBUG RFM2Pi 42742 adding frame to buffer => [1484688138.749206, 8, 747, 250, 528, 0, 246.93, 21.200000000000003, 300, 300, 300, 300, 300, 1, -61]
2017-01-17 21:22:18,766 DEBUG RFM2Pi 42742 Sent to channel(end)' : ToEmonCMS
2017-01-17 21:22:20,500 DEBUG RFM2Pi 42743 NEW FRAME : OK 5 0 0 0 0 0 0 0 0 238 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)This section shows the emonth8 being published to MQTT, if it isn’t showing in emoncms it is the emoncms’s mqtt_input thats not subscribing or not procesing that data. I have seen this and found a reboot overcome the issue, it may even be possible to restart the mqtt_input service or some other service rather than reboot, but I cannot confirm that to be the case. Have you tried a reboot?
2017-01-17 21:22:13,934 DEBUG RFM2Pi 42740 Sent to channel(start)' : ToEmonCMS
2017-01-17 21:22:13,935 INFO RFM2Pi Publishing: emon/emonth8/temperature 24.9
2017-01-17 21:22:13,936 INFO RFM2Pi Publishing: emon/emonth8/external temperature 0
2017-01-17 21:22:13,936 INFO RFM2Pi Publishing: emon/emonth8/humidity 19.4
2017-01-17 21:22:13,937 INFO RFM2Pi Publishing: emon/emonth8/battery 3.1
2017-01-17 21:22:13,938 INFO RFM2Pi Publishing: emon/emonth8/pulsecount 1
2017-01-17 21:22:13,939 INFO RFM2Pi Publishing: emon/emonth8/rssi -48
2017-01-17 21:22:13,939 INFO RFM2Pi Publishing: emonhub/rx/26/values 24.9,0,19.4,3.1,1
2017-01-17 21:22:13,940 INFO RFM2Pi Publishing: emonhub/rx/26/rssi -48
2017-01-17 21:22:13,941 DEBUG RFM2Pi 42740 adding frame to buffer => [1484688133.932369, 26, 24.900000000000002, 0, 19.400000000000002, 3.1, 1, -48]
An rssi of -48 should be strong enough so once you have the input visible in emoncms check the “updated” column, it should update every 60secs, give or take.
I tried - update what doing reboot to system, and that’s was helpful.
emonTH8 appeared to input list, and all works.
thanks
Please contact the shop via support email to arrange a replacement for the faulty emonTH: [email protected]
Was there any additional diagnosis on what caused emoncms not to pick up these messages?
I just experienced the same issue. Two new EmonTH devices, both powered up and publishing to MQTT. I changed the nodenames in emonhub.conf, restarted the emonhub service, and confirmed that the messages were coming in and getting published to the proper topics in MQTT. Using mosquitto_sub, I subscribed to my emon/emonth1/# and emon/emonth2/# topics and saw data values come across, yet emoncms showed only a single rssi input and only that for one of my two devices (the second one never appeared at all). A full restart cleared things up, but that’s an awfully heavy hammer.
I’ve published all kinds of new inputs to this instance before with the straight input API, so I wonder if there’s an edge case in the phpmqtt_input script that needs squashing.
This is a long standing issue that hasn’t yet been addressed.
See the “Newly created inputs not appearing in emonCMS via MQTT” thread from around post 10/27.
The issue has been confirmed to only exist within emoncms MQTT implementation, all data can always be seen via mosquitto_sub which points to either the mqtt_service or more likely phpmqtt_input.php.
Agreed, but to date the only sure advice to overcome what has sadly become “expected behaviour” when adding new nodes on an emonPi/emonSD, is to reboot
However, in the “MQTT Strangeness” thread @TrystanLea confirms he had no issue having “only just started the mqtt service script” so it maybe that the emonPi doesn’t need a full reboot, I haven’t tested this theory yet.
As for restarting emonHub, that shouldn’t be necessary, emonhub was written to run continuously, it shouldn’t ever need restarting unless a revised version is installed/updated etc. All settings should be picked up during normal running.