Actually, when a ring action happens the binary sensor "ring action" turned on. When polling for updates is enabled in the integration configuration, it calls the /list endpoint of the Nuki Bridge HTTP API so the "ring action" sensor may be turned off with the polling updates.
So what happens if the polling for updates is disabled? Well, once the "ring action" binary sensor turned on it will never turned off.
I delegate the updates for Nuki devices to the webhook so I keep disabled the polling for updates to reduce LAN traffic.
This PR introduced the schedule of a task to turn off the "ring action" binary sensor 5 second after it turn on.
Actually, when a ring action happens the binary sensor "ring action" turned on. When polling for updates is enabled in the integration configuration, it calls the /list endpoint of the Nuki Bridge HTTP API so the "ring action" sensor may be turned off with the polling updates.
So what happens if the polling for updates is disabled? Well, once the "ring action" binary sensor turned on it will never turned off. I delegate the updates for Nuki devices to the webhook so I keep disabled the polling for updates to reduce LAN traffic.
This PR introduced the schedule of a task to turn off the "ring action" binary sensor 5 second after it turn on.