-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Yale doorman state loop #159
Comments
Interesting, anything in the logs? |
I’m seeing this 2023-04-01 14:22:40Verisure Bridgeverisure SmartLock (Entré dörr): Setting target lock state to: 0 |
Also this 2023-04-01 20:55:38Verisure BridgeERROR[Verisure Bridge 6ADE@Lock Target State] The write handler for the characteristic 'Lock Target State' on the accessory 'SmartLock (Entré dörr)' was slow to respond! |
Any updates with this issue, seems that I have same problem. |
Yes, for me too. |
I opened up pull request #161 to hopefully fix this issue. |
Any progress? |
@ptz0n, could you review the pull request? |
@ptz0n any progress? :) |
Yes, can you review the pull request? |
Any update? |
Could you please review the pull request? Thank! |
I also experience this phenomenon. Latest version of Homebridge/plugin |
@ptz0n this seems to work. Can you have a quick look? |
@torandreroland or anyone that got time, we need to add some tests. I'll see what I can do with my limited javascript knowledge :) |
@devkmadh: Added test now. Hopefully this can be merged and new version pushed. |
Has this been merged. I still have the problem, and it sometime causes the API calls to Verisure to exceed the limited and the account is block for the rest of the day. |
Please fix this |
Sometimes I’ll find my lock in this state. Usually it’s when unlocking and locking manually on the door. It will say locking but it’s in fact already locked. Confirmed physically and in the Verisure app. This started with 2.0.0.
The text was updated successfully, but these errors were encountered: