Yale doorman state loop
Opened this issue · 18 comments
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.
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
2023-04-01 14:22:40Verisure Bridgeverisure SmartLock (Entré dörr): Resolving: pollLockState
2023-04-01 14:22:41Verisure Bridgeverisure SmartLock (Entré dörr): Got "null" back from: pollLockState
2023-04-01 14:22:41Verisure Bridgeverisure SmartLock (Entré dörr): Resolving: pollLockState
2023-04-01 14:22:41Verisure Bridgeverisure SmartLock (Entré dörr): Got "null" back from: pollLockState
2023-04-01 14:22:41Verisure Bridgeverisure SmartLock (Entré dörr): Resolving: pollLockState
2023-04-01 14:22:41Verisure Bridgeverisure SmartLock (Entré dörr): Got "null" back from: pollLockState
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
@torandreroland or anyone that got time, we need to add some tests. I'll see what I can do with my limited javascript knowledge :)
#161 (comment)
@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