Ring camera Motion sensor unavailable post upgrade to 2024.10.1

[c3101]

The problem

Post upgrade to 2024.10, the Ring camera Motion sensor reports to be "unavailable".

Automation using this sensor now fails.

Restored 2024.9 to test, and it works.

What version of Home Assistant Core has the issue?

core-2024.10.1

What was the last working version of Home Assistant Core?

core-2024.9.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ring

Link to integration documentation on our website

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

Diagnostics information

config_entry-ring-52a0293b8c16482691d13e80370ca92c.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of ring 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 ring 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)}}

---

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

[GrimD]

I'm seeing the same issue. Events Ding and Motion both show as Known on Core 2024.10.1.

There is also Sensors Ding and Motion but they never report anything except for "Clear" for me (I think those have been like that since before Core 2024.10.1).

[sdb9696]

2024.10 has switched over to the ring realtime notification api. You may have issues with this due to too many authorised devices. Try the steps in the docs link provided and if you still have issues please upload some debug logs.