ring: Refresh Token is not valid
Bug Report
Describe the Bug
I installed the Ring plug in to handle a Ring Doorbell 2 using the homebridge-config-ui-x and it works like a charm, for like an hour or two, sometimes less. After that, I get only errors.To Reproduce
Steps to reproduce the behavior:
- Start Homebridge
- Sign in to Ring and authenticate.
- See error
Expected behavior
To stay signed in.Screenshots/Logs
I[10/13/2021, 5:08:49 PM] [Ring] Request to https://api.ring.com/clients_api/dings/active failed:[10/13/2021, 5:08:49 PM] [Ring] Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens at RingRestClient.getGrantData (/usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:113:15) at RingRestClient.<anonymous> (/usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:117:36) at Generator.next (<anonymous>) at /usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:8:71 at new Promise (<anonymous>) at __awaiter (/usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:4:12) at RingRestClient.getAuth (/usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:116:16) at RingRestClient.<anonymous> (/usr/local/lib/node_modules/homebridge-ring/lib/api/rest-client.js:141:33) at Generator.throw (<anonymous>)
Additional context
Homebridge Ring Config
{
"refreshToken": "XXXXX",
"platform": "Ring"
}
Environment
- OS: MacOS 11.6
- Node.js: v14.18.0
- NPM: v6.14.15
- homebridge-ring: v9.22.1
- homebridge: v1.3.5
- hoobs: N/A
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 27 (9 by maintainers)
I could do whatever but not get it to work. I removed Homebridge from Home, added it again and now it seems to work. 🤞
Those logs just mean you had a network hiccup of some sort. You can ignore them
On the new host it worked for a while, somewhere during the configuration process of the Sonos plugin I believe the Ring plugin started to complain: “Register request has failed with Error=PHONE_REGISTRATION_ERROR”. Refresh access token, but still the same. This error is new for me.
EDIT: But, it seems to work at least, getting new snapshots.
Interesting hypothesis. One of these days when I have some time I’ll try that out and report back.
I believe the MacOS version is the problem. That seems to be what’s common for everyone having this issue. Update to a newer version if you are able, otherwise consider running in Docker or on a different device