Beginning 2025.03.12 about 06:26 PST began getting 401 Unauthorized from api.ring.com/clients_api/dings/EventID fetchs

[4Dolio]

Beginning 2025.03.12 about 06:26 PST began getting 401 Unauthorized from api.ring.com/clients_api/dings/EventID fetch requests.

I appear to still be able to query for event IDs for all devices for my account, but fetching the mp4 clips is failing with 401s.

Auth seems fine, for the event requests at least. I threw out my old token and complete the 2FA challange for a new one just fine, but it's still not working.

I try to rate limit my clip fetching and do not let my script do any simultaneous requests which in the past would get my IP Banned. Perhaps this is the problem, as I may be on a shared IP. I'll try switching to a different ISP perhaps tomorrow, or maybe if banned now it will get lifted after a few hours?

I will check back in, but was curious if anyone else has noticed a similar problem.

[4Dolio]

Been a few days now, 2025.03.17 and still getting the 401 unauthorized, so looks like perhaps Ring changed something. Not sure if anyone else is still trying to use this project for fetching ring video clips... Am still able to fetch the list of devices and clips for each camera, but the downloads just do not work any more... Sigh....

[4Dolio]

Finally has some time to poke at this, turns out that the clips are pulled from api.ring.com and that has begun to require the Bearer token... I've been using wget in a loop to re attempt that fetch every few seconds because a year or two ago the clip was not immediately available, so the added latency meant that it often failed. Anyway, I needed to add a new wget option '--header="Authorization: Bearer $YourOAuthToken" in order to get this first call to the api.ring.com to start to succeed again as of the 17th.

But now that that is working, it returns a 302 permanently moved with a url for filestore-numbers-etc.amazonaws.com/super-long-url-with-tokens-and-stuff now. But wget does not succeed when attempting to follow that 302, so instead I just do another wget to fetch that .mp4 clip. This second one does not require the new auth token as it's all embedded in the 302 url it appears.

Now to catch back up on the two weeks of clips I'm missing...

[github-actions[bot]]

There hasn't been any activity on this issue recently. This issue has been automatically marked as stale because of that. It will be closed if no further activity occurs. Please make sure to update to the latest ring_doorbell version and check if that solves the issue. Thank you for your contributions.