-
Notifications
You must be signed in to change notification settings - Fork 41
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
Nuki Opener timeout after upgrade to 9.03-master8 #557
Comments
I have opened via mobile app and now seems responsive. |
With the updated libs I also changed the way nuki ble library reconnects with the lock/opener. It tries to do this faster than before by not querying services each time it connects. Might give some issues though when something in the connection goes wrong and then does not recover. Maybe connecting to the opener through the app disconnected the esp32 and the opener in some way that allows the esp32 to recover the connection afterwards. Will see about forcing a full reconnect on errors. |
The problem repeats after a while, despite I can open with the App and later with Nuki Hub, the same disconnect issue happens again (eg. the next day). |
@duhow Is there any change with the 9.04 release? |
Still having issues. Even after opening with the app, 2h later I would have issues with the device. |
Please report if this is fixed in 9.05-master4 |
Not sure if related, but i've updated to 9.05-master4 and after 4+ hours could not get in to the Opener or Lock:
|
Please report if this is fixed in 9.05-master5. I'm optimistic the issue has been found and addressed. |
No retries for me at least, so seems to work for now for both Opener and Lock. |
This seems fixed. Please re-open if issues persist on 9.05-master5/9.05-beta1 and up. |
PROBLEM DESCRIPTION
Timeouts when attempting to open Nuki Opener.
Can't open the intercom door.
All 4 retry attempts appear within 1 second, expecting to delay a bit.
Noticed these errors couple of days after upgrading to #554 ...
REQUESTED INFORMATION
9.03-master8
The text was updated successfully, but these errors were encountered: