I am facing a strange behavior for the pendingdelay timings in the alarm panel.
I have configured:
alarm_control_panel:
- platform: manual
name: Home Alarm
code: 7737
pending_time: 60
delay_time: 60
trigger_time: 15
disarmed:
trigger_time: 0
armed_home:
pending_time: 0
delay_time: 0
trigger_time: 5
armed_away:
delay_time: 60
In “armed_home” mode I triggered an alarm. I would expect that there is no delay time between triggering alarm an the execution of the alarm trigger. What I observe is different though:
The alarm is triggered at 3:49:57pm. The event goes to “pending” immediately and then changed to “triggered” at 3:50:58pm, which equals roughly 60 seconds but not the delay_time: 0 seconds under “armed_home”.
The event changes back to “armed_home” at 3:51:03pm - exactly the 5 seconds of defined “trigger_time”.
Then I switch the mode to “armed_away” at 3:53:33pm - shown by the event state “pending”. At 3:54:33pm the event changes to “armed_away”. This is as expected: default pending_time: 60.
I trigger an alarm at 3:55:27pm. The event switches to “pending”. At 3:57:28pm the event changes to "triggered. This is 120 seconds but not the defined 60 seconds.
The event changes back to “armed_away” at 3:57:43pm - exactly the 15 seconds of defined default “trigger_time”.
It seems that pending_time and delay_time of the individual modes are added(!) to the default times delay_time respectively pending_time.
While not shown here this behavior also seems to apply to pending_time.
Can anybody comment on this?
