No node XX MQTT-Topic: home/rfm_gw/sb/nodeXX/dev16 ON Val:1

[kisa]

Hi,

I've been successfully running a few temperature sensors around the house (in and out) for a couple of weeks, which have worked well. Also added an ultrasonic sensor to my rainwater tanks, which is not working well, but I will report further on that elsewhere once I've finished my testing.

I added another 3 temperature sensors to my network yesterday, which all seems to work as they got added, but by yesterday evening I saw (on Grafana via influxDB) that basically all the graphs had straight lines (no value change) over a 5 hour period, showing there was a problem.

I initially thought it may have been my main RF receiver, but after looking at it's operation through its serial debugging lines I'm thinking it may be a configuration on Openhabian (not really sure). This is what I'm continually receiving (note:- all sensors are running in sleep mode and wake up every 5 minutes, Node 50 is currently not working):-

DEBUGRADIO Serial Begin GW Version GW V2.5.1_p1

433 Mhz...
Setting up network
Ethernet begun
connecting
no link
MQTT-link OK
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1


The RF receiver seems to be getting flooded with an inability to find my Node 50. What confuses me is why it's singled out Node 50. If I turn off any other sensor it doesn't say it can't see it (it doesn't care). I also notice the Transmit LED on my RF receiver is nearly always on. I'm guessing it's continually trying to find Node 50???

Just so you know, Node 50 has stopped working, I did get it working last night briefly (cycled the power), which started a massive flood of information into the RF receiver, before it failed again and everything stopped again. So from that, when Node 50 is working everything seems to be happy, but I don't think one Node dropping out should kill the RF network.

Having looked through the RF receiver code I found these bits which I believe produce the Node 50 message, but don't understand which end is causing it and why no other node is stated when it is off:-

mqttClient.subscribe(subTopic); // subscribe to all southbound messages
mqttClient.subscribe(subTopic); // re-subscribe to mqtt topic
Suggestions?

Thanks for reading .

[kisa]

UPDATE

I reprogrammed one of the other Nodes to be Node 50 (not in sleep mode like the others still are, so I can log easier) and let it sit for about half an our and got these readings on both the Node and RF Receiver, which commenced at the same time.

From Node 50:-

Node 50 Version 2.2MhC DS18B Cels GW2.5.1

Transmitting at 433 Mhz...
Requesting temperatures...DONE
Temperature for DS18 Device 50 is: 19.75 C
No connection...

No connection...
No connection...
No connection...
No connection...
Requesting temperatures...DONE
Temperature for DS18 Device 50 is: 19.56 C

No connection...
No connection...
No connection...
No connection...
Requesting temperatures...DONE
Temperature for DS18 Device 50 is: 19.19 C

No connection...
Node: 50 dev: 4 cmd: 0 Ival: 0 Fval: 3.53 RSSI: -27
Node: 50 dev: 9 cmd: 0 Ival: 3 Fval: 3.53 RSSI: -27
Node: 50 dev: 50 cmd: 0 Ival: 0 Fval: 19.19 RSSI: -26
Requesting temperatures...DONE
Temperature for DS18 Device 50 is: 19.19 C

Node: 50 dev: 2 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
Node: 50 dev: 4 cmd: 0 Ival: 0 Fval: 3.58 RSSI: -28
Node: 50 dev: 9 cmd: 0 Ival: 1 Fval: 3.58 RSSI: -27
Node: 50 dev: 50 cmd: 0 Ival: 0 Fval: 19.19 RSSI: -27

Node: 50 dev: 2 cmd: 0 Ival: 0 Fval: 0.00 RSSI: -27
Node: 50 dev: 4 cmd: 0 Ival: 0 Fval: 3.56 RSSI: -27
Node: 50 dev: 9 cmd: 0 Ival: 1 Fval: 3.56 RSSI: -27
Node: 50 dev: 50 cmd: 0 Ival: 0 Fval: 19.19 RSSI: -27

From RF Receiver:-

DEBUGRADIO Serial Begin GW Version GW V2.5.1_p1

433 Mhz...
Setting up network
Ethernet begun
connecting
no link
no link
MQTT-link OK
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 51,4,0,3.33
MQTT msg: home/rfm_gw/nb/node51/dev04: 3.33
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 55,2,0,0.00
MQTT msg: home/rfm_gw/nb/node55/dev02: -44
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,4,0,3.54
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.54
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 55,9,6,2.86
MQTT msg: home/rfm_gw/nb/node55/dev09: 6
Node 50,9,6,3.54
MQTT msg: home/rfm_gw/nb/node50/dev09: 6
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,50,6,19.75
MQTT msg: home/rfm_gw/nb/node50/dev50: 19.75
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,2,0,0.00
MQTT msg: home/rfm_gw/nb/node50/dev02: -14
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,4,0,3.54
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.54
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,9,6,3.54
MQTT msg: home/rfm_gw/nb/node50/dev09: 6
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,50,6,19.56
MQTT msg: home/rfm_gw/nb/node50/dev50: 19.56
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,2,0,0.00
MQTT msg: home/rfm_gw/nb/node50/dev02: -13
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 50,4,0,3.53
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.53
Node 50,4,0,3.53
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.53
Node 50,9,3,3.53
MQTT msg: home/rfm_gw/nb/node50/dev09: 3
Node 50,50,0,19.19
MQTT msg: home/rfm_gw/nb/node50/dev50: 19.19
Node 50,2,0,0.00
MQTT msg: home/rfm_gw/nb/node50/dev02: -28
Node 50,4,0,3.58
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.58
Node 50,9,1,3.58
MQTT msg: home/rfm_gw/nb/node50/dev09: 1
Node 50,50,0,19.19
MQTT msg: home/rfm_gw/nb/node50/dev50: 19.19
Node 50,2,0,0.00
MQTT msg: home/rfm_gw/nb/node50/dev02: -28
Node 50,4,0,3.56
MQTT msg: home/rfm_gw/nb/node50/dev04: 3.56
Node 50,9,1,3.56
MQTT msg: home/rfm_gw/nb/node50/dev09: 1
Node 50,50,0,19.19
MQTT msg: home/rfm_gw/nb/node50/dev50: 19.19

It seems to be working now. I then disconnected Node 50 (removed power) and everything continued to work fine, obviously without any temperature readings from Node 50.

I then reopened the RF Receiver serial window, which resets the RF Receiver, still with Node 50 off and it worked fine again:-

DEBUGRADIO Serial Begin GW Version GW V2.5.1_p1

433 Mhz...
Setting up network
Ethernet begun
connecting
no link
MQTT-link OK
MQTT-Topic: home/rfm_gw/sb/node50/dev16
ON
Val:1
No node 50
Node 55,2,0,0.00
MQTT msg: home/rfm_gw/nb/node55/dev02: -41
Node 55,4,0,2.87
MQTT msg: home/rfm_gw/nb/node55/dev04: 2.87
Node 55,9,1,2.87
MQTT msg: home/rfm_gw/nb/node55/dev09: 1
Node 55,50,0,14.25
MQTT msg: home/rfm_gw/nb/node55/dev50: 14.25
Node 54,2,0,0.00
MQTT msg: home/rfm_gw/nb/node54/dev02: -31
Node 54,4,0,3.07
MQTT msg: home/rfm_gw/nb/node54/dev04: 3.07
Node 54,9,1,3.07
MQTT msg: home/rfm_gw/nb/node54/dev09: 1
Node 54,50,0,15.06


It is still looking specifically for Node 50 but didn't go into a failing loop when it couldn't find it. Also the TX LED on the RF Receiver is no longer permanently on.

I'm baffled by this and not satisfied with the outcome as I've changed nothing and it's now working, so I think it's just a matter of time before it fails again .

I'm still open for suggestions .

[papa]

I'm busy & tired from helping family move. Will make a few comments.

Ultrasonic sensor does not work well for water, a dripping or flowing surface confuses it. That's why I did the other water level sensor.

May need more info on your node 50 problems. A few ideas: loose connection to RFM69, faulty RFM69, more than one node 50. RFM69 can handle limited number of nodes (I did a thread on adding gateways), but one gateway can handle at least dozen nodes.

[kisa]

Understand, moving is draining.
The tank I'm measuring has no flow or dripping, it connects to another couple of tanks via a small pipe at the bottom. The tank that collects fills up the tank I'm measuring slows and from under the water.
Do you think the ultrasonic would work in that case?
Definitely only one Node 50 and the Node 50 I was using is a moteino arduino, so the RFM is attached as part of production, so I expect it's connection should be fine.
I'll keep an eye on it and let you know if I notice anything else.

[papa]

My ultrasonic water monitor sort of worked, & sort of not, but it was monitoring a sump hole that had a sometimes flow & sometimes trickle of water.

I don't know but suspect that even if still, water surface does not necessarily give a reliable bounce back of the ultrasonic sound waves. I find my other water level sensor to be much more reliable. Let us know your experience & conclusions.

Regarding Node 50 troubles ... as with WiFi ... devices' "position" can affect transmission ... intervening distance & obstacles, other nearby "transmitters" that use the same frequency as your RFM69.

[kisa]

Thanks for the reply. I'll let you know how it goes. I'm keen for the accuracy the ultrasonic may give (emphasising may), but will have a read over your sensor/transistor option.

Thanks for your suggestions about the rfm's, that is possible. One random thought I had may be regarding the battery voltage getting low and (which occurred to me later) that I was connecting it to the Vin and GND on the Motenio input, which feeds a voltage regulator, producing a 3.3V output. With 2 x AA batteries, maybe the voltage got too low for the regulator and it kept collapsing its output, causing the node to act strangely, flooding the network? Bit far fetched, I guess, but I've now connected the batteries to the 3.3V direct input and will see what happens.

[papa]

kisa: "Thanks for your suggestions about the rfm's, that is possible. One random thought I had may be regarding the battery voltage getting low and (which occurred to me later) that I was connecting it to the Vin and GND on the Motenio input, which feeds a voltage regulator, producing a 3.3V output. With 2 x AA batteries, maybe the voltage got too low for the regulator and it kept collapsing its output, causing the node to act strangely, flooding the network? Bit far fetched, I guess, but I've now connected the batteries to the 3.3V direct input and will see what happens."

papa: Your thought about power issues is a good insight, kisa. Too little voltage AND too much voltage & too little current can cause problems.

I did this thread & this thread on using battery power with home made Arduinos: Though they are a couple years old, you might glean something useful from them. Do NOT use the node sketches in those thread because they are old versions of the latest multi-choice node sketch.

Back when, member lewishollow used solar cells to replenish rechargeable batteries powering an outdoor node.  See this thread.

This post summarizes some of my results with a home made Arduino powered by batteries. Perhaps a Moteino or Miniwireless would use less power.

Since then I've not done much with battery power, but I always thought a Moteino or an Anarduino Miniwireless might be good Arduino compatibles to use battery power like for a mailbox node.

Please report back on your experiences with using batteries to power a Moteino node.