esphome / esphome/feature-requests

Feature request: Alarm Control Panel

Open
#2,307 2 comments 0 reactions 0 assignees View on GitHub
component: alarm_control_panel
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

1. Add per-zone entry delay attribute so that some zones would remain as instant, (example: glass break detectors) while others would would trigger the pending timer (example: front door)
2. For the alarm control panel during the time it is in the pending state, add an attribute to disable certain zones set to instant alarm so that the alarm isn't triggered by the PIR's due to people walking to the disarm point.

**Please describe your use case for this integration and alternatives you've tried:**

1. A user comes home, and enters through the front door. The alarm state goes to pending. Unbeknownst to the user, a home invasion burglar is waiting for the user to come home, they then break a window covered by a glass break sensor to enter just after a user enters through the front door. In the existing code there would be no alarm as all zones go through the pending timer before triggering the alarm.
2. When a user arrives home Passive Infrared Sensors could be triggered when the user makes their way to the disarm point. If these are set to instant per use case 1 above, then the alarm is going to get triggered inadvertently. However if an attribute is set preventing triggers in the pending state for the PIR sensors which will get triggered then the alarm can be disarmed before the pending state timer expires.

**Additional context**

This feature is implemented on the Ademco/Honeywell Vista 20 panel

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing alarm control panel implementation and understanding how zones and the pending state are represented. Define how per-zone entry delays and pending-state zone suppression should interact, using the two home-entry scenarios in the issue as acceptance cases. Done means both behaviors work without causing unintended alarms.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.