Rfm12 fails to work in new Pi

Hardware RFM69Pi
1

I had a working system with the 2017 distro on an old Pi that has just 26 pins and where a rfm12 was connected to the block nearest the corner of the Pi and the board facing in. It still works when I return the rfm12 to the old Pi and boot it up.

My new Pi3 B+ is running the 2021 distro. It has 40 pins and, again, I attach the rfm12 to the block nearest the corner and facing in. The green light flashes ever 10secs but no data is received. The emonHub log has no entries.

The entries in the config are the same as in the old Pi:
[[RFM2Pi]]
Type = EmonHubJeeInterfacer
[[[init_settings]]]
com_port = /dev/ttyAMA0
com_baud = 9600 # 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)

The other oddity is that in the Admin page the emonhub is reported as
emonhub Activating loaded activating auto-restart
If I click the Start button, it does not start.

So it looks like the new Pi is not communicating with the rmf12 and I am wondering if the correct pins of the Pi are connected to the block on the rfm12, now there are 40 instead of 26 pins on the Pi.

The rfm12 continues to work when I return it to the old Pi.

Can somebody please comment whether the pin configuration has changed.

Thanks

2

Hello @nigeldodd I’ve just pushed a fix for the emonhub issue a few minutes ago, could you run a full update to see if that clears the issue for you?

3

Thank you Trystant.

Is the update not in the 2021 download which I have on the new Pi.

If not, could you please explain how to run a full update. Is it from the emon web interface?

thanks so much.

4

Sorry, I see you did it a few minutes ago.

So can I run the update from the emon web interface, please?

thanks
again

5

Yes you can

6

thanks Trystan,

I did a full update.
The scrolling text said “rfm2pi detected”.
Looking afterwards at the setup it says “emonHub config v2.1.4”
After reboot it says “Emonhub active running”
But I still don’t think it is getting data from the emonHub radio board. Instead of data I’m getting

2022-11-13 18:10:46.173|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-13 18:10:46.078|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0
2022-11-13 20:15:59.044|WARN|emoncms_mqtt.php|Not connected, retrying connection
2022-11-13 20:15:59.132|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-14 10:25:32.049|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-14 10:25:32.162|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-14 10:27:25.-269|ERROR|index.php|Not Authenticated|admin/info 
2022-11-14 10:43:49.072|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-14 10:43:49.163|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-15 10:39:44.438|ERROR|index.php|Not Authenticated|admin/info 
2022-11-15 10:55:51.-348|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-15 10:55:51.-326|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-15 10:58:25.206|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-15 10:58:25.157|ERROR|index.php|Not Authenticated|admin/info 
2022-11-15 10:58:25.256|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-15 11:05:19.351|WARN|emoncms_mqtt.php|Not connected, retrying connection 
2022-11-15 11:05:19.441|WARN|emoncms_mqtt.php|Connecting to MQTT server: Connection Accepted.: code: 0 
2022-11-15 11:05:31.-65|ERROR|index.php|Not Authenticated|admin/info

[edit by MOD for clarity]

7

Thanks @nigeldodd is it all working as expected? those messages are nothing to worry about, you usually get those every time you reboot.

1 Like
8

Yon need to look at the emonhub log not the emoncms log.

9

Thanks again, but not it is not working. The error messages that I showed in the previous post are all I get. Nothing more.

With the old Pi and old software and old emoncms I get a continuous stream of chatter from which I can tell that the house power - solar power = 142 Watts right now:

2022-11-15 12:19:05,497 INFO RFM2Pi Publishing: emon/emontx1/power1 142
2022-11-15 12:19:05,504 INFO RFM2Pi Publishing: emon/emontx1/power2 189
2022-11-15 12:19:05,511 INFO RFM2Pi Publishing: emon/emontx1/power3 0
2022-11-15 12:19:05,517 INFO RFM2Pi Publishing: emon/emontx1/power4 0
2022-11-15 12:19:05,524 INFO RFM2Pi Publishing: emon/emontx1/vrms 241.4
2022-11-15 12:19:05,531 INFO RFM2Pi Publishing: emon/emontx1/temp1 0
2022-11-15 12:19:05,537 INFO RFM2Pi Publishing: emon/emontx1/rssi 0
2022-11-15 12:19:05,544 INFO RFM2Pi Publishing: emonhub/rx/10/values 142,189,0,0,241.4,0
2022-11-15 12:19:05,551 INFO RFM2Pi Publishing: emonhub/rx/10/rssi 0
2022-11-15 12:19:05,559 DEBUG RFM2Pi 107 adding frame to buffer => [1668514745.449513, 10, 142, 189, 0, 0, 241.4, 0]
2022-11-15 12:19:05,562 DEBUG RFM2Pi 107 Sent to channel(end)’ : ToEmonCMS
2022-11-15 12:19:08,932 INFO emoncmsorg sending: https://emoncms.org/input/bulk.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y&data=[[1668514723.748423,10,147,186,0,0,240.47,0],[1668514734.618039,10,133,186,0,0,241.55,0],[1668514745.449513,10,142,189,0,0,241.4,0]]&sentat=1668514748
2022-11-15 12:19:09,361 DEBUG emoncmsorg acknowledged receipt with ‘ok’ from https://emoncms.org
2022-11-15 12:19:09,365 INFO emoncmsorg sending: https://emoncms.org/myip/set.json?apikey=E-M-O-N-C-M-S-A-P-I-K-E-Y
2022-11-15 12:19:16,278 DEBUG RFM2Pi 108 NEW FRAME : 10 128 0 183 0 0 0 0 0 108 94 0 0
2022-11-15 12:19:16,287 DEBUG RFM2Pi 108 Timestamp : 1668514756.28
2022-11-15 12:19:16,290 DEBUG RFM2Pi 108 From Node : 10
2022-11-15 12:19:16,293 DEBUG RFM2Pi 108 Values : [128, 183, 0, 0, 241.72, 0]
2022-11-15 12:19:16,296 DEBUG RFM2Pi 108 Sent to channel(start)’ : ToEmonCMS
2022-11-15 12:19:16,300 INFO RFM2Pi Publishing: emon/emontx1/power1 128
2022-11-15 12:19:16,307 INFO RFM2Pi Publishing: emon/emontx1/power2 183
2022-11-15 12:19:16,349 INFO RFM2Pi Publishing: emon/emontx1/power3 0
2022-11-15 12:19:16,400 INFO RFM2Pi Publishing: emon/emontx1/power4 0
2022-11-15 12:19:16,534 INFO RFM2Pi Publishing: emon/emontx1/vrms 241.72
2022-11-15 12:19:16,594 INFO RFM2Pi Publishing: emon/emontx1/temp1 0
2022-11-15 12:19:16,655 INFO RFM2Pi Publishing: emon/emontx1/rssi 0
2022-11-15 12:19:16,877 INFO RFM2Pi Publishing: emonhub/rx/10/values 128,183,0,0,241.72,0
2022-11-15 12:19:16,967 INFO RFM2Pi Publishing: emonhub/rx/10/rssi 0
2022-11-15 12:19:17,044 DEBUG RFM2Pi 108 adding frame to buffer => [1668514756.277574, 10, 128, 183, 0, 0, 241.72, 0]
2022-11-15 12:19:17,047 DEBUG RFM2Pi 108 Sent to channel(end)’ : ToEmonCMS

10

Thank you Borpin, yes the data is coming in on the emonhub log, as you say.

The dashboard from the old system has transferred across.

I now need to get node-red working and re-establish my hot water diverter.

Oh, and I guess the evse car charger will need a new ip address.

thanks all

11

If you had an old EmonSD with Node-RED on it, it is no longer on the default image and the advice is not to run it on the same Pi.

Possibly, or possibly not.

A reason to reserve IP addresses at the router or use static IP addresses for some things.

12

thanks Borpin.

“If you had an old EmonSD with Node-RED on it, it is no longer on the default image and the advice is not to run it on the same Pi.”
I have it running on the new emon pi.
The mqtt is forever saying “connecting” . In the old system such a node listened to emon/emontx/power1 and produced the excess Watts measurement. The server is localhost:1883 as before but it is not working.

I have reserved IP addresses, thanks.

13

In Node-RED?

Try the IP Address.

14

Yes, in Node-Red the mqtt input node is forever saying “connecting”

I have edited the mqtt broker to 192.168.1.168 with port 1883 as you suggested and redeployed. The node still says “connecting”

If I point a browser at 192.168.1.168:1883 I get “This site can’t be reached”

I am not sure why the mqtt server has this port.

15

Have you got an catch node to capture the error?

User and Password correct?

I suggest you SSH in and try connecting to the MQTT broker via the command line.

16

How do I tell node red the login details? What login details would they be? The SSH ones?

17

Sorry, I have found the correct way to give security details

There is a tab on the node-red config for the mqtt node
security details are in

2 Likes