nuki_hub: Using "Lock'n'go" does not change the lock state
It appears that when using the “Lock’n’go” feature (e.g. via a double click of the lock button), the state of the lock entity in Home Assistant is not updated (i.e. neither the lock nor unlock action register in the logbook, it looks as if the lock remained closed).
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- fixed issue #23: Using Lockngo does not change the lock state — committed to technyon/nuki_hub by technyon 2 years ago
Hi,
I finally had some time to setup my own HA testing instance. I’ve fixed the issue a bit differently than suggestet: I created a new “binaryState” that maps the other states to either locked or unlocked, and changed the HA config accordingly.
Could you test if this fixes the issue (you’ll eventually have to disable and enable the HA integration --> clear and enter HA path).
nuki_hub.zip
Maybe also include “unlatching” and map it to unlocked. I haven’t seen it very often, but just for the sake of completeness maybe include it.