Some devices become unavailable due to Overkiz integration errors

[OlivierD31]

The problem

In the Overkiz integration I added an Hexaom Hexaconnect hub in order to control my Somfy Covers and lights. Once credentials filled, everything seem ok, I was able to add cards in my dashboards to control covers and lights connected to this Hexaom hub, but few minutes after all these devices became unavailable. In the overkiz integration page, this hub is tagged as "needs attention" and in error status

What version of Home Assistant Core has the issue?

core-2023.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz

Diagnostics information

home-assistant_2023-12-22T08-50-32.797Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @imicknl, @vlebourl, @tetienne, @nyrodev, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `overkiz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign overkiz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

overkiz documentation overkiz source _{^{(message by IssueLinks)}}

[iMicknl]

Do you have this often, and does it not recover? I am not too familiar with the Hexaom server, but it might be that they don't accept this many requests.

Please add your diagnostics:

1. If your device already shows up in Home Assistant, go to your integrations page and select Overkiz, your hub and the device. Press the 3 dots and select "Download diagnostics. Otherwise, go to your integrations page and select Overkiz. Next to your hub, click the 3 dots and select "Download diagnostics".

2. Attach your diagnostics (JSON file) to this issue by uploading the file in a new comment (drag and drop supported).

[OlivierD31]

Yes I have this same behavior each time I try to add this Hexaom hub, and it does not recover, once the hub is in failed mode I have to remove it from the integration, create a new secondary access account on my hexaom app because the one already used is locked (one time I used my primary access account and I had to contact the Hexaom support to unlock it because it was locked/banned). I cannot Download diagnostics on both unavailable device or failed hub, the option is not present. I have the option only for working hub (my cozytouch gateway).

Thanks

[iMicknl]

@OlivierD31 your problem is bigger than this small bug. It seems your account is blocked by Hexaom all the time, triggering this message.

When you login correctly, you are able to download the diagnostics. Downloading diagnostics is not possible when the integration is not starting.

[OlivierD31]

overkiz-53db7e47c13a7b5492bf413dc502bb50-VR Bureau-24c9f38bb9386cbef2b6210ed575a191.json (8).txt @iMicknl please find attached the diagnostics file of one device which become unavailable. When I said it does not recover I was wrong, in logbook I can see the device of this hexaom hub become unavailable and 24h after they are back available during 10 minutes approximativly. And this every days.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.