Closed azvero closed 5 years ago
Are you polling for changes? And if so, what are the polling-interval?
Experience shows that polling the gateway will make it freeze, and freezing seems more frequent when using shorter intervals. If you don't really need to observe changes, I would recommend disabling "observe changes".
Using real resource observations (i.e. not polling for changes) are downright impossible to implement using the current api (coap-client). I'm working on a aiocoap version of the plugin that hopefully will be more stable, but it's still some way off...
Take a look at issue #59
Polling at 300 seconds seems to be fine for me and does not freeze. Shorter will.
Thanks for the suggestion (and for the great plugin).
I was using the default polling interval, which I have now increased to 300s.
same problem here but can't fix it and the 300s dusn't help me rebooted all systems multiple times and changed to an interval of 300s but still not posible to recover
Several times a day my Domoticz instance loses its ability to talk to the TRÅDFRI gateway.
In the Domoticz log I see lots of the following:
often accompanied by
and then more of "(Tradfri) No transport, write directive to 'Main' ignored."
When this happens, I found that the only way to recover is by rebooting the TRÅDFRI gateway.
On its own (i.e. before integration into Domoticz) the gateway was very stable, running for weeks on end controlling the lights on a schedule etc.