From 79aa1dad55559e019eb58156a1c0898e49a7926c Mon Sep 17 00:00:00 2001 From: Mick Vleeshouwer Date: Wed, 8 Jan 2025 10:06:04 +0100 Subject: [PATCH] Add device state limitations in Overkiz (#36791) * Add device state limitations * tiny tweak --------- Co-authored-by: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> --- source/_integrations/overkiz.markdown | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/source/_integrations/overkiz.markdown b/source/_integrations/overkiz.markdown index c6ff4a345af..20e0a378ecf 100644 --- a/source/_integrations/overkiz.markdown +++ b/source/_integrations/overkiz.markdown @@ -137,6 +137,12 @@ cover: ### Overkiz API limits +**Device state changes are not broadcasted for all devices** + +Some Overkiz devices do not broadcast status changes. To update their status, the vendor's app (for example, Somfy TaHoma) requests a status update when opened. The app then broadcasts the states via events that the Overkiz integration also listens to. The Overkiz integration cannot replicate this behavior, as it does not know when you access the Home Assistant dashboard or run automations. + +As a result, the state of some Overkiz devices in Home Assistant may not always be up-to-date. + **Server busy, please try again later. (Too many executions)** During peak hours, it could happen that the Overkiz platform is unable to execute your command. The integration will try to retry this command, however, this is not guaranteed to succeed.