Object: Door¶

A 'door' type object represents a physical or virtual entity that monitors the access state of an opening within the Netsocs ecosystem. This object is responsible for reflecting in real-time conditions such as open, closed, locked, or even in motion (for automatic gates), as well as detecting critical events such as forced attempts or closing failures.

Its functionality is fundamental for:

Access control: Managing entries to homes, offices, or restricted areas.
Automations: Activating lights when opening a door, adjusting climate control when detecting closure, or sending alerts for unexpected openings.
Security integration: Linking with alarms, cameras, or notification systems to respond to perimeter violations.
Remote monitoring: Verifying the state of doors, gates, or hatches from any location.

States¶

Possible states:¶

door.state.open → Open.
door.state.close → Closed.
door.state.lock → Locked.
door.state.opening → Opening.
door.state.closing → Closing.
door.state.unknown → Unknown.

Can represent doors, windows, gates, turnstiles, vehicle barriers, or any access point.

Iconography¶

Open¶

An open door will be displayed

Closed¶

A closed door will be displayed

Locked¶

A door with a padlock will be displayed

Beyond Open/Closed: Derived States¶

Thanks to the system's logic, we can create contextual states that the physical sensor doesn't detect directly:

left_open (Neglected) → The door remains open longer than allowed.
Example: refrigerator door open for 5 minutes.
inactive (Abandoned) → The door hasn't changed state in a long time.
Example: emergency access without use.
forced (Forced) → The door opens while the Alarm Panel is armed.
Example: possible intrusion.
tampered (Tampered) → Anomalous signals detected, possible sensor sabotage.

These states are configured through rules and automations, allowing advanced supervision and proactive responses to situations that go beyond simple opening or closing.