emonPi can't find emonTx

junhong.liang · 2016-12-15T09:49:26.027Z

Hello everybody,

so I was experimenting with emonPi and emonTx. I got 2 emonPis and 1 emonTx, which were ordered by another guy before me, so I don’t really know the details of these devices. I managed to use 1 emonPi to find the emonTx. However, when I tried to use anothere emonPi, the emonTx node never shows up. I was confused because I was doing the exact same thing with these two emonPis. I have been searching for the answer but it seems that no one was experiencing the same problem. So I thought I would ask you guys about the cause of this problem. Could it be that some models of emonPi do not support connection with emonTx? If you guys need any information, please inform me, because I don’t know what kind of information would be helpful to you. Thank you very much!

Junhong

Robert.Wall · 2016-12-15T10:51:19.597Z

What has [quote=“junhong.liang, post:1, topic:2513”]
another guy before me
[/quote]

done to the second emonPi?

We do not know what state it is in. I suggest you download the latest version of the software and write it to the SD card, so you will know that you have a good point to start from.

One other check - is everything working on the same radio frequency? All should be 433 MHz - if you open the cases and look at the radio modules and compare each with these pictures, you can check which you have.

glyn.hudson · 2016-12-15T12:08:54.469Z

Do you know the OpenEnergyMonitor shop order number? Or the date of the order? We could try and help you find out if there was any custom config involved. The emonTx config can be read by using a USB to UART cable to view the serial debug output at startup @9600 baud or @115200 (on newer units)

It would help if you posted a copy of your emonhub.conf and emonhub.log from both emonPi’s for us to be able to check the config.

junhong.liang · 2016-12-15T13:47:55.605Z

@Robert.Wall, @glyn.hudson, thank you very much for your quick replies. I did ask the guy before me and he said nothing was changed. So they both should have the original system (built 03 May 2016). And I don’t have the proper tool to open the case, so I can’t check the RF module right now.

After a couple more tries, the emonPi did manage to recognize the Node emontx3. However, it still gets no data from emonTx.

screen.jpg1881×823 111 KB

I check the emonhub.conf, they are the same for both devices:

#######################################################################
#######################      emonhub.conf     #########################
#######################################################################
### emonHub configuration file, for info see documentation:
### http://github.com/openenergymonitor/emonhub/blob/emon-pi/configuration.md
#######################################################################
#######################    emonHub  settings    #######################
#######################################################################

[hub]
### loglevel must be one of DEBUG, INFO, WARNING, ERROR, and CRITICAL
loglevel = DEBUG
# 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
    [[[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 = emonpi
        mqtt_passwd = emonpimqtt2016

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

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

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


[nodes]

## See config user guide: http://github.com/openenergymonitor/emonhub/blob/master/configuration.md   ##

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

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

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

junhong.liang · 2016-12-15T13:49:29.252Z

Log from the good emonPi:

2016-11-23 09:31:53,129 INFO     RFM2Pi     Publishing: emon/emontx3/temp3 300
2016-11-23 09:31:53,130 INFO     RFM2Pi     Publishing: emon/emontx3/temp4 300
2016-11-23 09:31:53,132 INFO     RFM2Pi     Publishing: emon/emontx3/temp5 300
2016-11-23 09:31:53,133 INFO     RFM2Pi     Publishing: emon/emontx3/temp6 300
2016-11-23 09:31:53,134 INFO     RFM2Pi     Publishing: emon/emontx3/pulse 1
2016-11-23 09:31:53,136 INFO     RFM2Pi     Publishing: emon/emontx3/rssi -48
2016-11-23 09:31:53,137 INFO     RFM2Pi     Publishing: emonhub/rx/8/values 0,0,0,0,260.63,300,300,300,300,300,300,1
2016-11-23 09:31:53,139 INFO     RFM2Pi     Publishing: emonhub/rx/8/rssi -48
2016-11-23 09:31:53,141 DEBUG    RFM2Pi     216 adding frame to buffer => [1479893513, 8, 0, 0, 0, 0, 260.63, 300, 300, 300, 300, 300, 300, 1, -48]
2016-11-23 09:31:53,141 DEBUG    RFM2Pi     216 Sent to channel' : ToEmonCMS
2016-11-23 09:31:53,649 DEBUG    RFM2Pi     217 NEW FRAME : OK 5 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)
2016-11-23 09:31:53,652 DEBUG    RFM2Pi     217 Timestamp : 1479893513.65
2016-11-23 09:31:53,652 DEBUG    RFM2Pi     217 From Node : 5
2016-11-23 09:31:53,653 DEBUG    RFM2Pi     217    Values : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2016-11-23 09:31:53,654 INFO     RFM2Pi     Publishing: emon/emonpi/power1 0
2016-11-23 09:31:53,655 INFO     RFM2Pi     Publishing: emon/emonpi/power2 0
2016-11-23 09:31:53,657 INFO     RFM2Pi     Publishing: emon/emonpi/power1pluspower2 0
2016-11-23 09:31:53,658 INFO     RFM2Pi     Publishing: emon/emonpi/vrms 0
2016-11-23 09:31:53,660 INFO     RFM2Pi     Publishing: emon/emonpi/t1 0
2016-11-23 09:31:53,661 INFO     RFM2Pi     Publishing: emon/emonpi/t2 0
2016-11-23 09:31:53,662 INFO     RFM2Pi     Publishing: emon/emonpi/t3 0
2016-11-23 09:31:53,664 INFO     RFM2Pi     Publishing: emon/emonpi/t4 0
2016-11-23 09:31:53,665 INFO     RFM2Pi     Publishing: emon/emonpi/t5 0
2016-11-23 09:31:53,666 INFO     RFM2Pi     Publishing: emon/emonpi/t6 0
2016-11-23 09:31:53,668 INFO     RFM2Pi     Publishing: emon/emonpi/pulsecount 0
2016-11-23 09:31:53,669 INFO     RFM2Pi     Publishing: emon/emonpi/rssi 0
2016-11-23 09:31:53,671 INFO     RFM2Pi     Publishing: emonhub/rx/5/values 0,0,0,0,0,0,0,0,0,0,0
2016-11-23 09:31:53,672 INFO     RFM2Pi     Publishing: emonhub/rx/5/rssi 0
2016-11-23 09:31:53,674 DEBUG    RFM2Pi     217 adding frame to buffer => [1479893513, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2016-11-23 09:31:53,674 DEBUG    RFM2Pi     217 Sent to channel' : ToEmonCMS

Log from the bad emonPi:

2016-12-15 13:05:20,639 INFO     RFM2Pi     Publishing: emon/emonpi/t3 0
2016-12-15 13:05:20,640 INFO     RFM2Pi     Publishing: emon/emonpi/t4 0
2016-12-15 13:05:20,642 INFO     RFM2Pi     Publishing: emon/emonpi/t5 0
2016-12-15 13:05:20,643 INFO     RFM2Pi     Publishing: emon/emonpi/t6 0
2016-12-15 13:05:20,644 INFO     RFM2Pi     Publishing: emon/emonpi/pulsecount 0
2016-12-15 13:05:20,645 INFO     RFM2Pi     Publishing: emon/emonpi/rssi 0
2016-12-15 13:05:20,647 INFO     RFM2Pi     Publishing: emonhub/rx/5/values 0,0,0,0,0,0,0,0,0,0,0
2016-12-15 13:05:20,648 INFO     RFM2Pi     Publishing: emonhub/rx/5/rssi 0
2016-12-15 13:05:20,649 DEBUG    RFM2Pi     116 adding frame to buffer => [1481807120, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2016-12-15 13:05:20,650 DEBUG    RFM2Pi     116 Sent to channel' : ToEmonCMS
2016-12-15 13:05:25,653 DEBUG    RFM2Pi     117 NEW FRAME : OK 5 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)
2016-12-15 13:05:25,656 DEBUG    RFM2Pi     117 Timestamp : 1481807125.65
2016-12-15 13:05:25,657 DEBUG    RFM2Pi     117 From Node : 5
2016-12-15 13:05:25,658 DEBUG    RFM2Pi     117    Values : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2016-12-15 13:05:25,659 INFO     RFM2Pi     Publishing: emon/emonpi/power1 0
2016-12-15 13:05:25,660 INFO     RFM2Pi     Publishing: emon/emonpi/power2 0
2016-12-15 13:05:25,661 INFO     RFM2Pi     Publishing: emon/emonpi/power1pluspower2 0
2016-12-15 13:05:25,662 INFO     RFM2Pi     Publishing: emon/emonpi/vrms 0
2016-12-15 13:05:25,663 INFO     RFM2Pi     Publishing: emon/emonpi/t1 0
2016-12-15 13:05:25,665 INFO     RFM2Pi     Publishing: emon/emonpi/t2 0
2016-12-15 13:05:25,666 INFO     RFM2Pi     Publishing: emon/emonpi/t3 0
2016-12-15 13:05:25,667 INFO     RFM2Pi     Publishing: emon/emonpi/t4 0
2016-12-15 13:05:25,668 INFO     RFM2Pi     Publishing: emon/emonpi/t5 0
2016-12-15 13:05:25,669 INFO     RFM2Pi     Publishing: emon/emonpi/t6 0
2016-12-15 13:05:25,671 INFO     RFM2Pi     Publishing: emon/emonpi/pulsecount 0
2016-12-15 13:05:25,672 INFO     RFM2Pi     Publishing: emon/emonpi/rssi 0
2016-12-15 13:05:25,673 INFO     RFM2Pi     Publishing: emonhub/rx/5/values 0,0,0,0,0,0,0,0,0,0,0
2016-12-15 13:05:25,674 INFO     RFM2Pi     Publishing: emonhub/rx/5/rssi 0
2016-12-15 13:05:25,675 DEBUG    RFM2Pi     117 adding frame to buffer => [1481807125, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
2016-12-15 13:05:25,676 DEBUG    RFM2Pi     117 Sent to channel' : ToEmonCMS

pb66 · 2016-12-15T14:19:49.496Z

Can you post a longer log from the emonPi that isn’t receiving the emonTx? This log is only 5s long and the emonTx posts every 10s. If you can post a minute or so that should be sufficient if the devices are fairly close to each other and it’s unlikely one emonPi is subject to range or interference issues.

The specific area to check in the emonhub.conf’s is

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

is this exactly the same in both?

junhong.liang · 2016-12-15T14:37:53.921Z

Hi Paul,

thanks for your reply. Could you tell me how to get a longer log? I copy this log from the EmonHub (the automatically refresh textfield). But I have been watching it for quite a while, and I don’t see it publishing information from emontx3 (unlike the good one, which did publish information from emontx3).

For the configuration, they are both the same, I put both files in a text compare software to check.

glyn.hudson · 2016-12-15T14:49:36.755Z

Try updating the emonPi’s by clicking on Admin > Update emonPi in local Emoncms.

The update may fix the issue and will also allow you to download the full emonhub log by clicking the download log button:

junhong.liang · 2016-12-16T12:07:14.661Z

Hi Glyn, I tried to update the software and it works now! So I guess it’s just some old software issue? Thank you for your reply!