-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
API disconnects every second (approx. since V 0.0.4) #66
Comments
Hi, Could you please try version 0.0.4 and confirm whether the issue starts with this version? There are no significant changes between 0.0.3 and 0.0.4, so it would be helpful to verify this. I could understand if it was 0.0.5 but 0.0.4 should still run fine. Thanks |
@AzonInc I have no clue on how to use a specific version. |
Use the following:
|
It's throwing a fatal error - even after commenting out the recent added sensor like nightmode and last_unlock_user:
|
Did u add the libraries block? It's still needed for versions < 0.0.5
|
Thanks @AzonInc Here is my code:
|
Did u also clean the build files? |
Yes, I did.
|
Oh sorry, I forgot something. Try this:
|
Thanks @AzonInc Let me know if there is anything that I can contribute to narrow this issue down. It would be great to have all the recently added sensors and switches, but at the house door, reliability rules. |
The Event Logs and Auth Data Entry requests are probably the reason (I could add a flag to disable these requests - that will also disable the last unlock user entity but keeps all the new settings entities) |
It would be nice to have such a flag in the current version of the component. Enable requests for debugging purposes in a "Smart Home Maintenance window" and disable them when the family needs a reliable door lock. In fact the Last Unlock User sensor was always on my wishlist since it is supported by the Nuki-App itself as well as by the ESP32 nuki_hub project. So if there is anything I can provide (eg. Event Logs) just let me know. At the moment, version 0.0.4 is up and running since yesterday. |
Every few days, my ESPHome-Nuki-Lock enters a state where the api conntection to HA becomes unstable.
This never occured on older versions of this outstanding integration.
See below the HA Core Logs and a screenshot of the ESP32 Log.
The text was updated successfully, but these errors were encountered: