I have been made aware of an issue with Ring that started recently (probably yesterday?).

The symptoms are this:

• The plugin is online, but the individual nodes appear as Offline.
• The log shows lines like this:
  • 2025-07-08 00:03:21.890 Thread-124 (pollHandler) udi_interface      ERROR    oauth:_oAuthTokensRefresh: Failed to refresh oAuth token: 401 Client Error: Unauthorized for url: https://oauth.ring.com/oauth/token
• Authorizing works, everything will then be normal for 4 hours, but when the access token is expired, attempts to refresh fails with the error above.

For now I assume there has been a change at Ring that causes this. I have contacted Ring support for help.

If for some reason your plugin works as expected, please let me know. I'm assuming it's down for everyone.

It's down for me, as you described. The plugin Indicates it is Online but all of the individual nodes appear as Offline. 

same issue here.  Worked for a few hours after authentication

Ring Status shows 100% operational.  LOL

I just checked. I have an older doorbell and I can read the battery level in it. Refreshing doesn't cause errors

I'm on v 1.2.3

28 minutes ago, paulbates said:

I just checked. I have an older doorbell and I can read the battery level in it. Refreshing doesn't cause errors

I'm on v 1.2.3

I have many generation doorbells and noticed today none of them are showing battery,  I ignored it since even my gen 1 are hardwired, but I think it should show 100% when you are hardwired now that I think of it.  Not sure if it ever showed 100% or not.

9 minutes ago, macjeff said:

I ignored it since even my gen 1 are hardwired,

This one uses the battery pack. It was on the house when I moved here and I'm sure it's really old, would be surprised if it was *not* gen 1. One of the benefits I get from the plugin is battery low notifications with my other battery devices.

Yes - the plug-in is online, but all nodes are offline until re-authenticated.

 

Having the same problem here. Deleted Ring plug-in and reinstalled as well as doing a reboot of EISY.  Did not help correct this problem.

Edited July 10Jul 10 by TUhl01

Re-authenticating brought my devices back online. 

Re-authenticating worked for me for a short period of time. Have done many times without permanent success. 

I have similar issues where the Nodeserver lists a message that I need to re-authenticate.  Re-authenticating works for about 1/2 a day and then the same message appears.  Started occurring July 7th.  I also notice that in the Ring.com accounts for Authorized Client Devices my ISY does not show up like it used to.

Ring made a change in their API.

I updated the Ring plugin accordingly. Please update the plugin and re-authenticate, that should solve it.

Great, thanks!

Edited July 11Jul 11 by aeroRC

4 minutes ago, aeroRC said:

Great, thanks! Has the plug-in version number been changed?

Try again.  At first it was not installing the new version but now I am at 1.2.5 (not 1.2.4)

Ring advised me of another upcoming change. I had to make another release of the plugin, version 1.2.6. Please update when you have a chance.

For now, 1.2.5 works. However the authentication should start to fail in the next few days if you don't update.

Updated as stated to 1.2.6 4 hours ago and just got an offline message for 1 of my Ring devices. The Ring plug-in has a message to authenticate. Any suggestions. 

13 hours ago, TUhl01 said:

Updated as stated to 1.2.6 4 hours ago and just got an offline message for 1 of my Ring devices. The Ring plug-in has a message to authenticate. Any suggestions. 

Totally puzzled. Did not have time to look into what I experienced last night with the device offline message and authenticate message stated on the Ring plugin that I viewed on UD Mobile.  Viewing this morning on AC, all devices are online, and no messages are shown on the Ring plugin.  All is well at this time. Thanks@bmercier for the quick action taken to resolve the RING problem.