Same here. Got it working with the patch after last week’s post-2FA fail, now down again as of a few hours ago. Error logging in to ring api - unauthorized. The connection just failed silently sometime in the last few hours, then the error showed up on restart. Do you think Ring is deliberately trying to break HA?
At this point I’m thinking to link HA to Ring motion trigger via IFTTT webhook and forget about trying to keep fixing this…
Darn, I was hoping that I could use the set_state.py script to set the Ring binary_sensor via an IFTTT trigger, but annoyingly HA makes that sensor unavailable but unremovable, and refuses to allow another sensor of the same name to be created. So I would have to go through all my Node Red flows to change it. Grrr… HA is being really, really annoying this week.
Oh well, the user agent change mentioned below works for the moment.
Also having difficulties locating /components/ring/ init .py
I clicked around just about every possible folder by using WinSCP to SSH into the pi4 with Hassio installed, 103.4. I did not even see any ring addon files except a .pickle file in the config folder.
This appears to be changes made by Ring once again.
It was fixed in 0.103.3 and then a few days later something changed on Rings end again and it is broken again.
After 0.103.3 was released it worked again, until sometime on 24 December for me (probably when the token expired).
Hopefully a permanent fix will be found soon.
To Clarify
The current fix is only temporary
As Paulus has explain
I have been in touch with Ring. The reason they are actively blocking this lib right now is that this library is not following the proper OAuth2 authentication. Whenever the token expires, we should get a new access token using the refresh token that was returned, instead of fetching a new access/refresh token using username/password.
The linked tutorial above describes exactly how this can be added to this lib.
Ring wants to work with us, but we need to follow the spec. Until we do, they will keep blocking us.
If someone rewrites this lib to use the above tutorial for OAuth2, I’ll update Home Assistant to work with it.
it will work for some and others it won’t. It all depends on the ring api site deciding whether it likes you or thinks your another hacker trying to get in then it will just block you till you can fool it again with a different User-Agent string and it thinks okay same address but a different device,
for me it doesn’t like me at the moment with any User-Agent Code i give it.
Updating to 0.103.4 and its still not working.
Error: 401 Client Error: Unauthorized for url: https://api.ring.com/clients_api/session
You will need to restart hass after fixing.
My setup was all working on the 24th Dec with the latest version of HA. Went away for 3 days, came back and Ring integration wasn’t working. They need to fix this ASAP, I need HA more that I need a Ring Doorbell. I can get better functionality without a paid subscription on my own hardware. The Ring device initially looked like a good (tidy) package but when you take the monthly cost and the unreliability into account it is much less appealing. Constant failures and being locked out of a device I paid for means I am unlikely to ever upgrade or recommend.
