Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add device state limitations in Overkiz #36791

Merged
merged 2 commits into from
Jan 8, 2025
Merged

Add device state limitations in Overkiz #36791

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5245e16
Add device state limitations
iMicknl Jan 7, 2025
fe43c1a
tiny tweak
c0ffeeca7 Jan 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/_integrations/overkiz.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading