EmonHub not parsing RFM69pi values

emonHub
1

Hi Everyone.

I need advise about the following problem.

I have a emonhub config that looks like the following:

#######################################################################
#######################      emonhub.conf     #########################
#######################################################################
### emonHub configuration file, for info see documentation:
### https://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
    autoconf = 0
    ### Uncomment this to also send to syslog
    use_syslog = yes
#######################################################################
#######################       Interfacers       #######################
#######################################################################

[interfacers]
    ### This interfacer manages the RFM12Pi/RFM69Pi/emonPi module
    [[EmonPi2]]
        Type = EmonHubOEMInterfacer
        [[[init_settings]]]
            com_port = /dev/ttyAMA0
            com_baud = 38400
        [[[runtimesettings]]]
            pubchannels = ToEmonCMS
            subchannels = ToRFM12
            frequency = 433
            group = 210
            baseid = 11    # emonPi / emonBase nodeID
            #quiet = true                            # Report incomplete RF packets (no implemented on emonPi)
            calibration = 230V    # (UK/EU: 230V, US: 110V)
    
    
    
    [[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 = 0
            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/
            
            # Single JSON payload published  - use with Emoncms MQTT
            node_JSON_enable = 0
            node_JSON_basetopic = emon/
    
    [[emoncmsorg]]
        Type = EmonHubEmoncmsHTTPInterfacer
        [[[init_settings]]]
        [[[runtimesettings]]]
            pubchannels = ToRFM12,
            subchannels = ToEmonCMS,
            url = http://192.168.68.111
            apikey = 653588bd9818c2576bf28b8c40dd4ff3
            senddata = 1    # Enable sending data to Emoncms.org
            sendnames = 1    # Send full input names (compression will be automatically enabled)
            interval = 30    # Bulk send interval to Emoncms.org in seconds

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

## See config user guide: https://github.com/openenergymonitor/emonhub
## If autoconf is enabled above, node configuration will automatically
## populate based on templates listed in available.conf
[nodes]
    [[11]]
        nodename = emontx3_3phase_11
        [[[rx]]]
            names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
            datacodes = h, h, h, h, h, h, h, h, h, h, h, L
            scales = 1.0, 1.0, 1.0, 1.0, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 1.0
            units = W, W, W, W, V, C, C, C, C, C, C, p

Emonhub appears to fail to map the values posted from a EmonTX V3 unit. It appears that it also attempts to retransmit the values.

Below is EmonHub’s log

2024-01-07 21:52:57,469 DEBUG    EmonPi2    Current configuration:
2024-01-07 21:52:57,573 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1
2024-01-07 21:53:02,999 DEBUG    EmonPi2    3121 NEW FRAME : OK 11 6 0 7 0 2 0 0 0 35 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-49)
2024-01-07 21:53:03,001 DEBUG    EmonPi2    3121 Timestamp : 1704664382.999017
2024-01-07 21:53:03,002 DEBUG    EmonPi2    3121 From Node : 11
2024-01-07 21:53:03,003 DEBUG    EmonPi2    3121    Values : [6, 7, 2, 0, 118.11, 30, 30, 30, 30, 30, 30, 4]
2024-01-07 21:53:03,004 DEBUG    EmonPi2    3121      RSSI : -49
2024-01-07 21:53:03,005 DEBUG    EmonPi2    3121 Sent to channel(start)' : T
2024-01-07 21:53:03,006 DEBUG    EmonPi2    3121 Sent to channel(end)' : T
2024-01-07 21:53:03,007 DEBUG    EmonPi2    3121 Sent to channel(start)' : o
2024-01-07 21:53:03,008 DEBUG    EmonPi2    3121 Sent to channel(end)' : o
2024-01-07 21:53:03,008 DEBUG    EmonPi2    3121 Sent to channel(start)' : E
2024-01-07 21:53:03,009 DEBUG    EmonPi2    3121 Sent to channel(end)' : E
2024-01-07 21:53:03,010 DEBUG    EmonPi2    3121 Sent to channel(start)' : m
2024-01-07 21:53:03,010 DEBUG    EmonPi2    3121 Sent to channel(end)' : m
2024-01-07 21:53:03,012 DEBUG    EmonPi2    3121 Sent to channel(start)' : o
2024-01-07 21:53:03,013 DEBUG    EmonPi2    3121 Sent to channel(end)' : o
2024-01-07 21:53:03,013 DEBUG    EmonPi2    3121 Sent to channel(start)' : n
2024-01-07 21:53:03,014 DEBUG    EmonPi2    3121 Sent to channel(end)' : n
2024-01-07 21:53:03,015 DEBUG    EmonPi2    3121 Sent to channel(start)' : C
2024-01-07 21:53:03,016 DEBUG    EmonPi2    3121 Sent to channel(end)' : C
2024-01-07 21:53:03,017 DEBUG    EmonPi2    3121 Sent to channel(start)' : M
2024-01-07 21:53:03,018 DEBUG    EmonPi2    3121 Sent to channel(end)' : M
2024-01-07 21:53:03,018 DEBUG    EmonPi2    3121 Sent to channel(start)' : S
2024-01-07 21:53:03,019 DEBUG    EmonPi2    3121 Sent to channel(end)' : S
2024-01-07 21:53:03,121 DEBUG    EmonPi2    3121 sent TX packet: T11,6,0,7,0,2,0,0,0,118,0,30,0,30,0,30,0,30,0,30,0,30,0,4,0,
2024-01-07 21:53:03,123 DEBUG    EmonPi2    3121 sent TX packet: T11,6,0,7,0,2,0,0,0,118,0,30,0,30,0,30,0,30,0,30,0,30,0,4,0,
2024-01-07 21:53:03,124 DEBUG    EmonPi2    3121 sent TX packet: T11,6,0,7,0,2,0,0,0,118,0,30,0,30,0,30,0,30,0,30,0,30,0,4,0,
2024-01-07 21:53:03,126 DEBUG    EmonPi2    3121 sent TX packet: T11,6,0,7,0,2,0,0,0,118,0,30,0,30,0,30,0,30,0,30,0,30,0,4,0,
2024-01-07 21:53:03,330 DEBUG    EmonPi2    Available commands:
2024-01-07 21:53:03,436 DEBUG    EmonPi2    <nn> i     - set node ID (standard node ids are 1..30)
2024-01-07 21:53:03,542 DEBUG    EmonPi2    <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
2024-01-07 21:53:03,650 DEBUG    EmonPi2    <nnnn> o   - change frequency offset within the band (default 1600)
2024-01-07 21:53:03,757 DEBUG    EmonPi2    96..3903 is the range supported by the RFM12B
2024-01-07 21:53:03,864 DEBUG    EmonPi2    <nnn> g    - set network group (RFM12 only allows 212, 0 = any)
2024-01-07 21:53:03,969 DEBUG    EmonPi2    <n> c      - set collect mode (advanced, normally 0)
2024-01-07 21:53:04,076 DEBUG    EmonPi2    t          - broadcast max-size test packet, request ack
2024-01-07 21:53:04,183 DEBUG    EmonPi2    ...,<nn> a - send data packet to node <nn>, request ack
2024-01-07 21:53:04,288 DEBUG    EmonPi2    ...,<nn> s - send data packet to node <nn>, no ack
2024-01-07 21:53:04,395 DEBUG    EmonPi2    <n> q      - set quiet mode (1 = don't report bad packets)
2024-01-07 21:53:04,502 DEBUG    EmonPi2    <n> x      - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2024-01-07 21:53:04,610 DEBUG    EmonPi2    <nnn> y    - enable signal strength trace mode, default:0 (disabled)
2024-01-07 21:53:04,717 DEBUG    EmonPi2    sample interval <nnn> secs/100 (0.01s-2.5s) eg 10y=0.1s
2024-01-07 21:53:04,825 DEBUG    EmonPi2    123 z      - total power down, needs a reset to start up again
2024-01-07 21:53:04,928 DEBUG    EmonPi2    Remote control commands:
2024-01-07 21:53:05,035 DEBUG    EmonPi2    <hchi>,<hclo>,<addr>,<cmd> f     - FS20 command (868 MHz)
2024-01-07 21:53:05,140 DEBUG    EmonPi2    <addr>,<dev>,<on> k              - KAKU command (433 MHz)
2024-01-07 21:53:05,244 DEBUG    EmonPi2    Current configuration:
2024-01-07 21:53:05,347 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1
2024-01-07 21:53:05,550 DEBUG    EmonPi2    Available commands:
2024-01-07 21:53:05,654 DEBUG    EmonPi2    <nn> i     - set node ID (standard node ids are 1..30)
2024-01-07 21:53:05,759 DEBUG    EmonPi2    <n> b      - set MHz band (4 = 433, 8 = 868, 9 = 915)
2024-01-07 21:53:05,864 DEBUG    EmonPi2    <nnnn> o   - change frequency offset within the band (default 1600)
2024-01-07 21:53:05,969 DEBUG    EmonPi2    96..3903 is the range supported by the RFM12B
2024-01-07 21:53:06,074 DEBUG    EmonPi2    <nnn> g    - set network group (RFM12 only allows 212, 0 = any)
2024-01-07 21:53:06,179 DEBUG    EmonPi2    <n> c      - set collect mode (advanced, normally 0)
2024-01-07 21:53:06,284 DEBUG    EmonPi2    t          - broadcast max-size test packet, request ack
2024-01-07 21:53:06,389 DEBUG    EmonPi2    ...,<nn> a - send data packet to node <nn>, request ack
2024-01-07 21:53:06,493 DEBUG    EmonPi2    ...,<nn> s - send data packet to node <nn>, no ack
2024-01-07 21:53:06,598 DEBUG    EmonPi2    <n> q      - set quiet mode (1 = don't report bad packets)
2024-01-07 21:53:06,704 DEBUG    EmonPi2    <n> x      - set reporting format (0: decimal, 1: hex, 2: hex+ascii)
2024-01-07 21:53:06,810 DEBUG    EmonPi2    <nnn> y    - enable signal strength trace mode, default:0 (disabled)
2024-01-07 21:53:06,916 DEBUG    EmonPi2    sample interval <nnn> secs/100 (0.01s-2.5s) eg 10y=0.1s
2024-01-07 21:53:07,021 DEBUG    EmonPi2    123 z      - total power down, needs a reset to start up again
2024-01-07 21:53:07,124 DEBUG    EmonPi2    Remote control commands:
2024-01-07 21:53:07,230 DEBUG    EmonPi2    <hchi>,<hclo>,<addr>,<cmd> f     - FS20 command (868 MHz)
2024-01-07 21:53:07,334 DEBUG    EmonPi2    <addr>,<dev>,<on> k              - KAKU command (433 MHz)
2024-01-07 21:53:07,437 DEBUG    EmonPi2    Current configuration:
2024-01-07 21:53:07,540 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1

For whatever reason, the logs also contain a list of “Available Commands” as if the character ‘?’ was sent to RFM69pi.

Any assistance will be appreciated.

Thanks and Regards.

2

I am certain that the radio of the EmonTx is transmitting and its packets are being received by RFM69pi

The following is an extract from the serial monitor log.

service-runner trigger sent for '/var/www/emoncms/scripts/serialmonitor/start.sh 38400 /dev/ttyAMA0'

[RF12demo.14] K i11 g210 @ 433 MHz q1

[RF12demo.14] K i11 g210 @ 433 MHz q1
OK 11 7 0 7 0 1 0 0 0 43 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-50)
OK 11 6 0 7 0 3 0 0 0 30 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-49)
OK 11 6 0 7 0 2 0 0 0 28 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-49)
OK 11 6 0 5 0 1 0 0 0 21 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-49)
OK 11 6 0 7 0 2 0 0 0 28 46 184 11 184 11 184 11 184 11 184 11 184 11 4 0 0 0 (-50)

The programmer USB cable is also unplugged.

3

For anyone wondering this is linked to this question emonSD-10Nov22 (Stable) and EmonTX V34

@BuciboLebo - not sure why you started a new thread.

I suggest you explain what hardware you have and how you got to this point. Has it ever worked? If so what has changed?

4

Good Day.

I previously used emonESP but then has since become unusable hence the switch to RFM69pi.

I am posting from a EmonTX V3.

This is how far I am currently.

The following is my emonhub config


#######################################################################
#######################      emonhub.conf     #########################
#######################################################################
### emonHub configuration file, for info see documentation:
### https://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
    [[EmonPi2]]
        Type = EmonHubOEMInterfacer
        [[[init_settings]]]
            com_port = /dev/ttyAMA0
            com_baud = 38400
        [[[runtimesettings]]]
            pubchannels = ToEmonCMS
            # subchannels = ToRFM12
            frequency = 433
            group = 210
            baseid = 11    # emonPi / emonBase nodeID
            quiet = true                            # Report incomplete RF packets (no implemented on emonPi)
            calibration = 230V    # (UK/EU: 230V, US: 110V)
        
    [[emoncmsorg]]
        Type = EmonHubEmoncmsHTTPInterfacer
        [[[init_settings]]]
        [[[runtimesettings]]]
            # pubchannels = ToRFM12,
            subchannels = ToEmonCMS,
            url = http://192.168.68.111
            apikey = 653588bd9818c2576bf28b8c40dd4ff3
            sendstatus = 1
            senddata = 1    # Enable sending data to Emoncms.org
            sendnames = 1    # Send full input names (compression will be automatically enabled)
            interval = 30    # Bulk send interval to Emoncms.org in seconds
#######################################################################
#######################          Nodes          #######################
#######################################################################

## See config user guide: https://github.com/openenergymonitor/emonhub
## If autoconf is enabled above, node configuration will automatically
## populate based on templates listed in available.conf
[nodes]
        [[11]]
        nodename = emontx3_3phase_11
        [[[rx]]]
            names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
            datacodes = h, h, h, h, h, h, h, h, h, h, h, L
            scales = 1.0, 1.0, 1.0, 1.0, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 1.0
            units = W, W, W, W, V, C, C, C, C, C, C, p

The following are the contents of the emonhub logs.

2024-01-08 14:44:28,422 DEBUG    MainThread Signal 15 received.
2024-01-08 14:44:28,575 INFO     MainThread Exiting hub...
2024-01-08 14:44:28,777 INFO     MainThread Exit completed
2024-01-08 14:44:30,232 INFO     MainThread EmonHub v2.6.2
2024-01-08 14:44:30,234 INFO     MainThread Opening hub...
2024-01-08 14:44:30,234 INFO     MainThread Running as user: pi
2024-01-08 14:44:30,235 INFO     MainThread Logging level set to DEBUG
2024-01-08 14:44:30,236 INFO     MainThread Creating EmonHubOEMInterfacer 'EmonPi2'
2024-01-08 14:44:30,238 DEBUG    MainThread Opening serial port: /dev/ttyAMA0 @ 38400 bits/s
2024-01-08 14:44:30,239 INFO     MainThread Creating EmonHubEmoncmsHTTPInterfacer 'emoncmsorg'
2024-01-08 14:44:30,241 DEBUG    MainThread Setting emoncmsorg interval: 30
2024-01-08 14:44:30,242 DEBUG    MainThread Setting emoncmsorg subchannels: ['ToEmonCMS']
2024-01-08 14:44:30,242 INFO     MainThread Setting emoncmsorg apikey: set
2024-01-08 14:44:30,243 INFO     MainThread Setting emoncmsorg url: http://192.168.68.111
2024-01-08 14:44:30,243 INFO     MainThread Setting emoncmsorg senddata: 1
2024-01-08 14:44:30,244 INFO     MainThread Setting emoncmsorg sendstatus: 0
2024-01-08 14:44:30,244 INFO     MainThread Setting emoncmsorg sendnames: 1
2024-01-08 14:44:30,245 INFO     MainThread Setting emoncmsorg compress: 0
2024-01-08 14:44:30,246 DEBUG    MainThread Automatic configuration of nodes disabled
2024-01-08 14:44:34,859 DEBUG    EmonPi2    ---------------------------------------------------------------------
2024-01-08 14:44:34,863 DEBUG    EmonPi2    Config format: old
2024-01-08 14:44:34,874 DEBUG    EmonPi2    CONFIG SET:group        cmd:210g            reply:[RF12demo.14] K i11 g210 @ 433 MHz q1
2024-01-08 14:44:34,876 DEBUG    EmonPi2    CONFIG SET:frequency    cmd:433b            reply:> 210g
2024-01-08 14:44:34,952 DEBUG    EmonPi2    CONFIG SET:baseid       cmd:11i             reply:K i11 g210 @ 433 MHz q1
2024-01-08 14:44:34,953 DEBUG    EmonPi2    ---------------------------------------------------------------------
2024-01-08 14:44:35,054 DEBUG    EmonPi2    > 433b
2024-01-08 14:44:35,155 DEBUG    EmonPi2    > 11i
2024-01-08 14:44:35,257 DEBUG    EmonPi2    K i11 g210 @ 433 MHz q1
2024-01-08 14:44:44,712 DEBUG    EmonPi2    5 NEW FRAME : OK 11 5 0 7 0 2 0 0 0 186 44 184 11 184 11 184 11 184 11 184 11 184 11 79 0 0 0 (-54)
2024-01-08 14:44:44,715 DEBUG    EmonPi2    5 Timestamp : 1704725084.712159
2024-01-08 14:44:44,716 DEBUG    EmonPi2    5 From Node : 11
2024-01-08 14:44:44,717 DEBUG    EmonPi2    5    Values : [5, 7, 2, 0, 114.5, 30, 30, 30, 30, 30, 30, 79]
2024-01-08 14:44:44,719 DEBUG    EmonPi2    5      RSSI : -54
2024-01-08 14:44:44,719 DEBUG    EmonPi2    5 Sent to channel(start)' : T
2024-01-08 14:44:44,720 DEBUG    EmonPi2    5 Sent to channel(end)' : T
2024-01-08 14:44:44,721 DEBUG    EmonPi2    5 Sent to channel(start)' : o
2024-01-08 14:44:44,722 DEBUG    EmonPi2    5 Sent to channel(end)' : o
2024-01-08 14:44:44,723 DEBUG    EmonPi2    5 Sent to channel(start)' : E
2024-01-08 14:44:44,724 DEBUG    EmonPi2    5 Sent to channel(end)' : E
2024-01-08 14:44:44,725 DEBUG    EmonPi2    5 Sent to channel(start)' : m
2024-01-08 14:44:44,726 DEBUG    EmonPi2    5 Sent to channel(end)' : m
2024-01-08 14:44:44,727 DEBUG    EmonPi2    5 Sent to channel(start)' : o
2024-01-08 14:44:44,728 DEBUG    EmonPi2    5 Sent to channel(end)' : o
2024-01-08 14:44:44,728 DEBUG    EmonPi2    5 Sent to channel(start)' : n
2024-01-08 14:44:44,729 DEBUG    EmonPi2    5 Sent to channel(end)' : n
2024-01-08 14:44:44,730 DEBUG    EmonPi2    5 Sent to channel(start)' : C
2024-01-08 14:44:44,731 DEBUG    EmonPi2    5 Sent to channel(end)' : C
2024-01-08 14:44:44,732 DEBUG    EmonPi2    5 Sent to channel(start)' : M
2024-01-08 14:44:44,733 DEBUG    EmonPi2    5 Sent to channel(end)' : M
2024-01-08 14:44:44,734 DEBUG    EmonPi2    5 Sent to channel(start)' : S
2024-01-08 14:44:44,735 DEBUG    EmonPi2    5 Sent to channel(end)' : S

So far I am not getting anything into Emoncms.

Thanks,

5

@borpin
I asked what appears on the emonCMS Inputs page, but the question has not been answered. Maybe the OP is looking at Feeds?

6

This is my inputs page.

image
image1946×1926 272 KB

7

That is wrong for the 3-phase emonTx V3.4 Node 11 data, you should have only 4 powers, Vrms, 6 temperatures and a pulse count.

Do you have two Node 11 in your emonhub.conf file? If you do, delete the one (or more?) that corresponds with the 6 powers, 6 energies etc.

8

This is the nodes section in its entirety.

[nodes]
        [[11]]
        nodename = emontx3_3phase_11
        [[[rx]]]
            names = powerL1, powerL2, powerL3, power4, Vrms, temp1, temp2, temp3, temp4, temp5, temp6, pulse
            datacodes = h, h, h, h, h, h, h, h, h, h, h, L
            scales = 1.0, 1.0, 1.0, 1.0, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 1.0
            units = W, W, W, W, V, C, C, C, C, C, C, p

These input were created when I created a device. I have since deleted them and the inputs page remains empty after a few frames were processed by emonhub.

image
image1978×454 44.7 KB

9

On the Admin → System Info page of emonCMS, are all the Services running?

10

Services

image
image1844×706 114 KB

11

I have run out of suggestions for what has gone wrong.
@TrystanLea Can you help please?

@BuciboLebo started off here emonSD-10Nov22 (Stable) and EmonTX V34 by reverting the rfm69Pi to Jeelib Classic, but I think his 3-phase emonTx V3 sketch was your LPL converted version. (We really need the RF library version in the logs - second time request!)
He didn’t have a node definition at all in his emonhub.conf.
He didn’t record what he changed to get the data into emonHub – rfm69Pi or sketch.
Then he started this new topic so I closed the old one to avoid duplication & confusion.
The log mentions “emonPi2” but the inactive LCD service suggests it’s an emonBase.

12

Hi @TrystanLea
emonTx34_DS_jeelib_classic.ino.zip (8.7 KB)

These are the changes I made to the Emontx sketch. I changed nodeID and networkGroup.

//-----------------------RFM12B / RFM69CW SETTINGS----------------------------------------------------------------------------------------------------
byte RF_freq=RF12_433MHZ;                                           // Frequency of RF69CW module can be RF12_433MHZ, RF12_868MHZ or RF12_915MHZ. You should use the one matching the module you have.
byte nodeID = 11;                                                    // emonTx RFM12B node ID
int networkGroup = 210;
boolean RF_STATUS = 1;                                              // Enable RF

My emonhub config remains as listed in my earlier post above.
The output in the emonhub remains the same as listed above as well.
My device is not a emonPi. I installed emonSD myself into my own RaspberryPi.
rfm69p is receiving and processing frames as evidenced in the emonhub logs.
I have provided the Emontx sketch I used as an attachment to this post.

This is the JeeLibClassic version I choose for updating the rfm69pi

image
image1836×330 46.7 KB

The following is the log resulting of updating the rfm69pi

-------------------------------------------------------------
emonBase_jeelib Firmware Upload
-------------------------------------------------------------
Downloading firmware from: 
https://github.com/openenergymonitor/RFM2Pi/releases/download/1.4.0/firmware.hex

Downloaded file: 
-rw-r--r-- 1 pi pi 22K Dec  7  2021 /opt/openenergymonitor/data/firmware/emonBase_jeelib.hex

EmonHub is running, stopping EmonHub

Uploading emonBase_jeelib on serial port ttyAMA0
Attempt 1...

avrdude -Cavrdude.conf -v -pATMEGA328P -carduino -D -P/dev/ttyAMA0 -b38400 -Uflash:w:/opt/openenergymonitor/data/firmware/emonBase_jeelib.hex:i 

avrdude-original: Version 6.3-20171130
                  Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
                  Copyright (c) 2007-2014 Joerg Wunsch

                  System wide configuration file is "avrdude.conf"
                  User configuration file is "/root/.avrduderc"
                  User configuration file does not exist or is not a regular file, skipping

                  Using Port                    : /dev/ttyAMA0
                  Using Programmer              : arduino
                  Overriding Baud Rate          : 38400
                  AVR Part                      : ATmega328P
                  Chip Erase delay              : 9000 us
                  PAGEL                         : PD7
                  BS2                           : PC2
                  RESET disposition             : dedicated
                  RETRY pulse                   : SCK
                  serial program mode           : yes
                  parallel program mode         : yes
                  Timeout                       : 200
                  StabDelay                     : 100
                  CmdexeDelay                   : 25
                  SyncLoops                     : 32
                  ByteDelay                     : 0
                  PollIndex                     : 3
                  PollValue                     : 0x53
                  Memory Detail                 :

                                           Block Poll               Page                       Polled
                    Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                    ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                    eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
                    flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
                    lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                    hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                    efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                    lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
                    calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                    signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

                  Programmer Type : Arduino
                  Description     : Arduino
                  Hardware Version: 3
                  Firmware Version: 4.4
                  Vtarget         : 0.3 V
                  Varef           : 0.3 V
                  Oscillator      : 28.800 kHz
                  SCK period      : 3.3 us

avrdude-original: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude-original: Device signature = 0x1e950f (probably m328p)
avrdude-original: reading input file "/opt/openenergymonitor/data/firmware/emonBase_jeelib.hex"
avrdude-original: writing flash (7814 bytes):

Writing | ################################################## | 100% 2.73s

avrdude-original: 7814 bytes of flash written
avrdude-original: verifying flash memory against /opt/openenergymonitor/data/firmware/emonBase_jeelib.hex:
avrdude-original: load data flash data from input file /opt/openenergymonitor/data/firmware/emonBase_jeelib.hex:
avrdude-original: input file /opt/openenergymonitor/data/firmware/emonBase_jeelib.hex contains 7814 bytes
avrdude-original: reading on-chip flash data:

Reading | ################################################## | 100% 2.47s

avrdude-original: verifying ...
avrdude-original: 7814 bytes of flash verified

avrdude-original done.  Thank you.

avrdude-original: Using autoreset DTR on GPIO Pin 7
avrdude-original: Using autoreset DTR on GPIO Pin 7
avrdude-original: Using autoreset DTR on GPIO Pin 7
SUCCESS: flash verifed

Restarting EmonHub
13

Additionally I find that when manually sending data to Emoncms my API KEY is unrecongnized.

See below for API KEY value.

image
image1984×1418 240 KB

See below for result of posting manually.

image
image2004×1168 200 KB

14

The API key for the local and remote instances will be different. Are you using the right Write Key?

It is never a good idea to publish an API key on a public forum.

15

I am posting to a local instance of Emoncms.
I used the Read & Write API KEY.

16

When I click though the highlighted HTTP example found in the documentation and already repopulated with the correct API KEY I get the following results.

HTTP Call

image
image1966×1452 417 KB

Result

image
image2004×262 38.3 KB

17

Please guide on how to obtain internal and external API keys. In my user profile page I see only one set set of keys that are neither marked as internal nor external.

image
image426×622 10.7 KB

18

I do not recognise what you mean by “internal” and “external”.

Every instance of emonCMS has an unique pair of APIkeys. Your RPI has a pair, only one pair, to use when requesting data from (read) or sending data to (read & write), its emonCMS. As far as I am aware, nothing running inside the RPI needs an APIkey to read or write. If you sign up for an account at emoncms.org, your account there will also have a pair of APIkeys, and these will be different to your RPi’s, and from anyone else’s account on emoncms.org. If you use your browser on your LAN to send a block of data (it could be test data) to your RPi, then you need your read & write APIkey from your emonCMS running on the RPi.

One thing puzzled me about your configuration in post no.4. Is the URL there your RPi? – because if it is, I think (I could be wrong) this will send the data back into itself. You only fill in the URL, APIkey and particularly ‘senddata’ when you are sending to ANOTHER emonCMS running on another server somewhere else.

Where is the emonCMS, which the screenshot in post no.13 comes from?

Have you created and then deleted an account on your emonCMS running on your RPi? Is this where the screenshot in post no.17 immediately above comes from? Your Username, which you choose when you create the account, and the two APIkeys which will be created by the system, should be there, like post no.13.

Where did the screenshot in post no.16 come from, because this shows a read & write APIkey in one of the examples.

19

Strange, it works for me.

Local = 192.168.x.x or remote = emoncms.org. These are 2 instances so have different API Keys.