Hi there,
Firstly - thanks for the great work on this, has really improved the usability (aka Wife Acceptance Factor) of our Yale Locks (with Zigbee module.
However, yesterday I managed to lock her out of the house by toggling the 'Code Status' for a code slot that wasn't hers.
Took a bit of digging into but the root cause is that the Code Slots on the Yale locks are offset by +1 when accessed via the Zigbee calls. In my oopsie yesterday, I disabled Code Slot 3 in the ZLM UI, which we had used temporarily for a house sitter, which sends a 'zha.disable_lock_user_code' call for Slot 3. However, because of the offset on the Yale locks, this actually disables what is labelled up as Slot 2 on the UI.
Easy fix on my end, I just updated the automation details in the package to refer to slots "2 - 11" instead of "1 - 10" and it's behaving fine.
Different ways this could be addressed, maybe just a simple note in the documentation telling people about the above in the context of Yale Assure locks. Could be an extra Q in the setup steps that asks if the lock has an offset and then makes the adjustment in the automations when it creates the package files.
Hi there,
Firstly - thanks for the great work on this, has really improved the usability (aka Wife Acceptance Factor) of our Yale Locks (with Zigbee module.
However, yesterday I managed to lock her out of the house by toggling the 'Code Status' for a code slot that wasn't hers.
Took a bit of digging into but the root cause is that the Code Slots on the Yale locks are offset by +1 when accessed via the Zigbee calls. In my oopsie yesterday, I disabled Code Slot 3 in the ZLM UI, which we had used temporarily for a house sitter, which sends a 'zha.disable_lock_user_code' call for Slot 3. However, because of the offset on the Yale locks, this actually disables what is labelled up as Slot 2 on the UI.
Easy fix on my end, I just updated the automation details in the package to refer to slots "2 - 11" instead of "1 - 10" and it's behaving fine.
Different ways this could be addressed, maybe just a simple note in the documentation telling people about the above in the context of Yale Assure locks. Could be an extra Q in the setup steps that asks if the lock has an offset and then makes the adjustment in the automations when it creates the package files.