Ring: Error: 401 Client Error: Unauthorized for url

Configuration
21

Same. I bet they locked down their API after the recent bad PR with account hacking.

22

Well, i used to get the same error. i went to ring.com and changed my password.
Seems that the problem went away.

23

I tried changing the password on the site and updated the config, still doesnt work for me. Anyone has any luck?

24

Same boat here. Seems like it coincided with the 0.103 release.

25

Wow they really are having a bad time. Website wouldnt let me reset the password, I had to contact support to get a reset link.

Changed the password and same issue :confused:

26

Had the same issue as described above - literally just started working for me…only thing I did was uncomment some Google token code and restarted Home Assistant…(probably unrelated)…

27

I also tried changing the password. No luck.

28

And another restart (more config changes not related to Ring) and it’s not working again.

29

Same issue here - started after a HA restart today for an unrelated config change. Tried everything - I deleted the .ring_cache.pickle file and changed ring password and it kind of worked for a few minutes, but then went bad again and I can’t get it going at all now.

30

Turns out, the solution in my case is to activate te subscription. My boss activated it and I reconfigured and it was ok. Much of a delay dough, about 5 seconds :unamused:

31

I have always had a plan (Basic Plan) and it always worked before today.

1 Like
32

Do you also get so much delay in the image?

33

UK user here, also getting the same issue

34

This started for me yesterday. It actually filled my log with garbage, hundreds of entries about this api error, before I restated.

35

I have the same issue. Started yesterday after I rebooted my HA.

36

Same issue here. But only after I updated to 0.103.2
I’ve also reset my ring password but that didn’t help.

37

Maybe a change made to the api by Ring. Hopefully the HA folks will be able to make an adjustment to an upcoming release to make it work again. I wish I was smart enough to do it.

Changing password did not help.

1 Like
38

+1 on the issue when moving to 0.103.2

39

+1 Im running 103.0 and this appeared after a reboot no update. I wonder if this has anything to do with Rings recent bad press?

1 Like
40

Keep an eye on https://github.com/tchellomello/python-ring-doorbell/issues/142 for updates

2 Likes