gate opened
This block is part of the globals group and was last modified in core v15.0.0.
gate opened v15.0.0 Starts the flow when the gate physically 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 door_position becoming true for a gate. Identical in mechanism to door_opened : a gate is a door to the controller : and separate so gate automations read as gate automations. Select the gate in the device pin; with no device selected it fires for any door-type device, which is probably not what a block called 'gate opened' should do.
zigbee |
zwave |
matter |
thread |
smart home |
home assistant |
trigger |
gate opened fires when the movement completes rather than when the command was sent, which is the distinction that matters for anything chained behind it. It is the trigger to hang a close-again timer on, and the one that tells a camera flow that a vehicle is about to arrive.
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 