-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Abode Integration doesn't update, throws exception #86765
Comments
Hey there @shred86, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) abode documentation |
cc: @tradel |
I just want to add that I am also experiencing the same issue with the Abode integration since upgrading to 2023.2.0. I can successfully arm or disarm the alarm using Home Assistant, but the status displayed in Home Assistant does not change. Log entry:
|
I'm experiencing the same issue. I'm not sure if it's an issue with HA or with the Abode package by @jaraco . The line throwing comes from here: https://github.com/jaraco/jaraco.abode/blob/main/jaraco/abode/devices/alarm.py#L26 . It looks like the |
@jaraco are you able to take a look at this?
…On Thu, Feb 2, 2023 at 11:12 AM Brian Johnson ***@***.***> wrote:
I'm experiencing the same issue. I'm not sure if it's an issue with HA or
with the Abode package by @jaraco <https://github.com/jaraco> . The line
throwing comes from here:
https://github.com/jaraco/jaraco.abode/blob/main/jaraco/abode/devices/alarm.py#L26
. It looks like the panel_state is derived within that package.
—
Reply to this email directly, view it on GitHub
<#86765 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHPYDNRHMR5L6TSJAXATWVPMILANCNFSM6AAAAAAUIIONDA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
FWIW when I run Somewhat relatedly I had to re-auth the abode integration when I updated to 2023.2, I assume it's because of the new package. |
Yes, the jaraco.abode library changed how it stores authentication tokens.
I should have added a warning.
It sounds like the jaraco EventController either isn’t receiving updates
from Abode or isn’t propagating them correctly to HA to update its status.
…On Thu, Feb 2, 2023 at 1:02 PM Evan Moses ***@***.***> wrote:
FWIW when I run abode directly on the cli from the jaraco/jaraco.abode
package, it works fine to get the state and I see the 'mac' key if I ask
it to output json. So must be an interaction between HA and the python
package.
Somewhat relatedly I had to re-auth the abode integration when I updated
to 2023.2, I assume it's because of the new package.
—
Reply to this email directly, view it on GitHub
<#86765 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANRHP3QIBAL7OCWKKYVNYDWVPZDTANCNFSM6AAAAAAUIIONDA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I spoke too soon. If I run |
I'm gonna post this as an issue to that repo. |
I just wanted to chime in that I am seeing the same issue. |
I am having the same issue after upgrade to core 2.0, and it has persisted with core 2.1 Logger: jaraco.abode.socketio Captured exception during SocketIO event callback: 'NoneType' object has no attribute 'replace' |
Can also confirm this issue with 2023.2.0. Fixed it by downgrading to 2023.1. |
I submitted a PR that should fix this in the library, jaraco/jaraco.abode#22. Once that's merged it'll have to be pulled into HA. |
@evanmoses-okta I have tested with 2023.2.2 and still have the same issue. Current Version: 2023.2.2 2023-02-05 11:07:53.551 ERROR (SocketIOThread) [jaraco.abode.socketio] Captured exception during SocketIO event callback: 'NoneType' object has no attribute 'replace' |
It looks like you still have an older version of https://github.com/jaraco/jaraco.abode/blob/v3.2.2/jaraco/abode/devices/alarm.py#L26 |
Looks like the project still depends on 3.2.1: Line 1003 in a2530e7
|
Fixes home-assistant#86765 fixes undefined
I am very new to Home Assistant but being able to integrate my Abode system with it was a big reason for getting started with it. I know very little about coding so I don't really understand much but thank you for any and all who are keeping Abode integrating functioning. The alarm state not updating was very confusing for me as I had thought I had set everything up correctly and had a scene switcher so my wife could easily secure the house at night but it wasn't quite working unless I reloaded the integration. So far so good, and thank you. I hope to be able to contribute one day to such an amazing feat of human cooperation happening with HA |
2022.2.3 didn't seem to change anything for me, same errors. Can we re-open this? Rolling back to 2023.1.x still sufficient in meantime. |
It fixed it for me... |
2022.2.3 fixed this for me. @nathang21 are you still seeing exceptions in the logs with 2022.2.3? |
Weird, after upgrading again, it does indeed seem to be working. Perhaps I just needed another HA restart. Thanks folks. |
The problem
The abode alarm system status no longer updates. Actions such as arming and disarming function and the actual alarm state changes, but the alarm_control_panel.abode entity does not update with the new status.
Reloading the integration via settings corrects the status, but it breaks again.
There are connection exceptions in the logs, it's the same one every time:
What version of Home Assistant Core has the issue?
2023.2.0b1
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://rc.home-assistant.io/integrations/abode/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
This might be related to #80754
The text was updated successfully, but these errors were encountered: