Alarmo armed despite open sensor

[adunaph3l]

Alarmo Version

v1.9.5

HA Version

2022.8.7

Bug description

Despite I've open sensor, Alarmo still arms itself. And if I close then reopen the sensor while armed, it doesn't trigger the alarm. If I close the window during the activation (if I set an exit delay), the sensor will trigger the alarm once Alarmo is activated.

I've tried all sensor mode (door, windows etc), check/uncheck exit/entry delay, still nothing. I can't have Alarmo failed to arm if I have a sensor which is open. Sensor model : Aqara Door and Windows Sensor

Steps to reproduce

No response

Relevant log output

No response

[quintenbuijs2006]

Did you set the sensor in alarmo panel?

[adunaph3l]

Yes, all sensors are setup in each mode (away, present etc...)

[quintenbuijs2006]

Than i don't know try contacting the developer

[nielsfaber]

Did you set up Alarmo with multiple areas? If so, the sensors need to be assigned to the correct areas.

Otherwise, please enable debug logging by adding this to the configuration.yaml and restarting HA:

logger:
  default: warning
  logs:
    custom_components.alarmo: debug

Afterwards, open the door and arm the alarm. Please share the results of the HA log here.

[adunaph3l]

Hi @nielsfaber !

Thanks to take some times for the problem. Every sensor are in one and only one zone

You can see that the alarm can be armed despite one opened sensor :

I've activated the debug and here is the result : 2022-09-09 08:29:27.914 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] alarm_arm_away 2022-09-09 08:29:28.318 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm is now arming. Waiting for 20 seconds. 2022-09-09 08:29:28.319 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.maison was updated from disarmed to arming 2022-09-09 08:29:28.321 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.maison is updated from disarmed to arming 2022-09-09 08:29:48.320 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] async_leave_timer_finished 2022-09-09 08:29:48.321 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm 'Maison' is armed (armed_away) by Olivier. 2022-09-09 08:29:48.321 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.maison was updated from arming to armed_away 2022-09-09 08:29:48.323 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.maison is updated from arming to armed_away 2022-09-09 08:29:48.323 DEBUG (MainThread) [custom_components.alarmo.automations] executing automation 1656320629 2022-09-09 08:30:47.645 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] alarm_disarm 2022-09-09 08:30:48.057 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.maison was updated from armed_away to disarmed 2022-09-09 08:30:48.057 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm 'Maison' is disarmed by Olivier. 2022-09-09 08:30:48.057 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.maison is updated from armed_away to disarmed

[nielsfaber]

Can you please add logging of the opening of the window and then arming the alarm? It is apparently not detected by Alarmo. A screenshot of the settings of this sensor would also be useful. I assume you don't use sensor groups for it?

[adunaph3l]

How can I add debug for my sensor ? logger: default: warning logs: custom_components.alarmo: debug binary_sensor.fenetre_bureau_olivier: debug

But nothing in the log when I open/close the window, but HA sees the opening etc ...

[nielsfaber]

Alarmo only checks the sensor when needed, so when the alarm is disarmed you will not see any logging of the sensor changes. But you should see something if the sensor is triggered when the alarm is arming or armed. Example:

2022-09-09 08:59:40.764 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] Service alarmo.arm was called, 2022-09-09 08:59:41.330 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm is now arming. Waiting for 10 seconds., 2022-09-09 08:59:41.331 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from disarmed to arming, 2022-09-09 08:59:41.338 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.alarmo is updated from disarmed to arming, 2022-09-09 08:59:44.919 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.backdoor changed: old_state=closed, new_state=open, 2022-09-09 08:59:44.919 DEBUG (MainThread) [custom_components.alarmo.sensors] Arming was aborted due to a sensor being active: binary_sensor.backdoor, 2022-09-09 08:59:44.919 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from arming to disarmed, 2022-09-09 08:59:44.922 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.alarmo is updated from arming to disarmed, 2022-09-09 08:59:44.938 DEBUG (MainThread) [custom_components.alarmo.automations] alarm_control_panel.alarmo has failed to arm 2022-09-09 08:59:40.764 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] Service alarmo.arm was called, 2022-09-09 08:59:44.938 DEBUG (MainThread) [custom_components.alarmo.automations] alarm_control_panel.alarmo has failed to arm

[adunaph3l]

Ok, I've tried this : I'm arming Alarmo, then, while it's arming, I opened the window : Alarmo failed to arm, and I can see it in the log : 2022-09-09 09:05:42.963 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm is now arming. Waiting for 20 seconds. 2022-09-09 09:05:42.963 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.maison was updated from disarmed to arming 2022-09-09 09:05:42.964 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.maison is updated from disarmed to arming 2022-09-09 09:05:47.114 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.fenetre_bureau_olivier changed: old_state=closed, new_state=open 2022-09-09 09:05:47.115 DEBUG (MainThread) [custom_components.alarmo.sensors] Arming was aborted due to a sensor being active: binary_sensor.fenetre_bureau_olivier 2022-09-09 09:05:47.115 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.maison was updated from arming to disarmed 2022-09-09 09:05:47.115 DEBUG (MainThread) [custom_components.alarmo.automations] state of alarm_control_panel.maison is updated from arming to disarmed 2022-09-09 09:05:47.116 DEBUG (MainThread) [custom_components.alarmo.automations] alarm_control_panel.maison has failed to arm 2022-09-09 09:05:47.116 DEBUG (MainThread) [custom_components.alarmo.automations] executing automation 1656320891

I thought that if I already have an opened window, Alarmo won't arm because of this opened window, but maybe it works as intended and it's a feature to be added in a near future ?

[nielsfaber]

I thought that if I already have an opened window, Alarmo won't arm because of this opened window, but maybe it works as intended and it's a feature to be added in a near future ?

It depends on the settings of the sensors. If I try to arm the alarm with the backdoor still open, it is not allowed:

2022-09-09 09:09:18.448 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] Service alarmo.arm was called, 2022-09-09 09:09:19.015 DEBUG (MainThread) [custom_components.alarmo.automations] alarm_control_panel.alarmo has failed to arm, 2022-09-09 09:09:19.011 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Cannot arm right now, there are open sensors

These settings of the sensor are relevant:

[adunaph3l]

I've set my window sensor like yours (device type: door, and the same parameters as yours), I opened my window, and Alarmo can still be armed despite HA see the sensor as opened :(

[nielsfaber]

The same settings would give the same results. There must be some difference which we are overlooking. But from here it's difficult to identify this. Did you select the appropriate 'enabled modes' ? Did you you leave the 'group' setting empty?

[adunaph3l]

Sorry, was on holidays.

Yes, everything is set up as you asked

[nielsfaber]

Can you share the log results of opening the window and then arming alarmo? I would expect to see the arming fail immediately with this logging result:

2022-09-09 09:09:19.011 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Cannot arm right now, there are open sensors

[rucanunes]

I have the exact same problem....

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days