they send me an reply on the email, home assistant needs to partner up with ring to get this working again i hope the other PR is going to work.
1 Like
why contact Ring. they don’t want us to not use Ring app.
Yup, same here after a reboot.
As if I needed another reason to look at a different doorbell solution…
4 Likes
I moved to Halo ONE (gen2).
Sadly there isn’t a good alternative to the driveway/floodlight camera.
Hello @firstof9 and everyone. There is a PR already submitted by @xernaj that will address the issue. You can follow it at https://github.com/tchellomello/python-ring-doorbell/pull/143
3 Likes
Have just updated my to 103.2 and ring is not working at all now
Getting the following notification
Error: 403 Client Error: Forbidden for url: https://api.ring.com/clients_api/session
You will need to restart hass after fixing.
Just ran the temporary fix in the open github issues:
All works fine for me now.
Same for me as soon as I updated to 0.103 so are we sure is not the new HA version that is the issue here?
2019-12-20 14:09:45 ERROR (SyncWorker_16) [homeassistant.components.ring] Unable to connect to Ring service: 403 Client Error: Forbidden for url: https://api.ring.com/clients_api/session
We are sure.
3 Likes
It is Ring. They have changed something. It is co-incidence that it broke with the new version of HA - mine broke with no update, just a HA reboot. If you follow the link I posted above, there is a temporary fix.
1 Like
Well i’m not sure about that since it says:
& copying the contents of ring_doorbell to /srv/homeassistant/lib/python3.6/site-packages/ring_doorbell then removing the ring directory in custom_components & restarting HA
As i cannot find /srv/homeassistant/lib/python3.6/site-packages/ring_doorbell and I don’t have anything Ring in my custom components folder either.
I’d just sit tight for the fix to merge 
Mine was in /srv/homeassistant/lib/python3.7/site-packages/ring_doorbell.
I will add I am running HA in a Python VirtEnv and not docker or HassIO.
I moved the existing files to a subfolder called ‘orig’ and then extracted the field to it, rebooted HA and Ring back 
No idea where the path is for Hassio, running it on a pi4. Anyone with a similar setup know the folder path?
If anyone has any update please share it… running Hassio on PI4
If you download this and drop it into custom_components should fix it: https://drive.google.com/file/d/1C41E7OlOUZLtXBHosV9U6HTlBWNN8Cxf/view?usp=sharing
Just did for me and I’m running hassio on a pi4
Hi all–I tried incorporating the fix as both a custom_component and by overwriting ring_doorbell at /usr/local/lib/python3.7/ring_doorbell (I am running hass in docker on a nuc) but I still get the same 401 error. I deleted my .ring_cache.pickle file and updated my password and can log in via the ring app and ring website. The weird thing is the pickle file never gets re-created after restarting the docker container. But when I ‘touch .ring_cache.pickle’ and restart, it gets updated.
Update: I had quotes around my ring password in secrets.yaml and removed them to work.
I do not mind to try that manual update that was suggested in github. The problem is that I cannot get to /srv/. I do not have it when I installed Samba from Hass store.
What can I do?
Updated the manifest.json for the ring component in my homeassistant install from 0.2.3 to 0.2.5 and we’re good.
If anyone is interested, it’s in /srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/ring/ or similar directory on a venv install.
1 Like