gate closed

This block is part of the globals group and was last modified in core v15.0.0.

gate closed object v15.0.0

Starts the flow when the gate physically closes.

In pins 2

device v15.0.0
value
Only fire for this device. Leave empty to fire for every matching device.
room v15.0.0
value
Only fire for devices in this room. Leave empty for every room.

Out pins 9 + flow

flow v15.0.0
flow
device v15.0.0
object
The full device: id, name, room, type, capabilities, current state.
device id v15.0.0
value
Stable platform id, e.g. zigbee:0x00158d0007e1a2b3.
name v15.0.0
value
The device's friendly name.
room v15.0.0
value
The room the device is assigned to, empty if none.
type v15.0.0
value
sensor, light, switch, climate, cover, lock or button.
capability v15.0.0
value
Which capability changed, e.g. occupancy, contact, power.
value v15.0.0
value
The new value.
previous v15.0.0
value
The value before this change, empty on the first report.
at v15.0.0
number
Unix seconds the device reported.

Start-of-flow trigger on door_position becoming false for a gate. The natural pair for 'the gate has been open too long': start a timer on gate_opened and cancel it here.

zigbee

zwave

matter

thread

smart home

home assistant

trigger

gate closed completes the pair. It is the event that lets an automation stop worrying: arm a perimeter, stop a recording, or clear the "gate is open" state on a dashboard. Deriving it from a timer after the open instead is what leaves a site reporting secure while the gate is stuck half way.

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