Feature Proposal: Auth data in unlock state about nuki_hub HOT 3 CLOSED

Can you share how? When using the lock unlock state I always ran into race conditions since other values updated at different times. On 11. May 2024, at 15:31, iranl ***@***.***> wrote:  Thanks for sharing your automation. I don't think the sensor is necessary though, this automation should work without a separate sensor: alias: "Access: Nuki Keypad Advanced Action" description: "" trigger: - platform: mqtt topic: "nukiopener/lock/json" payload: "open" value_template: "{{ value_json.lock_state }}" condition: - condition: template value_template: "{{ state_attr(\"input_select.people_group_owners\", \"options\") | select('match', trigger.payload_json.auth_name) | replace(' (Keypad)', '')) | list |\_count > 0}}" action: - device_id: xxxxxxxxxxxxxxxxxxxx domain: button entity_id: yyyyyyyyyyyyyyyy type: press mode: single As such I don't see a reason to change the HA auto discovery code of Nuki Hub. — Reply to this email directly, view it on GitHub<#352 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABX5EXGHU5264O3QP3MWFJLZBYMSRAVCNFSM6AAAAABHQVC66KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBVG42DMMRUGI>. You are receiving this because you authored the thread.Message ID: ***@***.***>