Closed tristanXme closed 3 years ago
nuki documentation nuki source (message by IssueLinks)
Looks like #41460
Hey there @pschmitt, @pvizeli, mind taking a look at this issue as its been labeled with an integration (nuki
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
Oh yes, sorry for that. Created a Issue for that longer ago but got the information to use the template (sorry for not using it as i'm new to github) but as i was on vacation I did not had time before to do so. Now somebody else already created a (similar) issue.
Old one of me: https://github.com/home-assistant/core/issues/41071
I just fully removed my custom REST API Calls, to make sure, that the error is not because the bridge is busy and does not answer to the nuki integration. But even after removing it complete and also deleting the binary sensors generated by my API Calls in the the "database", it still does not work - even after a full reboot of the host system.
Any Idea?
Maybe in general it would be better to change the integration to push from nuki instead of pulling. Nuki is supporting this right now.
Same here. My bridge wifi does some sort of reboot as soon as HA tries to access the API. No problems if called via browser.
Tested a downgrade to 0.115 - it still does not get back to work... So it does not seem to be related to the current version.
The problem occured the first time when I upgraded to 0.116. It worked flawlessly with all previous versions (I upgraded from 0.115.6). But I can confirm, that a downgrade doesn't fix the problem now and I have no explanation for it.
The issue is that the current integration polls the lock for the status while the Nuki Bridge seems very limited in resources. A lot of request receive a 503 error from the lock. A much better way to integrate Nuki with Home Assistant is to use the callback functionality of the lock itself. That makes polling obsolete, will result in faster updates, will drain the Nuki battery less and is more reliable. More information is described in this feature request: https://community.home-assistant.io/t/nuki-use-callbacks-instead-of-unreliable-polling/229064/5
Yes, but if it would be that error, it should work at least sometimes. But it does not work at anytime anymore.
Oh yes, sorry for that. Created a Issue for that longer ago but got the information to use the template (sorry for not using it as i'm new to github) but as i was on vacation I did not had time before to do so. Now somebody else already created a (similar) issue.
Old one of me:
41071
Also for me. Same problem. Has anyone found a solution? Or temporarily a workaround?
No, sadly there is no workaround / fix currently that I know
No, sadly there is no workaround / fix currently that I know
I'm searching if HA can process/receive callback. I have already created 2 restful method to call lock and unlock nuki inside HA but i can't receive any info about state. Nuki can register 3 IP address to send state info anytime there any changes on nuki. But HA must receive this info....
You can get the state also by pulling the rest API but sadly the pulling method is not that reliable. The Callbacks could be gathered by webhooks I think - but I never worked with those, so I'm not sure how to do it exactly.
NO, polling is not an option. Webhook not permit to process any info, only to call a script. https://developer.nuki.io/page/nuki-bridge-http-api-1-12/4/
Even openHAB is using callbacks.
Same over here. Switching to nodered node to manage it
Same over here. Switching to nodered node to manage it
What does it mean? How did you manage to find Nuki's status from NodeRed?
I have the same problem after the update to Home Assistant 0.117
I have the same problem after the update to Home Assistant 0.117
Nuki Look Firmware 2.9.10 solved the problem for me
I have the same problem after the update to Home Assistant 0.117
Nuki Look Firmware 2.9.10 solved the problem for me
mine also came back to life!
The problem
Hello,
the nuki integration just stopped working for me. In Addition to the official NUKI integration, i use a custom REST API command to get the state of the door (opend /closed). Thats still working. Even calling the Nuki API by browser gives a "valid" response. So there shouldnt be any problem with the nuki bridge in general.
Environment
Currently Running HASS.IO on a Rapsberry PI with 4GB.
Supervisor Version: 247 HassOS 4.13 Home Assistant 0.116.2 - but it did not work on 0.115 either.
Problem-relevant
configuration.yaml
Traceback/Error logs
`Logger: homeassistant.components.lock Source: /usr/local/lib/python3.8/asyncio/events.py:81 Integration: Schloss (documentation, issues) First occurred: 11. Oktober 2020, 13:55:18 (1 occurrences) Last logged: 11. Oktober 2020, 13:55:18
Additional information