Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Group in Alarmo (2x Doors) trigger immediately instead of after consecutive opens. #933

Open
vaemarr opened this issue May 5, 2024 · 3 comments
Open

Group in Alarmo (2x Doors) trigger immediately instead of after consecutive opens. #933

vaemarr opened this issue May 5, 2024 · 3 comments
Labels
bug Something isn't working waiting for user input

Comments

@vaemarr
Copy link

vaemarr commented May 5, 2024

Alarmo Version

1.10.0

HA Version

2024.4.3

Bug description

I have an alarmo group consisting of 2x door sensors - my garage door and another inner door in the garage.

Both have 'Use entry delay enabled'.

Alarmo Group timeout is set to 5 mins. Both sensors are selected for the group.

I only need to activate one sensor (open the door) before the alarm is triggered. Instead of having to activate another sensor within the minute window as you would expect.

I can't workout why this is happening.

Steps to reproduce

Setup 2 testing scenarios. One to only open the inner door - the other to open the garage.

Waited for 15 mins between each test to be sure no timeout was active.

Checked group settings to be sure setup is correct.

Opened different doors in each test, but only one door.

Alarmo is immediately triggered despite a 2nd activation not occuring.

Relevant log output

Not sure where to get this.
@vaemarr vaemarr added the bug Something isn't working label May 5, 2024
@nielsfaber
Copy link
Owner

In an attempt to reproduce this issue, I created a sensor group like this:

Both sensors are configured to be active in the 'armed home' and 'armed away'.
With all sensors closed, I arm the alarm in mode 'armed away'. When the system is armed I open the front door.
The debug log now shows:

2024-05-08 14:14:25.575 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.frontdoor changed: old_state=closed, new_state=open
2024-05-08 14:14:25.575 DEBUG (MainThread) [custom_components.alarmo.sensors] tripped sensor binary_sensor.frontdoor was ignored since it belongs to group My Group

The alarm remains in state 'armed away'.
Next I open the front door.
The debug log now shows:

2024-05-08 14:18:06.409 DEBUG (MainThread) [custom_components.alarmo.sensors] entity binary_sensor.back_door changed: old_state=unavailable, new_state=open
2024-05-08 14:18:06.410 DEBUG (MainThread) [custom_components.alarmo.sensors] tripped sensor binary_sensor.back_door caused the triggering of group My Group
2024-05-08 14:18:06.410 INFO (MainThread) [custom_components.alarmo.sensors] Alarm is triggered due to sensor: binary_sensor.back_door
2024-05-08 14:18:06.410 DEBUG (MainThread) [custom_components.alarmo.alarm_control_panel] entity alarm_control_panel.alarmo was updated from armed_away to pending
2024-05-08 14:18:06.411 INFO (MainThread) [custom_components.alarmo.alarm_control_panel] Alarm will be triggered after 5 seconds.

In summary, opening the first door is ignored, the second one triggers the alarm.
This works as the function is intended to work.

I cannot reproduce the problem you are experiencing.
Please provide more information if you think something is wrong within Alarmo.

If you wish to see debug logging, you can do so by adding this to the configuration.yaml:

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

The extra information should appear in the HA logs.

@vaemarr
Copy link
Author

vaemarr commented May 8, 2024 via email

@sato9882
Copy link

Alarmo Version
1.10.1

HA Version
2024.5.2

Bug description
Same behavior as vaemarr.
Opening just one door will trigger an alarm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working waiting for user input
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nielsfaber @vaemarr @sato9882