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.

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

override sensors remain ignored after arming, and immediate sensors don't trigger during warning #38

Open
jcooper-korg opened this issue Aug 26, 2018 · 3 comments

Comments

@jcooper-korg
Copy link

related to #15

I noticed an issue with “override sensors”. I have set up my armed_away mode as follows:

 armed_away: 
  #[OPTIONAL] State specific overrides default time above
  trigger_time: 600  
  ##[OPTIONAL however either an immediate or delayed group must exist] Sensors in this group tigger the alarm immediately 
  immediate:
    - binary_sensor.door_side_garage
    - binary_sensor.window_office
    - binary_sensor.window_living_room
    - binary_sensor.window_dining_room
    - binary_sensor.window_master_bedroom
  ##[OPTIONAL] Sensors in this group start the clock (pending_time) when tripped before the alarm is triggered 
  delayed:
    - binary_sensor.door_front
    - binary_sensor.door_garage
  #[OPTIONAL] Use this group to automatically override the warning message on open sensors when arming. (I use this as I have a motion sensor at the front door)
  override:
    - binary_sensor.motion_hall
    - binary_sensor.motion_living_room

I specified “override” for the motion sensors for the same reason as specified in the comments- I need to be able to walk around the doors while arming and leaving. That works.

However, once the alarm is armed_away, the motion sensors remain on the inactive list, and do not trigger the siren if there is motion. Really, they should only be ignored while in the pending arming stage, and they should trigger the siren immediately if there is motion after arming.

Furthermore, it appears that immediate zones do not trigger during the re-entry warning state. That doesn’t seem right.
If the alarm is armed away, and I open the front door, it starts the warning count-down ok- but if I then open or break a window while still counting-down, it really should trigger the alarm. And in this state, the motion detectors should be overridden to allow walking down the hall to turn off the alarm.
Based on the comments, it seems that’s what the override option in alarm.yaml is intended for, but it’s not working that way.

@jcooper-korg
Copy link
Author

I'm running latest HA 0.76.2 on current hassbian. Sensors/siren are on nodemcu running konnected.io and are working properly.

@gazoscalvertos
Copy link
Owner

I'll check this out thanks for the heads up

@jcooper-korg
Copy link
Author

I forked and fixed this in my repo. Take a look: https://github.com/jcooper-korg/Hass-Custom-Alarm/commits/johns-customizations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants