Unable to get new emonTx working with existing emonPi

Nicola_Reina · 18 November 2017 16:43

Hi All
I have a emonPi bought @ kickstarter project.
Recently I have bought a Emontx to extend the system but I am really frustrated
It is a week I am trying to get the node recoglized by emonhub
It is seen just at start and then it goes offline.
I have read quite a lot of threads on disconnection/communication problems (this is just one) and I have not been able to find a solution.

I am very tempted to request a refund as unfortunately I can spend time on setting up fixes but days… not weeks

Please advice
From the log: I have a “Discarded frame entry”

2017-11-18 04:57:49,878 INFO     RFM2Pi     Publishing: emon/emonpi/t5 0
2017-11-18 04:57:49,884 INFO     RFM2Pi     Publishing: emon/emonpi/t6 0
2017-11-18 04:57:49,887 INFO     RFM2Pi     Publishing: emon/emonpi/pulsecount 0
2017-11-18 04:57:49,891 INFO     RFM2Pi     Publishing: emon/emonpi/rssi 0
2017-11-18 04:57:49,895 INFO     RFM2Pi     Publishing: emonhub/rx/5/values 3,1016,1019,237.24,0,0,0,0,0,0,0
2017-11-18 04:57:49,900 INFO     RFM2Pi     Publishing: emonhub/rx/5/rssi 0
2017-11-18 04:57:49,903 DEBUG    RFM2Pi     196 adding frame to buffer => [1510981069.832833, 5, 3, 1016, 1019, 237.24, 0, 0, 0, 0, 0, 0, 0]
2017-11-18 04:57:49,904 DEBUG    RFM2Pi     196 Sent to channel(end)' : ToEmonCMS
2017-11-18 04:57:51,014 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 0 0 0 0 0 0 0 0 235 94 184 11 184 11 184 11 184 11 184 11 (-53)
2017-11-18 04:57:54,836 DEBUG    RFM2Pi     197 NEW FRAME : OK 5 6 0 246 3 252 3 202 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-18 04:57:54,840 DEBUG    RFM2Pi     197 Timestamp : 1510981074.84
2017-11-18 04:57:54,841 DEBUG    RFM2Pi     197 From Node : 5
2017-11-18 04:57:54,842 DEBUG    RFM2Pi     197    Values : [6, 1014, 1020, 237.54, 0, 0, 0, 0, 0, 0, 0]
2017-11-18 04:57:54,843 DEBUG    RFM2Pi     197 Sent to channel(start)' : ToEmonCMS
2017-11-18 04:57:54,844 INFO     RFM2Pi     Publishing: emon/emonpi/power1 6
2017-11-18 04:57:54,847 INFO     RFM2Pi     Publishing: emon/emonpi/power2 1014
2017-11-18 04:57:54,848 INFO     RFM2Pi     Publishing: emon/emonpi/power1pluspower2 1020
2017-11-18 04:57:54,851 INFO     RFM2Pi     Publishing: emon/emonpi/vrms 237.54
2017-11-18 04:57:54,852 INFO     RFM2Pi     Publishing: emon/emonpi/t1 0
2017-11-18 04:57:54,854 INFO     RFM2Pi     Publishing: emon/emonpi/t2 0
2017-11-18 04:57:54,856 INFO     RFM2Pi     Publishing: emon/emonpi/t3 0
2017-11-18 04:57:54,858 INFO     RFM2Pi     Publishing: emon/emonpi/t4 0
2017-11-18 04:57:54,860 INFO     RFM2Pi     Publishing: emon/emonpi/t5 0
2017-11-18 04:57:54,861 INFO     RFM2Pi     Publishing: emon/emonpi/t6 0
2017-11-18 04:57:54,863 INFO     RFM2Pi     Publishing: emon/emonpi/pulsecount 0
2017-11-18 04:57:54,865 INFO     RFM2Pi     Publishing: emon/emonpi/rssi 0
2017-11-18 04:57:54,867 INFO     RFM2Pi     Publishing: emonhub/rx/5/values 6,1014,1020,237.54,0,0,0,0,0,0,0
2017-11-18 04:57:54,869 INFO     RFM2Pi     Publishing: emonhub/rx/5/rssi 0
2017-11-18 04:57:54,871 DEBUG    RFM2Pi     197 adding frame to buffer => [1510981074.835703, 5, 6, 1014, 1020, 237.54, 0, 0, 0, 0, 0, 0, 0]

EmonPi sw is all updated.
EmonTx as it came from your shop (I have no usb auart to update anything)

Frankly disappointing this time

pb66 · 18 November 2017 17:08

I have moved your post as tacking it on the end of a thread 2yrs after the last post is unlikely to get the attention you need and that will only add to your frustration.

We are not all connected with “the shop” many of us are just users like yourself.

If you wish to contact the shop directly (for a refund) you will need to email them but all the tech support is here on the forum.

Can you post some more log? Possibly including a restart to see the initial packets and then the fail. quoting one packet isn’t very revealing, yes that one packet was discarded, but occasionally they can be. Is every packet discarded? or are some missing? or are some being passed on to mqtt and being lost that side of emonhub?

If you have just purchased the emonTx it should be the latest FW but a usb programmer would be handy to check the FW and/or to reinstall if needed. Can you borrow one?

The rssi of that one packet is -56, that is a fairly strong signal and I would not expect it to fail. “discarded packet” means the CRC checks failed, the packets checksum didn’t match the packet, this might suggest some interference.

If it is interference, sometimes selecting another “group” (channel) helps, for that you will require a usb programmer too.

How have you got the emonTx powered? Is it via a shop purchased AC:AC?

Nicola_Reina · 18 November 2017 20:05

Thanks for your quick reply and for putting the topic in evidence.
Let me answer inline and in a subsequent post have some more log entry

TX

Yes I know

I did to know what the process is but my first choice is still to have it working (indeed if I manage I buy onemore… But I have to have it working until 7/12 when it will be "sealed " in a kitchen)

I will add some log and check services are up

Ideally I would not like to have to touch the emontx fw

Yes indeed I know : the emontx and emonpi are in line of sight

I will try to select a different group. Here again : any suggestions or I just choose a random number?

AC/AC purchased from store

pb66 · 19 November 2017 10:46

IMO that is asking for trouble. sod’s law dictates if something is going to fail, it will be the thing that you cannot get to. You should make an access panel or if that is not at all possible then at the very least extend the 6way header to a point that is accessible to give you a way of resetting, debugging or updating. You could do that with a 6 way ribbon cable or buy a programmer and usb lead to leave connected.

You cannot change group without a programmer and it’s too early to know if changing group will help, it was an example. Changing group may help if the interference is from other RF devices, but not if it’s EMI radiated from appliances or cabling etc.

We can look a little closer at the data when you post, in the mean time I would recommend getting a programmer just in case, purely because of your deadline and postage times etc, you do not want to discover you need it at the 11th hour.

If you have no further use for it and decide to seal the emonTx away you can leave it permanently connected if you can’t extend the 6way header.

Nicola_Reina · 19 November 2017 11:09

Hi Thanks for the suggestions.
Well I don’t know yet how that part of the kitchen will be but I clearly will aim at having it in an accessible place (i.e. not in plain view but still accessible if needed).
I hope to put it in the base part of it.

I just bought this : https://www.amazon.it/WINGONEER-CP2104-Serial-Converter-compatibile/dp/B01CYBHM26/ref=sr_1_1?s=electronics&ie=UTF8&qid=1511088698&sr=1-1&keywords=usb+uart

The behaviour has changed a bit in my tests:

in the beginning I was at least receiving the RSSI input always.
Now not even that:
When I start or reset the emontx I have a first data sample in the feeds than nothing.

In the logs the message is always that of an unreliable frame discarded.

How can I check :

emonpi HW transmission frequency (433/868)
emontx HW tx frequency shall be 433

Sidenote: In my home there’s plenty of other radio but until now it was not a problem:
wifi 5/2.4
zigbee (hue)
zwave (openhab dongle) + I turned it now off

Here the downloaded log:

In this log: PI restart (reboot from admin interface) then emontx restart (restart from emonhub interface)

2017-11-19 11:02:26,511 INFO     MainThread EmonHub emonHub emon-pi variant v2.0.0
2017-11-19 11:02:26,512 INFO     MainThread Opening hub...
2017-11-19 11:02:26,514 INFO     MainThread Logging level set to DEBUG
2017-11-19 11:02:26,515 INFO     MainThread Creating EmonHubJeeInterfacer 'RFM2Pi' 
2017-11-19 11:02:26,520 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2017-11-19 11:02:28,533 INFO     MainThread RFM2Pi device firmware version: OK
2017-11-19 11:02:28,533 INFO     MainThread RFM2Pi device current settings:  5 184 6 71 5 255 11 128 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:28,534 INFO     MainThread Setting RFM2Pi frequency: 433 (4b)
2017-11-19 11:02:29,536 INFO     MainThread Setting RFM2Pi group: 210 (210g)
2017-11-19 11:02:30,538 INFO     MainThread Setting RFM2Pi quiet: 0 (0q)
2017-11-19 11:02:31,541 INFO     MainThread Setting RFM2Pi baseid: 5 (5i)
2017-11-19 11:02:32,543 INFO     MainThread Setting RFM2Pi calibration: 230V (1p)
2017-11-19 11:02:33,545 DEBUG    MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2017-11-19 11:02:33,546 DEBUG    MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2017-11-19 11:02:33,549 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT' 
2017-11-19 11:02:33,552 INFO     MainThread MQTT Init mqtt_host=127.0.0.1 mqtt_port=1883 mqtt_user=emonpi
2017-11-19 11:02:33,560 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:02:33,562 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg' 
2017-11-19 11:02:33,665 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:02:33,666 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:33,677 INFO     MQTT       Could not connect...
2017-11-19 11:02:33,770 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:02:33,874 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:02:33,985 DEBUG    RFM2Pi     1 NEW FRAME : OK 5 182 6 78 5 4 12 217 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:33,993 DEBUG    RFM2Pi     1 Timestamp : 1511089353.98
2017-11-19 11:02:33,995 DEBUG    RFM2Pi     1 From Node : 5
2017-11-19 11:02:33,996 DEBUG    RFM2Pi     1    Values : [1718, 1358, 3076, 237.69, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:02:33,998 DEBUG    RFM2Pi     1 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:02:33,999 DEBUG    RFM2Pi     1 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:02:34,109 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 17 0 0 0 0 0 0 0 24 95 184 11 184 11 184 11 184 11 184 11 (-59)
2017-11-19 11:02:34,214 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:02:34,780 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:34,783 INFO     MQTT       Could not connect...
2017-11-19 11:02:35,885 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:35,887 INFO     MQTT       Could not connect...
2017-11-19 11:02:36,989 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:36,991 INFO     MQTT       Could not connect...
2017-11-19 11:02:37,352 DEBUG    RFM2Pi     2 NEW FRAME : OK 5 192 6 144 4 80 11 242 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:37,359 DEBUG    RFM2Pi     2 Timestamp : 1511089357.35
2017-11-19 11:02:37,360 DEBUG    RFM2Pi     2 From Node : 5
2017-11-19 11:02:37,361 DEBUG    RFM2Pi     2    Values : [1728, 1168, 2896, 237.94, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:02:37,363 DEBUG    RFM2Pi     2 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:02:37,364 DEBUG    RFM2Pi     2 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:02:38,094 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:38,097 INFO     MQTT       Could not connect...
2017-11-19 11:02:45,397 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:45,399 INFO     MQTT       Could not connect...
2017-11-19 11:02:46,502 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:46,504 INFO     MQTT       Could not connect...
2017-11-19 11:02:47,606 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:47,609 INFO     MQTT       Could not connect...
2017-11-19 11:02:48,524 DEBUG    RFM2Pi     3 NEW FRAME : OK 5 192 6 134 5 70 12 209 91 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:48,529 DEBUG    RFM2Pi     3 Timestamp : 1511089368.52
2017-11-19 11:02:48,531 DEBUG    RFM2Pi     3 From Node : 5
2017-11-19 11:02:48,532 DEBUG    RFM2Pi     3    Values : [1728, 1414, 3142, 235.05, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:02:48,534 DEBUG    RFM2Pi     3 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:02:48,536 DEBUG    RFM2Pi     3 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:02:48,643 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 20 0 0 0 0 0 0 0 90 95 184 11 184 11 184 11 184 11 184 11 (-60)
2017-11-19 11:02:48,714 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:48,717 INFO     MQTT       Could not connect...
2017-11-19 11:02:49,820 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:49,823 INFO     MQTT       Could not connect...
2017-11-19 11:02:50,925 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:50,928 INFO     MQTT       Could not connect...
2017-11-19 11:02:52,030 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:52,033 INFO     MQTT       Could not connect...
2017-11-19 11:02:53,136 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:53,139 INFO     MQTT       Could not connect...
2017-11-19 11:02:53,502 DEBUG    RFM2Pi     4 NEW FRAME : OK 5 187 6 161 4 92 11 236 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:53,507 DEBUG    RFM2Pi     4 Timestamp : 1511089373.5
2017-11-19 11:02:53,508 DEBUG    RFM2Pi     4 From Node : 5
2017-11-19 11:02:53,510 DEBUG    RFM2Pi     4    Values : [1723, 1185, 2908, 237.88, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:02:53,511 DEBUG    RFM2Pi     4 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:02:53,513 DEBUG    RFM2Pi     4 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:02:54,242 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,347 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,451 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,556 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,660 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,785 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,889 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:54,993 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,097 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,201 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,305 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,411 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,516 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,621 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,727 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:02:55,732 INFO     MQTT       connection status: Connection successful
2017-11-19 11:02:55,734 DEBUG    MQTT       CONACK => Return code: 0
2017-11-19 11:02:55,836 DEBUG    MQTT       Publishing: emon/emonpi/power1 1718
2017-11-19 11:02:55,839 DEBUG    MQTT       Publishing: emon/emonpi/power2 1358
2017-11-19 11:02:55,841 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3076
2017-11-19 11:02:55,843 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.69
2017-11-19 11:02:55,846 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:02:55,848 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:02:55,850 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:02:55,852 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:02:55,855 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:02:55,858 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:02:55,861 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:02:55,864 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:02:55,867 INFO     MQTT       Publishing: emonhub/rx/5/values 1718,1358,3076,237.69,0,0,0,0,0,0,0
2017-11-19 11:02:55,869 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:02:55,872 DEBUG    MQTT       Publishing: emon/emonpi/power1 1728
2017-11-19 11:02:55,874 DEBUG    MQTT       Publishing: emon/emonpi/power2 1168
2017-11-19 11:02:55,877 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2896
2017-11-19 11:02:55,879 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.94
2017-11-19 11:02:55,881 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:02:55,884 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:02:55,887 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:02:55,888 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:02:55,890 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:02:55,891 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:02:55,893 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:02:55,896 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:02:55,898 INFO     MQTT       Publishing: emonhub/rx/5/values 1728,1168,2896,237.94,0,0,0,0,0,0,0
2017-11-19 11:02:55,899 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:02:55,901 DEBUG    MQTT       Publishing: emon/emonpi/power1 1728
2017-11-19 11:02:55,903 DEBUG    MQTT       Publishing: emon/emonpi/power2 1414
2017-11-19 11:02:55,904 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3142
2017-11-19 11:02:55,906 DEBUG    MQTT       Publishing: emon/emonpi/vrms 235.05
2017-11-19 11:02:55,908 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:02:55,910 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:02:55,912 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:02:55,914 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:02:55,916 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:02:55,917 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:02:55,918 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:02:55,920 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:02:55,922 INFO     MQTT       Publishing: emonhub/rx/5/values 1728,1414,3142,235.05,0,0,0,0,0,0,0
2017-11-19 11:02:55,923 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:02:55,925 DEBUG    MQTT       Publishing: emon/emonpi/power1 1723
2017-11-19 11:02:55,927 DEBUG    MQTT       Publishing: emon/emonpi/power2 1185
2017-11-19 11:02:55,928 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2908
2017-11-19 11:02:55,930 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.88
2017-11-19 11:02:55,932 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:02:55,933 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:02:55,935 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:02:55,936 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:02:55,937 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:02:55,939 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:02:55,940 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:02:55,942 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:02:55,944 INFO     MQTT       Publishing: emonhub/rx/5/values 1723,1185,2908,237.88,0,0,0,0,0,0,0
2017-11-19 11:02:55,945 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:02:55,948 INFO     MQTT       on_subscribe
2017-11-19 11:02:58,459 DEBUG    RFM2Pi     5 NEW FRAME : OK 5 194 6 224 4 162 11 44 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:02:58,463 DEBUG    RFM2Pi     5 Timestamp : 1511089378.46
2017-11-19 11:02:58,465 DEBUG    RFM2Pi     5 From Node : 5
2017-11-19 11:02:58,466 DEBUG    RFM2Pi     5    Values : [1730, 1248, 2978, 235.96, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:02:58,467 DEBUG    RFM2Pi     5 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:02:58,469 DEBUG    RFM2Pi     5 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:02:58,575 DEBUG    MQTT       Publishing: emon/emonpi/power1 1730
2017-11-19 11:02:58,579 DEBUG    MQTT       Publishing: emon/emonpi/power2 1248
2017-11-19 11:02:58,584 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 17 0 0 0 0 0 0 0 48 95 184 11 184 11 184 11 184 11 184 11 (-63)
2017-11-19 11:02:58,586 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2978
2017-11-19 11:02:58,589 DEBUG    MQTT       Publishing: emon/emonpi/vrms 235.96
2017-11-19 11:02:58,592 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:02:58,595 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:02:58,598 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:02:58,618 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:02:58,620 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:02:58,623 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:02:58,626 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:02:58,629 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:02:58,632 INFO     MQTT       Publishing: emonhub/rx/5/values 1730,1248,2978,235.96,0,0,0,0,0,0,0
2017-11-19 11:02:58,635 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:03,549 DEBUG    RFM2Pi     6 NEW FRAME : OK 5 191 6 107 5 42 12 144 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:03,552 DEBUG    RFM2Pi     6 Timestamp : 1511089383.55
2017-11-19 11:03:03,553 DEBUG    RFM2Pi     6 From Node : 5
2017-11-19 11:03:03,555 DEBUG    RFM2Pi     6    Values : [1727, 1387, 3114, 236.96, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:03,556 DEBUG    RFM2Pi     6 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:03,556 DEBUG    RFM2Pi     6 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:03,599 DEBUG    emoncmsorg Sending bulkdata, length: 6
2017-11-19 11:03:03,601 INFO     emoncmsorg sending: https://emoncms.org/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1511089353.984878,5,1718,1358,3076,237.69,0,0,0,0,0,0,0],[1511089357.35233,5,1728,1168,2896,237.94,0,0,0,0,0,0,0],[1511089368.523716,5,1728,1414,3142,235.05,0,0,0,0,0,0,0],[1511089373.501123,5,1723,1185,2908,237.88,0,0,0,0,0,0,0],[1511089378.459239,5,1730,1248,2978,235.96,0,0,0,0,0,0,0],[1511089383.548694,5,1727,1387,3114,236.96,0,0,0,0,0,0,0]]&sentat=1511089383
2017-11-19 11:03:03,610 DEBUG    MQTT       Publishing: emon/emonpi/power1 1727
2017-11-19 11:03:03,623 DEBUG    MQTT       Publishing: emon/emonpi/power2 1387
2017-11-19 11:03:03,633 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3114
2017-11-19 11:03:03,635 DEBUG    MQTT       Publishing: emon/emonpi/vrms 236.96
2017-11-19 11:03:03,637 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:03,639 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:03,651 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:03,653 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:03,655 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:03,657 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:03,660 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:03,662 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:03,665 INFO     MQTT       Publishing: emonhub/rx/5/values 1727,1387,3114,236.96,0,0,0,0,0,0,0
2017-11-19 11:03:03,667 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:04,170 DEBUG    emoncmsorg acknowledged receipt with 'ok' from https://emoncms.org
2017-11-19 11:03:04,171 DEBUG    emoncmsorg Sending bulkdata, success: True
2017-11-19 11:03:04,172 DEBUG    emoncmsorg Current queue length: 0
2017-11-19 11:03:04,174 INFO     emoncmsorg sending: https://emoncms.org/myip/set.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y
2017-11-19 11:03:08,512 DEBUG    RFM2Pi     7 NEW FRAME : OK 5 167 6 161 4 72 11 87 93 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:08,515 DEBUG    RFM2Pi     7 Timestamp : 1511089388.51
2017-11-19 11:03:08,516 DEBUG    RFM2Pi     7 From Node : 5
2017-11-19 11:03:08,517 DEBUG    RFM2Pi     7    Values : [1703, 1185, 2888, 238.95000000000002, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:08,518 DEBUG    RFM2Pi     7 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:08,519 DEBUG    RFM2Pi     7 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:08,628 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 16 0 0 0 0 0 0 0 41 95 184 11 184 11 184 11 184 11 184 11 (-60)
2017-11-19 11:03:08,723 DEBUG    MQTT       Publishing: emon/emonpi/power1 1703
2017-11-19 11:03:08,725 DEBUG    MQTT       Publishing: emon/emonpi/power2 1185
2017-11-19 11:03:08,727 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2888
2017-11-19 11:03:08,729 DEBUG    MQTT       Publishing: emon/emonpi/vrms 238.95
2017-11-19 11:03:08,734 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:08,737 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:08,739 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:08,742 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:08,745 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:08,749 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:08,752 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:08,755 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:08,758 INFO     MQTT       Publishing: emonhub/rx/5/values 1703,1185,2888,238.95,0,0,0,0,0,0,0
2017-11-19 11:03:08,761 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:09,669 DEBUG    MainThread SIGINT received.
2017-11-19 11:03:09,670 INFO     MainThread Exiting hub...
2017-11-19 11:03:09,903 INFO     MainThread Exit completed
2017-11-19 11:03:11,303 INFO     MainThread EmonHub emonHub emon-pi variant v2.0.0
2017-11-19 11:03:11,304 INFO     MainThread Opening hub...
2017-11-19 11:03:11,306 INFO     MainThread Logging level set to DEBUG
2017-11-19 11:03:11,307 INFO     MainThread Creating EmonHubJeeInterfacer 'RFM2Pi' 
2017-11-19 11:03:11,311 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2017-11-19 11:03:13,319 INFO     MainThread RFM2Pi device firmware version & configuration: not available
2017-11-19 11:03:13,320 INFO     MainThread Setting RFM2Pi frequency: 433 (4b)
2017-11-19 11:03:14,321 INFO     MainThread Setting RFM2Pi group: 210 (210g)
2017-11-19 11:03:15,324 INFO     MainThread Setting RFM2Pi quiet: 0 (0q)
2017-11-19 11:03:16,327 INFO     MainThread Setting RFM2Pi baseid: 5 (5i)
2017-11-19 11:03:17,329 INFO     MainThread Setting RFM2Pi calibration: 230V (1p)
2017-11-19 11:03:18,332 DEBUG    MainThread Setting RFM2Pi subchannels: ['ToRFM12']
2017-11-19 11:03:18,333 DEBUG    MainThread Setting RFM2Pi pubchannels: ['ToEmonCMS']
2017-11-19 11:03:18,336 INFO     MainThread Creating EmonHubMqttInterfacer 'MQTT' 
2017-11-19 11:03:18,343 INFO     MainThread MQTT Init mqtt_host=127.0.0.1 mqtt_port=1883 mqtt_user=emonpi
2017-11-19 11:03:18,357 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg' 
2017-11-19 11:03:18,409 DEBUG    RFM2Pi     1 NEW FRAME : OK 5 198 6 147 4 89 11 5 93 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:18,414 DEBUG    RFM2Pi     1 Timestamp : 1511089398.41
2017-11-19 11:03:18,415 DEBUG    RFM2Pi     1 From Node : 5
2017-11-19 11:03:18,416 DEBUG    RFM2Pi     1    Values : [1734, 1171, 2905, 238.13, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:18,416 DEBUG    RFM2Pi     1 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:18,417 DEBUG    RFM2Pi     1 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:18,457 INFO     MQTT       Connecting to MQTT Server
2017-11-19 11:03:18,462 INFO     MQTT       connection status: Connection successful
2017-11-19 11:03:18,465 DEBUG    MQTT       CONACK => Return code: 0
2017-11-19 11:03:18,521 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:03:18,568 INFO     MQTT       on_subscribe
2017-11-19 11:03:18,625 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:03:18,670 DEBUG    MQTT       Publishing: emon/emonpi/power1 1734
2017-11-19 11:03:18,673 DEBUG    MQTT       Publishing: emon/emonpi/power2 1171
2017-11-19 11:03:18,676 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2905
2017-11-19 11:03:18,678 DEBUG    MQTT       Publishing: emon/emonpi/vrms 238.13
2017-11-19 11:03:18,680 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:18,683 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:18,686 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:18,689 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:18,691 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:18,694 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:18,697 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:18,699 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:18,702 INFO     MQTT       Publishing: emonhub/rx/5/values 1734,1171,2905,238.13,0,0,0,0,0,0,0
2017-11-19 11:03:18,705 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:18,732 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:03:18,837 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:03:18,942 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0
2017-11-19 11:03:19,050 DEBUG    RFM2Pi     2 NEW FRAME : OK 5 160 6 121 5 25 12 26 93 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:19,054 DEBUG    RFM2Pi     2 Timestamp : 1511089399.05
2017-11-19 11:03:19,056 DEBUG    RFM2Pi     2 From Node : 5
2017-11-19 11:03:19,057 DEBUG    RFM2Pi     2    Values : [1696, 1401, 3097, 238.34, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:19,058 DEBUG    RFM2Pi     2 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:19,059 DEBUG    RFM2Pi     2 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:19,166 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 14 0 0 0 0 0 0 0 76 95 184 11 184 11 184 11 184 11 184 11 (-60)
2017-11-19 11:03:19,248 DEBUG    MQTT       Publishing: emon/emonpi/power1 1696
2017-11-19 11:03:19,251 DEBUG    MQTT       Publishing: emon/emonpi/power2 1401
2017-11-19 11:03:19,254 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3097
2017-11-19 11:03:19,256 DEBUG    MQTT       Publishing: emon/emonpi/vrms 238.34
2017-11-19 11:03:19,259 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:19,261 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:19,264 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:19,266 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:19,269 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:19,272 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:19,274 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:19,276 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:19,279 INFO     MQTT       Publishing: emonhub/rx/5/values 1696,1401,3097,238.34,0,0,0,0,0,0,0
2017-11-19 11:03:19,281 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:23,511 DEBUG    RFM2Pi     3 NEW FRAME : OK 5 191 6 137 4 72 11 247 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:23,515 DEBUG    RFM2Pi     3 Timestamp : 1511089403.51
2017-11-19 11:03:23,516 DEBUG    RFM2Pi     3 From Node : 5
2017-11-19 11:03:23,517 DEBUG    RFM2Pi     3    Values : [1727, 1161, 2888, 237.99, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:23,518 DEBUG    RFM2Pi     3 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:23,519 DEBUG    RFM2Pi     3 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:23,746 DEBUG    MQTT       Publishing: emon/emonpi/power1 1727
2017-11-19 11:03:23,748 DEBUG    MQTT       Publishing: emon/emonpi/power2 1161
2017-11-19 11:03:23,750 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 2888
2017-11-19 11:03:23,751 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.99
2017-11-19 11:03:23,753 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:23,754 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:23,756 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:23,757 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:23,758 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:23,759 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:23,761 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:23,762 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:23,764 INFO     MQTT       Publishing: emonhub/rx/5/values 1727,1161,2888,237.99,0,0,0,0,0,0,0
2017-11-19 11:03:23,765 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:28,540 DEBUG    RFM2Pi     4 NEW FRAME : OK 5 160 6 155 5 59 12 220 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:28,543 DEBUG    RFM2Pi     4 Timestamp : 1511089408.54
2017-11-19 11:03:28,543 DEBUG    RFM2Pi     4 From Node : 5
2017-11-19 11:03:28,544 DEBUG    RFM2Pi     4    Values : [1696, 1435, 3131, 237.72, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:28,545 DEBUG    RFM2Pi     4 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:28,545 DEBUG    RFM2Pi     4 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:28,636 DEBUG    MQTT       Publishing: emon/emonpi/power1 1696
2017-11-19 11:03:28,638 DEBUG    MQTT       Publishing: emon/emonpi/power2 1435
2017-11-19 11:03:28,640 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3131
2017-11-19 11:03:28,642 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.72
2017-11-19 11:03:28,644 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:28,646 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:28,649 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:28,653 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:28,656 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:28,659 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 14 0 0 0 0 0 0 0 45 95 184 11 184 11 184 11 184 11 184 11 (-60)
2017-11-19 11:03:28,660 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:28,663 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:28,665 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:28,668 INFO     MQTT       Publishing: emonhub/rx/5/values 1696,1435,3131,237.72,0,0,0,0,0,0,0
2017-11-19 11:03:28,670 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:33,502 DEBUG    RFM2Pi     5 NEW FRAME : OK 5 193 6 143 5 80 12 238 92 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:33,504 DEBUG    RFM2Pi     5 Timestamp : 1511089413.5
2017-11-19 11:03:33,505 DEBUG    RFM2Pi     5 From Node : 5
2017-11-19 11:03:33,506 DEBUG    RFM2Pi     5    Values : [1729, 1423, 3152, 237.9, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:33,506 DEBUG    RFM2Pi     5 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:33,507 DEBUG    RFM2Pi     5 Sent to channel(end)' : ToEmonCMS
2017-11-19 11:03:33,697 DEBUG    MQTT       Publishing: emon/emonpi/power1 1729
2017-11-19 11:03:33,699 DEBUG    MQTT       Publishing: emon/emonpi/power2 1423
2017-11-19 11:03:33,701 DEBUG    MQTT       Publishing: emon/emonpi/power1pluspower2 3152
2017-11-19 11:03:33,702 DEBUG    MQTT       Publishing: emon/emonpi/vrms 237.9
2017-11-19 11:03:33,703 DEBUG    MQTT       Publishing: emon/emonpi/t1 0
2017-11-19 11:03:33,705 DEBUG    MQTT       Publishing: emon/emonpi/t2 0
2017-11-19 11:03:33,706 DEBUG    MQTT       Publishing: emon/emonpi/t3 0
2017-11-19 11:03:33,707 DEBUG    MQTT       Publishing: emon/emonpi/t4 0
2017-11-19 11:03:33,709 DEBUG    MQTT       Publishing: emon/emonpi/t5 0
2017-11-19 11:03:33,710 DEBUG    MQTT       Publishing: emon/emonpi/t6 0
2017-11-19 11:03:33,712 DEBUG    MQTT       Publishing: emon/emonpi/pulsecount 0
2017-11-19 11:03:33,713 INFO     MQTT       Publishing: emon/emonpi/rssi 0
2017-11-19 11:03:33,715 INFO     MQTT       Publishing: emonhub/rx/5/values 1729,1423,3152,237.9,0,0,0,0,0,0,0
2017-11-19 11:03:33,716 INFO     MQTT       Publishing: emonhub/rx/5/rssi 0
2017-11-19 11:03:38,035 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 15 0 0 0 0 0 0 0 17 95 184 11 184 11 184 11 184 11 184 11 (-60)
2017-11-19 11:03:38,505 DEBUG    RFM2Pi     6 NEW FRAME : OK 5 195 6 149 4 88 11 11 93 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-0)
2017-11-19 11:03:38,508 DEBUG    RFM2Pi     6 Timestamp : 1511089418.51
2017-11-19 11:03:38,509 DEBUG    RFM2Pi     6 From Node : 5
2017-11-19 11:03:38,509 DEBUG    RFM2Pi     6    Values : [1731, 1173, 2904, 238.19, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 11:03:38,510 DEBUG    RFM2Pi     6 Sent to channel(start)' : ToEmonCMS
2017-11-19 11:03:38,510 DEBUG    RFM2Pi     6 Sent to channel(end)' : ToEmonCMS

Nicola_Reina · 19 November 2017 11:11

This is the initial sample …
Node emonpi 95MB 2s
Node weather 12MB inactive
Node emonTx_3 0B 35 mins
Id Tag Nome Process list Pubblico Tipo dato Motore Dim. Aggiornato Valore
58 … node:emonTx_3:power1 REALTIME PHPFINA n/a 35 mins 7 <<<<
59 … node:emonTx_3:rssi REALTIME PHPFINA n/a 35 mins -48 <<<<<

not reachable after first sample

pb66 · 19 November 2017 11:59

This info is significant. This is due to an unresolved issue on the emonPi, nothing to do with the emonTx. When adding new devices, the MQTT is correctly passed by emonhub and can be subscribed to by other services, BUT the emoncms mqtt_input isn’t able to create new emoncms inputs correctly from the new topics. Originally it was found it could be overcome by rebooting the emonPi, since then the debugging has narrowed and I believe you can now restart the emoncms mqtt_input service (not the Mosquitto MQTT broker) to get the new inputs to create correctly in emonmcs.

Of course the above will need to be done when you have data flowing from the emonTx, restarting the mqtt_input service cannot create new inputs it cannot see at the time. So we need to concentrate on getting the data flowing to emonhub from the emonTx.

The connection between the emonPi and emonhub is good as we see the node 5 data and the “unreliable content”, those discarded packets look pretty regular so at this point it looks like an issue between the emonTx preparing to send and the emonPi processing the received packet.

I assume the emonPi is fully updated, can you check the emonpi update log (I think it’s on the data partition (~/data) or post it here so we can check the emonPi add-on board FW was definitely updated.

If that is in order, then once your programmer arrives I think we should check and possibly reinstall the emonTx FW. Unless the payload is getting corrupted whilst airborne, either the emonPi or emonTx is doing the CRC bit wrong, so ensuring the FW’s on both are sound maybe a good place to start.

Wifi shouldn’t effect this unless you have devices on top of each other. The others I do not know about, if they are 433MHz you could try switching them off for a bit whilst viewing the emonHub.log (not emoncms inputs or feeds)

In the emonhub.log you can see

11:02:33,665 DEBUG    RFM2Pi     device settings updated: E i5 g210 @ 433 MHz q0 USA 0

This is the emonPi board confirming it’s status as node 5, group 210, freq 433MHz, quiet mode false and USA mode fasle, so we know the emonPi is configured. The emonTx currently only comes as 433, but without the programmer we cannot check or change it, normally if you mix 433 and 868 devices they will only work over a very short range (a few centimetres) so you could try moving the emontx to be right next to the emonPi to test, but I think the RSSI proves the emonTx is on 433MHz.

Sorry I do not recognize the content of your last post, but for now you must only look at emonhub.log, do not rely on emoncms inputs or feeds. Regardless of whether we fix the “unreliable content” the inputs are unlikely to show in emoncms until after the mqtt_input service is restarted which has to happen after the data is flowing reliably.

Nicola_Reina · 19 November 2017 18:00

Hi thanks for the support.

Here is the start end of eminpiupdate.log
start:

Starting emonPi Update >
via service-runner-update.sh
Service Runner update script V1.0.0
EUID: 1000
Argument: emonpi
Sat 18 Nov 05:03:29 UTC 2017
#############################################################

emonSD version: emonSD-07Nov16

emonSD base image check passed...continue update

#############################################################
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
git pull /home/pi/emonpi
* master
  wifiap
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:

bla bla bla

Restarting Services...
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter

Restarting openhab (via systemctl): openhab.service.


set log rotate config owner to root
Restarting Services...


Starting emonPi LCD service..

Filesystem is locked - Read Only access
type ' rpi-rw ' to unlock
Sat 18 Nov 05:05:21 UTC 2017


...................
emonPi update done

so emonpi fw is updated

the behaviour of the emontx is consistent: i.e. only the first sample after a power on or relaoad of the sketch (reset button) gets to the input then nothing more

usb uart shall be here in a couple of days

pb66 · 19 November 2017 18:13

You maybe able to see that, but what you have included here doesn’t show that. It probably in the section replaced with “bla bla bla”.

means the enonSD update (aka emonpi update) routine was started and it has now ended, it doesn’t tell us what was or wasn’t successful, for that we need the complete log.

As I have previously said, do not use the emoncms input page to assess what’s going on. Please view and post the emonhub.log until we know that part is fixed.

So please attach the complete update log and also rephrase or confirm your last comment, is the first transmission (or subsequent transmissions) from the emonTx seen in the emonHub log (NOT emoncms inputs)?

That first rssi input in emoncms is triggered by a succesful transmission being received in emonhub and publishing to MQTT, after that, we do not expect to see any further inputs at this stage, so the fact you only see one input it irelivent at this stage. We need to know what is happening in the emonhub.log at the time and for a period after you see that first update occur in emoncms.

Nicola_Reina · 19 November 2017 18:49

here is the full update log:

Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
I2C LCD DETECTED Ox27
Starting emonPi Update >
via service-runner-update.sh
Service Runner update script V1.0.0
EUID: 1000
Argument: emonpi
Sat 18 Nov 05:03:29 UTC 2017
#############################################################

emonSD version: emonSD-07Nov16

emonSD base image check passed...continue update

#############################################################
Filesystem is unlocked - Write access
type ' rpi-ro ' to lock
git pull /home/pi/emonpi
* master
  wifiap
On branch master
Your branch is up-to-date with 'origin/master'.
Untracked files:
  (use "git add <file>..." to include in what will be committed)

	1
	hardware/emonpi/emonpi2c/

nothing added to commit but untracked files present (use "git add" to track)
Already up-to-date.
git pull /home/pi/RFM2Pi
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.
git pull /home/pi/emonhub
  K0den-wibeee_interface
* emon-pi
  hmm01i-syslogging
On branch emon-pi
Your branch is up-to-date with 'origin/emon-pi'.
nothing to commit, working directory clean
Already up-to-date.
git pull /home/pi/oem_openHab
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
Already up-to-date.
git pull /home/pi/usefulscripts
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
git pull /home/pi/huawei-hilink-status
* master
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean

Start emonPi Atmega328 firmware update:

=================================
EmonPi update started
=================================

EUID: 1000

Collecting paho-mqtt
  Downloading paho-mqtt-1.3.1.tar.gz (80kB)
Building wheels for collected packages: paho-mqtt
  Running setup.py bdist_wheel for paho-mqtt: started
  Running setup.py bdist_wheel for paho-mqtt: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/20/d8/0d/acdc8f2890111b7be7de71deebef0642fb83be0313dfff0493
Successfully built paho-mqtt
Installing collected packages: paho-mqtt
  Found existing installation: paho-mqtt 1.3.0
    Uninstalling paho-mqtt-1.3.0:
      Successfully uninstalled paho-mqtt-1.3.0
Successfully installed paho-mqtt-1.3.1
Stopping OpenEnergyMonitor emonHub: emonhub has been stopped ok.
Start ATmega328 serial upload using avrdude with latest.hex
Discrete Sampling
avrdude -c arduino -p ATMEGA328P -P /dev/ttyAMA0 -b 115200 -U flash:w:/home/pi/emonpi/firmware/compiled/latest.hex
avrdude-original: Using autoreset DTR on GPIO Pin 7
Starting OpenEnergyMonitor emonHub: emonhub has been started ok.
[email protected] node_modules/node-red-node-emoncms


Start emonhub update script:

=================================
EmonPi update started
=================================
Running emonhub automatic node addition script
EUID: 1000
EUID: 1000
[[5]]
Node 5 already present
[[6]]
Node 6 already present
[[7]]
Node 7 already present
[[8]]
Node 8 already present
[[9]]
Node 9 already present
[[10]]
Node 10 already present
[[11]]
Node 11 already present
[[12]]
Node 12 already present
[[13]]
Node 13 already present
[[14]]
Node 14 already present
[[19]]
Node 19 already present
[[20]]
Node 20 already present
[[21]]
Node 21 already present
[[22]]
Node 22 already present
[[23]]
Node 23 already present
[[24]]
Node 24 already present
[[25]]
Node 25 already present
[[26]]
Node 26 already present

Start emoncms update:

=================================
Emoncms update started
Emoncms update script V1.1.1

Sat 18 Nov 05:04:30 UTC 2017

#############################################################

emonSD version: emonSD-07Nov16

emonSD base image check pass...continue update

#############################################################
EUID: 1000
Checking cron tab for service runner entry...
service runner crontab entry already installed

current settings.php md5: c000f614aacbb38d288f0e3dbe9cfb88
Default settings.php md5: c000f614aacbb38d288f0e3dbe9cfb88

git pull /var/www/emoncms
  dev-mosquitto-php
  master
* stable
  symlinked_modules
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.

NEW default settings.php md5: c000f614aacbb38d288f0e3dbe9cfb88
settings.php had NOT been user modifed
No update required to settings.php


git pull /var/www/emoncms/Modules/app
  9.0
* stable
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.

git pull /var/www/emoncms/Modules/config
  9.0
* stable
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.

git pull /var/www/emoncms/Modules/wifi
  9.0
* stable
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.
git pull /var/www/emoncms/Modules/dashboard
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.

git pull /var/www/emoncms/Modules/graph
  master
* stable
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.

git pull /home/pi/postprocess
Your branch is up-to-date with 'remotes/origin/emonpi'.
Already up-to-date.
git pull /home/pi/backup
  master
* stable
On branch stable
Your branch is up-to-date with 'origin/stable'.
nothing to commit, working directory clean
Already up-to-date.
Your branch is up-to-date with 'origin/stable'.

update mqtt_input systemd unit file

Update Emoncms database
[]

Restarting Services...
Restarting OpenEnergyMonitor emonHub: emonhub has been restarted ok.
Log is turned off
Restarting feedwriter

Restarting openhab (via systemctl): openhab.service.


set log rotate config owner to root
Restarting Services...


Starting emonPi LCD service..

Filesystem is locked - Read Only access
type ' rpi-rw ' to unlock
Sat 18 Nov 05:05:21 UTC 2017


...................
emonPi update done

Nicola_Reina · 19 November 2017 18:52

tonight I will reconnect the emontx to have a log of the startup phase.
The previous tests are not anymore in current log.
Do you want me to do any other manoeuvre apart turning it on and perhaps doing a restart from the gui?

TY again for your patience

Nicola_Reina · 19 November 2017 21:37

And Here Emonhub.log
It includes a restartfrom gui
and a couple of resets from button.
You can see the first samples from node 8 (circa at 22:28)

~~2017-11-19 22:25:51,992 INFO MQTT Publishing: emonhub/rx/5/rssi 0201 - Pastebin.com~~

~~I had to paste it in Pastebin as it is quite long~~

[Please attach files rather than link to 3rd party sites as if the 3rd party copy disappears it effects readability of this thread] emonhub.log.txt (135.7 KB)emonhub.zip (29.8 KB)

pb66 · 19 November 2017 22:54

I’m somewhat confused now!

From your emonhub.log earlier in the discussion

2017-11-19 11:03:28,659 DEBUG    RFM2Pi     Discarding RX frame 'unreliable content'? 8 14 0 0 0 0 0 0 0 45 95 184 11 184 11 184 11 184 11 184 11 (-60)

this line or very similar appears several times, The rssi is good at -60db (the last value, in brackets) and it’s from node 8 (the first value). One of the things I was looking for when looking for a clue as to why it failed CRS was the last few values immediately before the rssi, in this case 45 95 184 11 184 11 184 11 184 11 184 11.

The last few numbers tell me the firmware is the later type that passes unused temp sensor readings as a fault code of 300 ((11*256) + 184) which is a good thing because the original FW that passed these 6 pairs of values as zero’s was prone to “bitslip” (you can search the forums for more info on that if interested) causing CRC fails. So with the 11 184 s I was confident that wasn’t a possibility.

The 5th pair of values (after the node id) are 45 95 which seems to be a Vrms of 243.65.

From your latest emonhub.log

2017-11-19 22:29:14,546 DEBUG    RFM2Pi     15 NEW FRAME : OK 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (-70)
2017-11-19 22:29:14,549 DEBUG    RFM2Pi     15 Timestamp : 1511126954.55
2017-11-19 22:29:14,550 DEBUG    RFM2Pi     15 From Node : 8
2017-11-19 22:29:14,551 DEBUG    RFM2Pi     15    Values : [6, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2017-11-19 22:29:14,552 DEBUG    RFM2Pi     15      RSSI : -70

This “node8” has a slightly weaker signal at -70db, passes the CRC checks and is all zero’s (bar that first “6” watts, perhaps just one CT attached?)

The successful node8 payload is all zero’s (suggesting a different FW?) and the AC voltage reading (Vrms) is missing, if the AC:AC isn’t connected, how is it working? Must have batteries in it and the AC:AC wasn’t present at start-up. Although on batteries the RSSI might be weaker so it’s not impossible this is the same device, except the temp sensor values suggest otherwise. This wouldn’t explain why you are getting better results on battery than on AC:AC, unless the fact you have both is causing the problem.

And also from the same log

2017-11-19 22:29:43,156 DEBUG    RFM2Pi     26 NEW FRAME : OK 8 0 0 0 0 0 0 0 0 235 95 184 11 184 11 184 11 184 11 184 11 184 11 0 0 0 0 (-50)
2017-11-19 22:29:43,159 DEBUG    RFM2Pi     26 Timestamp : 1511126983.16
2017-11-19 22:29:43,160 DEBUG    RFM2Pi     26 From Node : 8
2017-11-19 22:29:43,161 DEBUG    RFM2Pi     26    Values : [0, 0, 0, 0, 245.55, 300, 300, 300, 300, 300, 300, 0]
2017-11-19 22:29:43,162 DEBUG    RFM2Pi     26      RSSI : -50

Which is totally correct and an even stronger rssi of -50db

How many emonTx’s do you have?
Is there a possibility a neighbor has an emonTx?
How many CT’s do you have connected to your emonTx?
Do you have batteries in your emonTx?

Please confirm also are you reseting the emonPi or the emonTx? and what are you “restarting from gui”?

Please ensure you do not have batteries in the emonTx and try again, with the AC:AC adapter only. The emonTx only checks for an AC:AC signal at start up so if you have both batteries and AC:AC, when you turn off the AC and reset the emonTx it will restart imediatly on the batteries and not find the AC signal, switching the AC:AC on after it has booted will have on effect, likewise with CT’s, they must be connected before boot up (powering up or reset).

I will try and check the FW to see if it’s possible the temp sensor readings are still sent as zero’s when battery powered, (unless @Robert.Wall knows this offhand?)

Robert.Wall · 19 November 2017 23:14

I didn’t think the power source affected anything other than using the real or assumed voltage to calculate power or apparent power (when it sends the battery voltage instead of the a.c. voltage, and flashing the LED. (And it sleeps rather than delays - but that’s not visible.)

I can’t see anything in the sketch to affect temperatures depending on the power source, and I don’t think there ever has been anything.

Nicola_Reina · 20 November 2017 14:09

If you see the timestamp this was at a different time and different location (just a few meters away).

This “node8” has a slightly weaker signal at -70db, passes the CRC checks and is all zero’s (bar that first “6” watts, perhaps just one CT attached?)
Yes just one ct attached on CT1 (I think it was the AC-AC itself).
No Batteries in the EmonTx
AC:AC is connected
Just one EmonTx in house (for now)
ONe CT (CT1) connected
No Batteries

I will do a clean restart of PI an power up of emontx and take the log
Restarting from GUI : I mean pushing the restart button in the emonhub viewlog web gui (triggering a sigint in the log)

As said I will post a emonhub log and try to give you the timestamps of events I do (rebooting pi, connecting emontx etc…)

pb66 · 20 November 2017 15:05

I would recommend switching the node id DIP switch too so that you are using a different node id just to be sure something isn’t isn’t parading as node 8.

I struggle to see how a device with no voltage reading has power to operate and how a device with FW sending 184 11 in place of missing temp sensors suddenly sends all zeros.

I understand they are at different times, I wasn’t aware you were moving it around. perhaps you could place it right next to the emonPi until we gain some ground?

Nicola_Reina · 20 November 2017 16:05

Ok near to the emonpi is not possible.
I will test from the same place.
Could you point me to the DIP switch location on the board? I would not like to damage it.
TX

pb66 · 20 November 2017 16:17

https://wiki.openenergymonitor.org/index.php/EmonTx_V3.4#DIP_Switch_Config

The tricky bit can be getting the plastic film off, it’s like a piece of (orange?) sellotape on the switches that needs removing to get at the switches.

Nicola_Reina · 20 November 2017 16:19

Yep this is why I asked : I could see it but that did not look like a dip switch: it is the (black tape on it)

Nicola_Reina · 20 November 2017 20:33

Ok. Removed sealing (orange indeed) and moved dipswitch.
I first rebooted the pi (around 22:24)
Then I powered the emontx (AC:AC , no batteries, load on CT1 (pc ps)).
Same behaviour as for node 9.
First sample ok then nothing.
The log is attached

I also pushed once the reset button of the emontx : same behaviour first sample then nothing

emonhub_new.zip (11.8 KB)