Abode Cam 2 at idle

[thomasjomelnine7]

The problem

I cannot view or get streams from my abode cam2 working in HA all other entities including door sensors, occupancy, and key fobs and keypads for abode security are working fine w/ arming and disarming the system working properly. The cameras are stated as idle.

What version of Home Assistant Core has the issue?

core-2023.6.3

What was the last working version of Home Assistant Core?

core-2023.6.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Abode

Link to integration documentation on our website

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

Diagnostics information

n/a

Example YAML snippet

n/a

Anything in the logs that might be useful for us?

n/a

Additional information

n/a

[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.

_{^{(message by CodeOwnersMention)}}

---

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

[tmahlstrom]

Bump, same issue here

[jaimeburnap]

Having the same issue also

Core 2023.12.3 Supervisor 2023.12.0 Operating System 11.2 Frontend 20231208.2

[cheezmo]

I am having the same issue.

[sam011989]

Same issues. All cameras are "idle" not not transmitting any data.

[NeckBeardPrince]

Not that it seems to matter, but same issue here. Just started using HA, big disappointment.

[jaraco]

Support for Abode Cam 2 was added to the backing library in jaraco.abode 0.6.0.

I have gone through the jaraco.abode code and confirmed that it does indeed properly talk to camera devices and shows them as online and I'm able to pull images from them.

 jaraco.abode main @ pipx run --spec 'jaraco.abode>=5.2' abode --devices --interact
2024-05-13 16:40:28 INFO (MainThread) [jaraco.abode.client] Updating all devices...
2024-05-13 16:40:29 INFO (MainThread) [jaraco.abode.client] Login successful
...
2024-05-13 16:40:29 INFO (MainThread) [jaraco.abode.cli] Front Porch (ID: XF:b0c5ca318038, UUID: d19d0cf03b881208a8f6c6594fead48c) - Abode Cam 2 - Online
...
Interact with the Abode `client`.
>>> cam = client.get_device('XF:b0c5ca318038')
>>> cam.is_on
True
>>> cam._state['privacy']
'0'
>>> cam.privacy_mode(True)
2024-05-13 16:41:56 INFO (MainThread) [jaraco.abode.devices.camera] Set camera XF:b0c5ca318038 privacy mode to: 1
True
>>> cam.privacy_mode(False)
2024-05-13 16:42:00 INFO (MainThread) [jaraco.abode.devices.camera] Set camera XF:b0c5ca318038 privacy mode to: 0
True
>>> cam.snapshot()
True
>>> cam.snapshot_data_url(False)[:30]
'data:image/jpeg;base64,/9j/4AA'

I'm unfamiliar with how HA interfaces with component modules. I'll inspect that next.

[jaraco]

I read through the camera module and I don't see anything out of order there.

Does anyone experiencing this issue have access to troubleshooting logs? See the troubleshooting guide for advice on how get the logs and how to enable debugging.

It's also possible that an issue was resolved between the 3.3.0 release of jaraco.abode (what's currently in HA) and the 5.1.2 release, so it may be worth waiting for the next release of HA following the merge of https://github.com/home-assistant/core/pull/117363 to see if that happens to solve any issues (though I give that a slim chance).

[bobbeims]

Has there been any work on this issue lately?

[jaraco]

No work. The latest HA has been updated to a recent jaraco.abode. Now would be a good opportunity to gather diagnostics from someone affected.

[issue-triage-workflows[bot]]

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.

[NeckBeardPrince]

Not stale

[ahober]

Still no progress on this matter? I only have an ”Idle” status on my cameras and no video stream.

[tmahlstrom]

Still an issue for me too.

On Sun, Nov 10, 2024 at 2:09 PM Andreas Hober @.***> wrote:

Still no progress on this matter? I only have an ”Idle” status on my cameras and no video stream.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/98367#issuecomment-2466892685, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUFNT5Z26NW54F6GC2KFI3Z764P5AVCNFSM6AAAAAA3PDCYQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWHA4TENRYGU . You are receiving this because you commented.Message ID: @.***>

[USER19464727]

Ditto

[arphoenix-ms]

This remains an issue for me

[issue-triage-workflows[bot]]

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.

[ahober]

The issue still remains.

[tmahlstrom]

Still an issue for me as well.

On Sun, Mar 23, 2025 at 2:37 AM Andreas Hober @.***> wrote:

The issue still remains.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/98367#issuecomment-2746070409, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUFNT4REXIYJHL4P3TSCXL2VZQC5AVCNFSM6AAAAAA3PDCYQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBWGA3TANBQHE . You are receiving this because you commented.Message ID: @.***> [image: ahober]ahober left a comment (home-assistant/core#98367) https://github.com/home-assistant/core/issues/98367#issuecomment-2746070409

The issue still remains.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/98367#issuecomment-2746070409, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUFNT4REXIYJHL4P3TSCXL2VZQC5AVCNFSM6AAAAAA3PDCYQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBWGA3TANBQHE . You are receiving this because you commented.Message ID: @.***>

[jaraco]

Please don't reply with "me too" comments ("still broken" comments are okay following the bot's prompt). Instead, add a thumbs-up to the original post above, or better-yet, follow the directions in the comment above to provide the necessary diagnostics to unblock the effort to fix the issue.

[issue-triage-workflows[bot]]

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.

[tach47]

Not stale/still an issue.