![]() fresh : 150msec (to receive the updated info)ĭoes this give you already some idea on the issue ?.(i had to update the wait_sleep_duration from 0.5s to 5sec. I see that the problem is the delay to answer the sleep notification. after a restart of domoticz, it stop to work.Without debugging code yet, I can detect the following: ![]() To test, I send a update to a text variable trough api. Very basic : domoticz->mysensors_gw(serial)->nrf24->sensors I build the mysensors setup again to reproduce the problem. Debugging at the node shows that PRE-NOTIFICATION and POST-NOTIFICATION messages are present.ĭo you have any clue to what can cause this behaviour? Is there anything else I can look at?.Other children in the node, not reacting on SmartSleep continue to work (so the node is alive).No difference in Domoticz logging (debug on) except non-working Smartsleep gives error messages (Error: MySensors: Repeating previous command (2/2) andĮrror: MySensors: Command not received by Node !! (node_id: 101, child_id: 1)).No difference in database data (MySensors tables) with working and non-working Smartsleep.Clearly it had nothing to do with the update itself (nothing touched MySensors) but, confirmed with testing, the restart of Domoticz causes Smartsleep to stop working. The only thing that happened was an update of Domoticz on my system. After the update everything went fine until suddenly it stopped working. I have to get back to this since the working is not reliable. With issue #2487 the implementation of MySensors SmartSleep has been corrected and reported as ok.
0 Comments
Leave a Reply. |