Abode integration isn't tracking motion detector state changes (stuck to "detected")

[bobbeims]

The problem

Starting within the last 48 hours, the HA device created by the Abode integration for a motion sensor has been constantly reporting "detected". Initially, I only saw this behavior with their stand-alone motion detector. This afternoon, the motion sensor in the keypad has also started doing this.

As a diagnostic, I created CUE automations in the Abode platform that trigger with the motion sensors start detecting motion and when motion detection clears. I then turned on debug logging, reloaded the integration, walked by both of the sensors and watched the Abode platform automations trigger. After the "cleared" automations had run, I turned off the debug logging.

Here's the timeline shown in the Abode timeline:

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

core-2024.7.1

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

home-assistant_abode_2024-07-07T22-23-46.223Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign abode` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[smux84]

Good evening everyone, I have the usual problem with a volumetric presence sensor

[bobbeims]

@smux84 do you mean the multi-sensor https://goabode.com/product/multi-sensor-tp/

Abode doesn’t make a presence sensor, to the best of my knowledge.

[smux84]

I mean this

https://goabode.com/product/motion-sensor-tp/

[Jim-Cripe]

I'm having the same issue with Abode motion detectors stuck at "detected".

I did a hard reset on the Abode hub and rebooted HA, to no effect.

[bobbeims]

@Jim-Cripe and @smux84 if you're using Abode motion sensors in HA automations, this stuck behavior obviously prevents the triggering of those automations. I had developed a bit of a kludge workaround some time back for the iota base station motion sensor (it has never worked for me via the integration). I replicated that workaround for the two motion sensors that recently stopped working for me.

If you're interested, I'll write up a description of that workaround.

[smux84]

@Jim-Cripe and @smux84 if you're using Abode motion sensors in HA automations, this stuck behavior obviously prevents the triggering of those automations. I had developed a bit of a kludge workaround some time back for the iota base station motion sensor (it has never worked for me via the integration). I replicated that workaround for the two motion sensors that recently stopped working for me.

If you're interested, I'll write up a description of that workaround.

I sincerely hope they can solve it with an update of the integration but if you want to show us the alternative solution I will be grateful.

[bobbeims]

The workaround has three components:

1. Two CUE automations in the Abode platform for each sensor that send motion detected/cleared state change messages to Home Assistant via the mobile service connection that is created when the Abode integration is configured in HA
2. Two helpers for each sensor: one input boolean toggle (which is turned on/off by an automation) and one template binary sensor that evaluates the state of the input boolean (the template sensor is the entity that becomes the "replacement" for the always-stuck-on entity provided by the Abode integration)
3. One automation that is triggered by messages from the CUE automations, which toggles the input boolean helper

I've included screen snaps of each of these pieces.

Abode CUE definitions for iota status messages

Abode CUE detail

Home Assistant helpers

HA template binary sensor configuration

HA template binary sensor detail

HA automation triggered by Abode CUE messages

Dashboard showing behavior of template binary sensor in action

[smux84]

Thank you, you were very kind to share the alternative solution to the problem. Thank you very much, I will try. Thank you

[smux84]

Update...

With the update to HA 2024.7.2 my sensor has returned to working normally, check.

[bobbeims]

So it looks like jaraco.abode v 5.2.1 resolved the issue for the keypad and motion detector devices. But the iota base station motion is still stuck at “detected”.

[smux84]

So it looks like jaraco.abode v 5.2.1 resolved the issue for the keypad and motion detector devices. But the iota base station motion is still stuck at “detected”.

I have the “Smart Security kit” and I confirm the restoration to the correct operation

[voxmatt]

HA 2024.7.2 fixed it for me too

[riskmaker76]

So it looks like jaraco.abode v 5.2.1 resolved the issue for the keypad and motion detector devices. But the iota base station motion is still stuck at “detected”.

I am having this issue ONLY WITH the iota base station. Any update to the resolution?