alarm_trigger service disarms instead of triggering

[GussyH]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):

0.24.0

Python release (python3 --version):

Python 3.4.2

Component/platform:

alarm_control_panel

Description of problem:

alarm_trigger service disarms the alarm!

Regardless of whether the alarm is in an armed or disarmed state, calling the alarm_trigger service appears to first set the state to 'pending' and then to 'disarmed'. This is the opposite of what you'd want.....

Expected:

The alarm should enter the triggered state, and remain in that state until disarmed.

Problem-relevant configuration.yaml entries and steps to reproduce:

alarm_control_panel:
  platform: manual
  name: "HA Alarm"
  code: xxxx
  pending_time: 20
  trigger_time: 20

1. arm the alarm
2. call alarm_trigger
3. watch the state - it goes to Pending then Disarmed

Traceback (if applicable):

Additional info:

[tobiebooth]

This actually works properly in HASS but the Polymer UI doesn't handle the triggered state: https://github.com/home-assistant/home-assistant-polymer/blob/master/src/components/entity/ha-state-label-badge.html#L124

Perhaps this issue should be moved to https://github.com/home-assistant/home-assistant-polymer/issues?

[GussyH]

Not sure that's completely correct - I think there might be two issues. One the badge (and popup?) is wrong (says pending when history does show triggered) but second is then that it disarms itself(which is definitely bad!).

[tobiebooth]

I think that would actually be expected behavior (most if not all professional alarm systems disarm after alarm, example: Simplisafe.

However it might be nice to add an optional setting to return to the previous arm state (home or away).

[GussyH]

Hmmm really? Seems odd as if you have a false alarm, your house is now not protected until you can check it and reset it. My Yale doesn't work that way......

[emilhetty]

I edited the code to return to arm_away after trigger since I'm only using away and I don't know how to add previous state.
Could post the code if you would like to?

It have been nice to have a option to return to previous state instead of disarm when triggered.

[GussyH]

Shouldn't it just stay in the triggered state until someone manually does something about it?

[GussyH]

@tobiebooth do we need to create a separate issue for the polymer display problem?

[tobiebooth]

Probably, I'll get to fixing it sometime this weekend.

[GussyH]

Raised home-assistant/frontend#84