alarm_control_panel.abode_alarm does not report alarm triggered state

[bobbeims]

The problem

When an alarm is triggered on an Abode system that is connected via the Abode integration, the alarm_control_panel.abode_alarm entity state should transition to "triggered" but it doesn't. Other state changes are reported (and captured in the log).

What version of Home Assistant Core has the issue?

Supervisor 2022.10.0, Operating System 9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Abode

Link to integration documentation on our website

https://www.home-assistant.io/integrations/abode

Diagnostics information

Log book in HA:

Log in Abode app:

Example YAML snippet

alias: Alarm turns lights on
trigger:
  - platform: state
    entity_id:
      - alarm_control_panel.abode_alarm
    enabled: true
    to: triggered
condition: []
action:
  - service: light.turn_on
    data:
      brightness_pct: 100
    target:
      area_id:
        - back_porch
        - breakfast
        - dining_room
        - driveway
        - front_entry
        - front_porch
        - game_room
        - garage
        - garage_entry
        - guest_bath
        - guest_bath_up
        - guest_bed
        - guest_bed_up
        - hallway
        - kid_s_room
        - kitchen
        - laundry_room
        - living_room
        - master_bath
        - bedroom
        - master_closet
        - office
  - service: switch.turn_on
    data: {}
    target:
      area_id:
        - back_porch
        - breakfast
        - dining_room
        - driveway
        - front_entry
        - front_porch
        - game_room
        - garage
        - garage_entry
        - guest_bath
        - guest_bath_up
        - guest_bed
        - guest_bed_up
        - hallway
        - kid_s_room
        - kitchen
        - laundry_room
        - living_room
        - master_bath
        - bedroom
        - master_closet
        - office
mode: single

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @shred86, mind taking a look at this issue as it has been labeled with an integration (abode) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of abode can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant unassign abode Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

abode documentation
abode source
_{^{(message by IssueLinks)}}

[npentell]

Also doesn't appear to be logging abode_automation: Fired when an Automation is triggered from Abode either. Should I raise a separate issue?

[bobbeims]

@npentell I have observed that non-trigger behavior, too. In case the root cause is different, then I’d suggest opening a separate issue for accuracy in tracking.

[npentell]

Anything I can do to help with this? I'm eager to get it fixed as well.

[whereizben]

Any idea if this has been resolved? I only just realized it was an issue when I came here about the fact that the state is now not updating at all and saw this open issue (thankfully, it’s been a while since our alarm was triggered!)

[bobbeims]

@whereizben the Home Assistant 2023.2 release included an update to the Abode integration. I haven’t tested the alarm trigger event, yet, but you might give it a shot.

[whereizben]

@bobbeims I think that update is what broke alarm state change updates in general, when I performed it is when the alarm state stopped updating at all. See #86765

…

On Fri, Feb 3, 2023, 07:15 Bob Beims ***@***.***> wrote: @whereizben <https://github.com/whereizben> the Home Assistant 2023.2 release included an update to the Abode integration. I haven’t tested the alarm trigger event, yet, but you might give it a shot. — Reply to this email directly, view it on GitHub <#80754 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKGDZRYAL2SUHEIIOO6QGATWVUOHLANCNFSM6AAAAAARLPNXHI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tcochran1987]

It seems as though at least with the recent update it goes to unavailable or misses information from the gateway when you try to Arm it in either the Away or Home mode, because when I look at the history it show a void correlating to when the system is armed in either way, then when I disarm it it shows the current status.

[St3ve1988]

Hello, bumping this because I am having the same issue with the new Home Assistant update. 2023.2 seems to have broken the Abode integration. I installed the update yesterday. Here's the funny thing though. alarm_control_panel.abode_alarm did not update it's status at all yesterday, but when I woke up today it said that it was armed in home mode (an HA automation arms it overnight for me) after the time when it should have disarmed. When I checked the Keypad 2, it showed that it was in Standby (disarmed).

I power cycled the Abode hub thing (iota?) and it appeared to have fixed it. So I tried arming the system. Yet again, it did not send an update to HA through alarm_control_panel.abode_alarm. I thought I saw a fix for this floating around on GitHub but could not find it again in a quick search this morning. I have considered rolling back to the previous HA core until I can find a different solution.

Thanks for any other help that anyone has, in advance.

[TBE4034]

To get that fix for the missed status changes you’ll need to update to the :dev release.

[St3ve1988]

To get that fix for the missed status changes you’ll need to update to the :dev release.

I'm very amateur and have been making this up as I go along, so I'm not sure how to do that. Is there anywhere that I can find direction on that? Also, do you mean the HA :dev release or are you talking about the integration itself?

[TBE4034]

The dev release of home assistant.
I use docker so changed my image name to

image: homeassistant/home-assistant:dev

If not using docker I’m not familiar with how to do this.

Note that this fixed the status updates broken in 2022.2 but I haven’t yet tested the alarm notifications which have been broken for a while.

Also note that while this fixed the abode status updates, the dev branch can be unstable and I have noticed some odd things but nothing serious. A better option may be to roll back to 2023.1 until this fix is put into an official release.

[npentell]

I just rolled back the core for now. ha core update --version 2023.2.1 (put the date of your most recent backup before the issue) As for the state reporting of the alarm. What I did was go into the abode app and set up a CUE (that's abode's name for an automation) for each state I wanted to use in HA. I think there's one for smoke, CO, burglar, etc that can be set up. Then I set up automations for each in HA and used the CUE notification as the trigger. Here's my automation alias: Abode trigger CUE CO/Smoke description: "" trigger: - platform: event event_type: abode_automation event_data: event_name: "Automation : CO Alarm" - platform: event event_type: abode_automation event_data: event_name: "Automation : Smoke Alarm" condition: [] action: - if: - condition: template value_template: "{{ trigger.event.data.event_name == \"Automation : CO Alarm\" }}" then: - service: input_text.set_value data: value: Carbon Monoxide target: entity_id: input_text.abode_what_s_detected else: - if: - condition: template value_template: "{{ trigger.event.data.event_name == \"Automation : Smoke Alarm\" }}" then: - service: input_text.set_value data: value: Smoke target: entity_id: input_text.abode_what_s_detected - service: input_text.set_value data: value: "{{ trigger.event.data.device_id }}" target: entity_id: input_text.abode_smoke_detector - service: script.s data: {} mode: parallel Pardon the formatting. I'm just replying through email

…

On Wed, Feb 8, 2023, 7:10 AM TBE4034 ***@***.***> wrote: The dev release of home assistant. I use docker so changed my image name to image: homeassistant/home-assistant:dev If not using docker I’m not familiar with how to do this. Note that this fixed the status updates broken in 2022.2 but I haven’t yet tested the alarm notifications which have been broken for a while. Also note that while this fixed the abode status updates, the dev branch can be unstable and I have noticed some odd things but nothing serious. A better option may be to roll back to 2023.1 until this fix is put into an official release. — Reply to this email directly, view it on GitHub <#80754 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5VHHH4OFHEDNCLNGON7PDWWOEKPANCNFSM6AAAAAARLPNXHI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nathang21]

I just confirmed that the 2023.2.3 release which included some abode fixes, did not resolve the status not syncing issue.

[TBE4034]

The dev release fixed the system armed status for me at least.

I believe that for concerns with the system arm status (home, away, standby) changes not updating in HA, you should use issue #86765

While this issue is concerning alarm triggering not making it to HA.

[kevdliu]

As a workaround I made the following trigger sensor so I can check whether the alarm is in progress atm:

- trigger:
  - platform: event
    event_type: abode_alarm_end
  - platform: event
    event_type: abode_alarm
  binary_sensor:
    - name: Alarm In Progress
      state: '{{ trigger.event.event_type == "abode_alarm" }}'
      icon: mdi:alarm-light

I imagine you can probably make a template alarm control panel that integrates the actual abode alarm control panel and the above trigger sensor to achieve what you're looking for.

[TBE4034]

While they may be workarounds for this, I had an alarm today and verified this is still an issue. Abode Alarm entity has no history/log of the alarm having occurred at all.

[bobbeims]

Bumping this, as others have, with a minor addition. I have an "Abode event test" automation that can be triggered by all of the documented Abode integration events and simply sends a notification to my phone. In addition to an alarm event not triggering, the "abode_capture" event also does not trigger, even though I've verified that one of my cameras captured a person and that capture is recorded in the Abode app log.

alias: Abode event test
trigger:
  - platform: event
    event_type:
      - abode_alarm
  - platform: event
    event_type:
      - abode_alarm_end
  - platform: event
    event_type:
      - abode_arm
  - platform: event
    event_type:
      - abode_arm_fault
  - platform: event
    event_type:
      - abode_automation
  - platform: event
    event_type:
      - abode_capture
  - platform: event
    event_type:
      - abode_device
  - platform: event
    event_type:
      - abode_disarm
  - platform: event
    event_type:
      - abode_panel_fault
  - platform: event
    event_type:
      - abode_panel_restore
  - platform: event
    event_type:
      - abode_test
  - platform: state
    entity_id:
      - alarm_control_panel.abode_alarm
    to: armed_home
  - platform: state
    entity_id:
      - alarm_control_panel.abode_alarm
    to: armed_away
action:
  - service: notify.mobile_app_bobs_iphone_se
    data:
      message: "Abode event: {{ trigger.event.data.event_name }}"
mode: parallel
max: 10

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[TBE4034]

I just verified this is still an issue in the latest release. In my opinion this should be the top priority for the abode integration. A security system that is unable to notify when it’s alarm is triggered.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[TBE4034]

Still an issue.

[npentell]

Fyi , I ended up setting up cues in abode and capturing them in home assistant for automation.

…

On Tue, Oct 3, 2023, 8:27 PM TBE4034 ***@***.***> wrote: Still an issue. — Reply to this email directly, view it on GitHub <#80754 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE5VHHBAURE6HDXK6WQ2Y6TX5SUOLAVCNFSM6AAAAAARLPNXHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBVHEZTQNZZGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[bobbeims]

Still doesn't work for me.

• Home Assistant 2003.10.0
• Abode iota FW 7.0V

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[TBE4034]

Still an issue

[ma7801]

I just realized this was an issue also. I have an automation that notifies my mobile device when the alarm is triggered, but it hasn't been working. Is the issue that the Abode alarm just isn't reporting the "triggered" event to HA any longer? That's frustrating to hear Abode doesn't always play nicely with HA, since they market it as "Smart home friendly" and that's part of why I invested in their equipment!

I think as a workaround for now, I'll be creating a group entity for all my Abode sensors, and have my mobile device notifier automation triggered by abode alarm armed (home or away) AND group sensor entity is changed.

Oh, I should mention that I tried to resolve this by updating HA Core to 2024.1.6, no dice.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.