Alarmo triggers after HA restart when "Allow open initially" sensors remain open

[asixpack]

Checklist

• I am using the latest version of Alarmo (latest version can be found here)
• I checked for similar existing requests (both open and closed) before posting.

Alarmo Version

v1.10.17

HA Version

2026.5.1

Bug description

When restarting Home Assistant, Alarmo is triggering due to sensors that were open both before and after the restart. The sensors are not set to "Bypass automatically" but are set to "Allow open initially." Instead, it the sensor should still be allowed to be opened.

The logs seem to show the Alarmo stored their old state as "closed" even though they were actually open.

Note there is another closed issue #1238 but this seems related to another issue (sensors being unavailable initially) that was probably fixed.

Steps to reproduce

1. Set a sensor to Allow open initially.
2. Arm Alarmo with the sensor in step 1 open.
3. Restart Home Assistant.
4. The alarm will trigger right after Alarmo starts due to the sensor in step 1 being open.

Relevant log output

2026-05-09 16:58:51.478 DEBUG (MainThread) [custom_components.alarmo.mqtt] MQTT config was (re)loaded
2026-05-09 16:58:51.479 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] alarm_control_panel.alarmo is added to hass
2026-05-09 16:58:51.479 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] Initial state for alarm_control_panel.alarmo is armed_home
2026-05-09 16:58:51.479 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from None to armed_home

2026-05-09 16:59:15.172 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for Alarmo updated to away
2026-05-09 16:59:15.173 DEBUG (MainThread) [custom_components.alarmo.sensors] Evaluating sensors on startup for area [removed] (state: armed_home)
2026-05-09 16:59:15.173 INFO (MainThread) [custom_components.alarmo.sensors] Sensor binary_sensor.alarm_panel_pro_[removed]_left_window is open on startup while alarm is armed_home - simulating state change for evaluation
2026-05-09 16:59:15.173 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.alarm_panel_pro_[removed]_left_window changed: old_state=closed, new_state=open
2026-05-09 16:59:15.173 INFO (MainThread) [custom_components.alarmo.sensors] Alarm is triggered due to sensor: binary_sensor.alarm_panel_pro_[removed]_left_window
2026-05-09 16:59:15.173 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm will be triggered after 60 seconds.
2026-05-09 16:59:15.173 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from armed_home to pending
2026-05-09 16:59:15.173 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for Alarmo updated to away, home
2026-05-09 16:59:15.174 INFO (MainThread) [custom_components.alarmo.sensors] Sensor binary_sensor.alarm_panel_pro_[removed]_other_window is open on startup while alarm is pending - simulating state change for evaluation
2026-05-09 16:59:15.174 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.alarm_panel_pro_[removed]_other_window changed: old_state=closed, new_state=open
2026-05-09 16:59:15.174 INFO (MainThread) [custom_components.alarmo.sensors] Alarm is triggered due to sensor: binary_sensor.alarm_panel_pro_[removed]_other_window
2026-05-09 16:59:15.174 WARNING (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm is triggered!
2026-05-09 16:59:15.175 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from pending to triggered
2026-05-09 16:59:15.176 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.alarmo is updated from armed_home to pending
2026-05-09 16:59:15.177 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.alarmo is updated from pending to triggered

2026-05-09 16:59:23.815 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] Service alarmo.disarm was called
2026-05-09 16:59:23.815 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] alarm_disarm
2026-05-09 16:59:23.926 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from triggered to disarmed
2026-05-09 16:59:23.927 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm 'Alarmo' is disarmed by [removed].

[nico97118]

I was not able to reproduce the issue.

• I deployed a sandbox setup with the same versions of Alarmo / Home assistant.
• Armed the alarm with a allow_open_initially sensor
• Restarted home assistant

After Home Assistant is back online :

• Alarmo is still armed
• Sensor is still open
• Alarmo is working as expected if sensor goes off then on again later.

I am not experiencing the behavior you describe and I don't see any simulating state change for evaluation
Note: all my sensor are monitored through MQTT

Logs

homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for Inside updated to home
homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.sensors] Evaluating sensors on startup for area 1775144213 (state: armed_away)
homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for Garden updated to home
homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.sensors] Evaluating sensors on startup for area 1775386101 (state: armed_away)
homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for Garage updated to home
homeassistant-sandbox  | 2026-05-10 03:36:57.215 DEBUG (MainThread) [custom_components.alarmo.sensors] Evaluating sensors on startup for area 1775386114 (state: armed_away)
homeassistant-sandbox  | 2026-05-10 03:36:57.216 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] ready_to_arm_modes for master updated to home
homeassistant-sandbox  | 2026-05-10 03:36:58.178 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.living_room_motion_sensor_motion changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.178 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.living_room_motion_sensor_motion is open
homeassistant-sandbox  | 2026-05-10 03:36:58.179 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.kitchen_motion_sensor_motion changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.179 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.kitchen_motion_sensor_motion is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.179 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.bedroom_motion_sensor_motion changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.179 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.bedroom_motion_sensor_motion is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.living_room_window_sensor_window changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.living_room_window_sensor_window is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.living_room_door_sensor_door changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.living_room_door_sensor_door is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.kitchen_window_sensor_window changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.180 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.kitchen_window_sensor_window is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.181 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.bedroom_window_sensor_window changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.181 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.bedroom_window_sensor_window is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.182 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.garage_door_sensor_door changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.182 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.garage_door_sensor_door is closed
homeassistant-sandbox  | 2026-05-10 03:36:58.183 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.garden_motion_sensor_motion changed: old_state=unavailable, new_state=unknown
homeassistant-sandbox  | 2026-05-10 03:36:58.183 DEBUG (MainThread) [custom_components.alarmo.sensors] Initial state for binary_sensor.garden_motion_sensor_motion is closed

[asixpack]

Ah, then this must have something to do with how the Konnected Alarm Panel Pro sensors are showing as "off" (Closed) on reboot for a brief second until it determines they're "on" (Open). When Home Assistant restarts, so does the Konnected device and integration. I think the sensors start as off by default and then on, or unavailable --> off --> on. Note that the log for these sensors never show the sensors as Closed (off)...but they do repeat "Was opened" after restart. (Note that the closed sensors repeat "Was closed" as well.)

Now I wonder if this is specific to Konnected or if this is just how Home Assistant's core works with all wired sensor boards.

Your sensors through MQTT must be going from unavailable/unknown to the correct state of Open, which would make sense because the MQTT client is checking the sensors which themselves do not restart when HA restarts like Konnected does.

[nico97118]

After digging a bit in the code.
I understand there is indeed a confusing behavior here.

the function _async_evaluate_armed_state_on_startup works as follows:

If the alarm is armed on startup:
  retrieve all sensor concerned by this alarm (area)
  if any sensor is open (in violation with their safe state for this arm mode) :
    then simulate their switch from safe state to open -> trigger the alarm

I'm not concerned because my setup with MQTT has the sensor in "unknown" state so they are just ignored until their state are updated.

However, now that I'm looking deeper into this, I don't see a safe way to check that the sensor is currently open but is still in its "initially open" state. The point here is when alarmo is simulating a state changes. It doesn't really knows what was the "old_state".
Instead, Alarmo assume that if the sensor is open, then the alarm should trigger.

Considering Home assistant has restarted while alarmo was armed. I would not want to simply allow the sensors with initially open enabled to be open upon restart.
This could potentially ignore an alarm violation during HA restart.

The right way would be to store the real "old_state" of sensors in order to fire an event only if the state on startup is different from the state before HA shutdown. But I don't feel anything about doing so:
1 - We do not control how HA has been restarted so I cannot trust any routines that would store the sensors state.
2 - Checking the history of the sensors (would require users enable HA recorder) would bring potential weakness on the security side imo
3 - And even then, this would add a blind spot to Alarmo since we cannot be sure the sensors did not goes "off" and back to "open" while restarting.

Finally, allow initially open is meant to give motions sensors some time to reach their safe state after you leave.
It sounds weird to me that you could have Home assistant restarting during this short timespan.
At this moment, the _async_evaluate_armed_state_on_startup is assuming the alarm was in a stable state (i.e. all sensors in safe states) and I don't see a solution to handle your use case :(

I'll keep this in the corner of my mind. Eventually I will figure out a thorough way to handle this at some point.

[asixpack]

Yes, I see the conundrum. My thought process behind having most zones to be "allowed open initially" is two fold: (1) for user adoption...to encourage the alarm to be turned on regardless of what zones are open (versus just leaving the system disarmed altogether); and (2) to increase perimeter security by allowing but not requiring windows to be closed and secured after arming.

Going forward I'll probably just enable the option to bypass the sensors automatically. Maybe I'll create an automation to disarm and re-arm if a sensor is later closed to "undue" the bypass (to achieve goal number 2 above).

[nico97118]

Thank you your understanding my dilemma on this.

I must admit I'm still confused by the use case:

to encourage the alarm to be turned on regardless of what zones are open (versus just leaving the system disarmed altogether);

I'd rather send a critical notification to explain why the alarm can't be turned on with a "force arming" action available (bypass the sensor)
However this means the sensors won't be considered until next arm, whether it gets closed and reopened until then.
On the other hand, you get notified about which sensors are open and confirm that you are "ok" with this.

(2) to increase perimeter security by allowing but not requiring windows to be closed and secured after arming.

Same as above with automatically bypass option. But I assume that's already your plan as "workaround"

---

I'm feeling the way you use allow open initially is a misuse and @nielsfaber won't be down to implement changes in order to encourage this. He has already explained Alarmo is designed in accordance with usual alarm system and he wants to keep it that way.

Going forward I'll probably just enable the option to bypass the sensors automatically. Maybe I'll create an automation to disarm and re-arm if a sensor is later closed to "undue" the bypass (to achieve goal number 2 above).

That should work, you could also run an automation at HA startup -> if alarm is armed, then disarm and arm it again.
I'm not really convinced this is a good idea but I assume you understand the weakness and are ok with it 😄

---

Unless there is still points that need to be discussed here I think we can close this issue as not planned.