Node behavior after connection lost
-
I have a battery powered light sensor that was moved out of reach from the controllers range. Moving it back didn't make it reconnect. I had to reboot the sensor. Is that the behavior to expect in such conditions? Is there a way to make clients try to reconnect periodically in case the connection was lost?
-
I have a battery powered light sensor that was moved out of reach from the controllers range. Moving it back didn't make it reconnect. I had to reboot the sensor. Is that the behavior to expect in such conditions? Is there a way to make clients try to reconnect periodically in case the connection was lost?
-
It takes a few failed transmission before it tries to "find new parent". Not sure what happended here without seeing the node log.
@hek said:
It takes a few failed transmission before it tries to "find new parent". Not sure what happended here without seeing the node log.
@mfalkvidd said:
@รอเรือ which version are you using? 2.0 has a problem with nodes that go back to sleep too soon after a failed send. This is fixed in the development version. See https://github.com/mysensors/MySensors/pull/558 for details.
Thanks guys! Well, I'm on 2.0.0. I'm not the "adventurous type" so I'm not on the development version if You get my point (ha ha).
It's good to know that there exists some healing mechanisms in the communication. I might wait for the next stable release or I might build me a dedicated "MySensor : RepeaterNode" with an external antenna to facilitate the communication with my upcoming battery powered nodes in my garden and for the lawn mower that really must be automated soon.
Hej tjolahopp! (Cheers!)
