If they persist, then the same one is always picked up as the unlock reason. They need to not persist so that the latest one is always recognised. Issue #796
@@ -18,6 +18,7 @@ primary_entity:
# this is a guess for "lock_motor_state"
name: jammed
optional: true
+ persist: false
mapping:
- dps_val: null
value: false
@@ -25,31 +26,38 @@ primary_entity:
type: string
name: unlock_fingerprint
- id: 11
name: unlock_password
- id: 12
name: unlock_card
- id: 15
# "double" in Tuya doc, but no idea what that means. Key is unused.
name: unlock_key
- id: 16
name: unlock_temp_pwd
- id: 17
name: unlock_offline_pwd
- id: 22
name: unlock_app
- id: 23
name: lock_alarm_kit