Timeout fetching nuki devices data

[AlexW75]

The problem

Hi, I've been frequently encountering an error message in the log for my NUKI Lock. It occurs occasionally when I command the lock to either lock or unlock. However, if I execute the command a second time, it always succeeds. This issue has been present for at least a year, but since I managed it by using an automation that repeats the command, it is a minor issue for me.

I am happy to provide additional trace information if needed.

What version of Home Assistant Core has the issue?

core-2024.4.3

What was the last working version of Home Assistant Core?

none

What type of installation are you running?

Home Assistant OS

Integration causing the issue

NUKI

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: pynuki
Quelle: components/nuki/coordinator.py:98
Erstmals aufgetreten: 00:44:08 (1 Vorkommnisse)
Zuletzt protokolliert: 00:44:08

Call failed: <Response [200]>

Logger: homeassistant.components.nuki.coordinator
Quelle: helpers/update_coordinator.py:318
Integration: Nuki (Dokumentation, Probleme)
Erstmals aufgetreten: 00:43:54 (1 Vorkommnisse)
Zuletzt protokolliert: 00:43:54

Timeout fetching nuki devices data

Additional information

No response

[home-assistant[bot]]

Hey there @pschmitt, @pvizeli, @pree, mind taking a look at this issue as it has been labeled with an integration (nuki) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nuki 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 nuki 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)}}

---

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

[pree]

Hi @AlexW75. This looks really weird, having it "Failed 200". Is there anything special about your Network? Could you try querying the API directly to see if that also results in this behaviour?

[AlexW75]

My network is nothing special just a FritzBox Mesh. What you mean with directly? Over NukiWeb?

[aperezva]

Registrador: homeassistant.components.nuki.coordinator Fuente: helpers/update_coordinator.py:360 integración: Nuki (documentación, problemas) Ocurrió por primera vez: 15:23:23 (1 ocurrencias) Último inicio de sesión: 15:23:23

Timeout fetching nuki devices data

Same or similar problem

[SVNKoch]

I just had the same problem, restarts didn't help and reconfigurations with a newly set API key on the bridge still resulted in failed connection (some timeout message).

What helped: I restarted the bridge, deleted the integration, restarted HA, nuki got auto discovered, entered API key and everything was working again

[RaimondB]

I am having similar issues:

2024-10-11 12:11:47.858 ERROR (MainThread) [homeassistant.helpers.entity_registry] 'lock' from integration nuki has a non string unique_id '318250121', please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+nuki%22
2024-10-11 12:12:17.273 DEBUG (MainThread) [homeassistant.components.nuki.coordinator] Finished fetching nuki devices data in 0.094 seconds (success: True)
2024-10-11 12:12:57.182 ERROR (MainThread) [homeassistant.components.nuki.coordinator] Timeout fetching nuki devices data
2024-10-11 12:12:57.182 DEBUG (MainThread) [homeassistant.components.nuki.coordinator] Finished fetching nuki devices data in 10.003 seconds (success: False)

Restarting HA, rediscovering lock as mentioned above did not work for me.

[Claudio1L]

clean install of HAOS

Core 2024.10.2 Supervisor 2024.10.0 Operating System 13.1 Frontend 20241002.3

systematically every reboot:

Logger: pynuki Source: components/nuki/init.py:144 First occurred: 10:06:07 PM (1 occurrences) Last logged: 10:06:07 PM Call failed: <Response [200]>

[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.