door or gate unlocked
This block is part of the globals group and was last modified in core v15.0.0.
door or gate unlocked v15.0.0 Starts the flow when the lock releases, whether or not the door then opens.
- device
valuev15.0.0Only fire for this device. Leave empty to fire for every matching device.
- room
valuev15.0.0Only fire for devices in this room. Leave empty for every room.
- flow
v15.0.0 - device
objectv15.0.0The full device: id, name, room, type, capabilities, current state.
- device id
valuev15.0.0Stable platform id, e.g. zigbee:0x00158d0007e1a2b3.
- name
valuev15.0.0The device's friendly name.
- room
valuev15.0.0The room the device is assigned to, empty if none.
- type
valuev15.0.0sensor, light, switch, climate, cover, lock or button.
- capability
valuev15.0.0Which capability changed, e.g. occupancy, contact, power.
- value
valuev15.0.0The new value.
- previous
valuev15.0.0The value before this change, empty on the first report.
- at
numberv15.0.0Unix seconds the device reported.
Start-of-flow trigger on the lock_state capability transitioning to "unlocked". This is the ELECTRICAL state of the lock, not the physical position of the door : use door_opened for that. A momentary unlock fires this and then fires door_locked again seconds later when the relay re-locks itself, which is normal.
zigbee |
zwave |
matter |
thread |
smart home |
home assistant |
trigger |
A lock changing to unlocked is not the same event as a door opening: it happens when somebody turns a key, presses a button or when an automation releases it. door unlocked is therefore the trigger for auditing the lock itself, and the previous pin lets you tell a genuine change from a device repeating what it already said.
Used in these guides
These documentation pages use or explain this block:
Version history
Introduced in v15.0.0.
Back to
globals Return to the main group to view all sub-groups Back to home Return to the group to view all blocks within this group