Same as everyone else on 0.103.4 - dead Ring
Seems to have taken out ring and august devices this time.
Yes a restart broke my Ring platform too (was working with 103.4)
I just posted in another thread, a workaround that I applied to my local HA: https://github.com/tchellomello/python-ring-doorbell/issues/146#issuecomment-568645501
2 Likes
Ring will keep blocking us until the library uses OAuth2 authentication.
1 Like
Iâm having difficulties locating /components/ring/init.py in hassio, any help would be appreciated.
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.
The workaround posted by tekmaven worked for me!
location of the file I changed is: /srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/ring/
/Per
For me Ring is down but August lock working
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.
2 Likes
Yes. I saw that too. Current âtemporaryâ fix is no longer working, so we wait until someone who knows how to rewrite the library has time to do it 
1 Like
Question? Did it work again after restarting the Hassio?
The temp fix worked and is still working after a few reboots.
I can confirm ring stopped working ⌠again. Guess Harry13 is right⌠Ring Android app is still working without 2FA.
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.
1 Like
The temp fix works and is still working, Iâve rebooted multiple times after applying the temp fix.
You are running 0.103.4?