Trouble with nodes going offline after a while
Ryanmt last edited by
I have a mysensors network setup, my config is a WemosD1 mini for a gateway, RFM69 radios for comms. Using the latest stable version of mysensors, the new RFM69 driver
The network works fine, i have 4 sensors in total. All battery powered, some are a mix of boost converters and direct power, one is 1mhz and the others are 8mhz.
My problem is that after a while the all the nodes one by one go offline, they come back when you hit the reset button and occasionally they come back to life after the contact sensor is triggered but it's a bit like a game of whack a mole keeping them all online.
Another way I have had issues is if the gateway goes offline for a few hours the nodes never recover so after sorting the gateway I have to manually reset every node.
I am using my controller and have set the system to alert me whenever a node stops communicating for 30 mins. Each node is set to transmit some data every 10 mins as a heartbeat (rx strength).
Do i need to do something on these to enable the watchdog timer? I can upload the sketches if required but for the most part they are the example BME sensor and contact switch ones.
@ryanmt I have experienced this exact same issue and not yet found a definitive solution, but......
Smooth power supplies are essential. Adding extra ceramic/electrolytic caps may help.
Bad connections. This is a real pain to track down as although the dupont connections look fine, they can expand and contract with temperature changes and this can cause issues as well. https://forum.mysensors.org/topic/10470/solved-nrf24l01-radio-fails-connecting-to-gateway/7
Solder as much as you can to eliminate bad crimp connectors.
3.Boost converters should be avoided if you can as many are poorly filtered and are noisey both in their own power output lines and radiated noise from the charge pump switching.
I now send sensor data every 5 minutes regardless to if it has changed at all instead of heartbeat. Heartbeat only shows the node is alive, sending data also shows the sensor state and is for me a better option.
I am not sure if it is the GW or some implementation in mysensors that affects things this way, but if it is the latter jkandassa will find it and fix it.
Ryanmt last edited by
Thanks for the reply.
I'm using the easypcb for the nodes which have a cap on the radio to aid with stability.
I have checked my connectors, i'm pretty confident (and experienced) in putting bits together, to have bad connections on 4 nodes would be very unlucky!!!
Re the boost converters - So far the bootsted ones are more stable than the 1mhz direct drive from the battery ones.
Tis odd. I think i need to get my head around the watchdog timers better to reboot the arduinos automatically.
I have tested a node without mysensors too - just running a temp sensor and OLED, that has been reliable.
@ryanmt I had these issues again today - I am using pro mini with nrf24l01+ so it's not them as we are using different kit...
If I ever find a solution I will let you know.
zen85 last edited by
hey. i was having the same problems from time to time - i found out that its mostly wiring - therefor i am a great fan of easypcb and other boards that let one mount the radio directly.
and also mounting a fan on my gateway (rpi3b) helped a lot with that. other than that repeaternodes...
also install myscontroller - makes debugging way nicer and more efficient because you see in realtime whats going on... you might not have just one problem but more at the same time.
skywatch last edited by skywatch
@zen85 Thanks for the feedback - I do have a node where pin D9 was a bit duff - It would work for ages and then suddenly the node ceased sending data. I eventually tacked it down and 'squished' the connector with pilers and it's been solid ever since. I also have a big heatsink and temperature controlled fan on the pi.
Now it has done its' testing I will build it into an enclosure and solder all wires.
A bit of bug tracking today and I noticed 2 things that would cause problems with the mysensors network.
I accidently swapped values on a node and it was sending data as fast as it could - this would eventually crash the gateway - so always check all nodes are sending data as often as you think they are!
Loose connections - been here before but a bad connection on pin9 of promini/uno will cause the node to 'die'.
Just thought I'd update on this as promised.
I've had so many wiring issues that I always use either the "Nano Wireless Expansion Board", where the NRF module just plugs in, or I use devices that have the radio built in, like the RF-Nano.
Use the MyDebug function to check on your radio. And generally debug your sketch to make sure no race conditions occur
skywatch last edited by skywatch
@alowhum I actually orderd some of those nano boards by mistake (thinking they would work with promini). I don't have a nano so not much use, but I will get one today to try.
Regarding bad connections, dosen't using that board double the failure points?
With cable to the node you have the cable joint and node soldering joint.
With this board you have the cable joint, node soldering joint, socket connection and socket soldering connection. - Just a thought!
Not all failure points are the same. The Dupont wires break easily. Wires embedded inside hardware don't. Since I use these boards I've never had any trouble.
@alowhum I know - I was being pedantic (unusual for me)
I have had really bad batches of dupont cables from online sellers, so much that I bought a crimp tool and connectors and now make my own, but only for testing and prototyping. Never for finished items as they are all soldered.