search

dgreif / ring

Unofficial packages for Ring Doorbells, Cameras, Alarm System, and Smart Lighting
MIT License
1.2k stars 161 forks source link

No accessories #1465

Open Shaun-C2 opened 1 month ago

Shaun-C2 commented 1 month ago

Is there an existing issue for this?

Describe The Bug

I have two identical installations. One developed a hardware problem replaced the SD card and loaded the back up file. Ring no longer shows any accessories in Homebridge and the HomeKit accessories no longer work. All other accessories show in home bridge and home kit. Have deleted hub from HomeKit and preexisting accessories . knocked it back to the ground and rebuilt clean install. also generated new token ( more than once) . Nothing seems to work.

To Reproduce

erase SD card. Load Home bridge. Load back up ( previously working).

Expected behavior

the back up to recreate previous .

Relevant log output

[10/08/2024, 08:04:05] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:04:20] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:04:35] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:04:50] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:05:00] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 08:05:00] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 08:05:00] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:05:00] [homebridge-ring] Error connecting to API
[10/08/2024, 08:05:00] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:08:24] [homebridge-ring] Launched child bridge with PID 7287
[10/08/2024, 08:08:25] Loaded 0 cached accessories from cachedAccessories.0E49C066B5E8.
[10/08/2024, 08:08:33] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 08:08:33] Loaded 0 cached accessories from cachedAccessories.0E7B1913CD5B.
[10/08/2024, 08:08:44] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:08:59] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:09:14] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:09:29] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:09:39] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 08:09:39] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 08:09:39] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:09:39] [homebridge-ring] Error connecting to API
[10/08/2024, 08:09:39] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:24:16] [homebridge-ring] Launched child bridge with PID 7830
[10/08/2024, 08:24:25] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 08:24:36] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:24:51] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:25:06] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:25:21] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:25:31] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 08:25:31] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 08:25:31] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:25:31] [homebridge-ring] Error connecting to API
[10/08/2024, 08:25:31] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:29:35] [homebridge-ring] Launched child bridge with PID 8138
[10/08/2024, 08:29:43] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 08:29:54] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:30:09] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:30:39] [homebridge-ring] Launched child bridge with PID 8308
[10/08/2024, 08:30:39] Loaded 2 cached accessories from cachedAccessories.0E3B54C8AD41.
[10/08/2024, 08:30:39] Loaded 13 cached accessories from cachedAccessories.0EAC5DC796E1.
[10/08/2024, 08:30:49] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 08:30:49] Loaded 0 cached accessories from cachedAccessories.0E7B1913CD5B.
[10/08/2024, 08:31:00] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:31:15] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:31:30] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:31:45] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 08:31:56] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 08:31:56] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 08:31:56] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 08:31:56] [homebridge-ring] Error connecting to API
[10/08/2024, 08:31:56] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[Te Anau front 244F] The image snapshot handler for the given accessory is slow to respond! See https://homebridge.io/w/JtMGR for more info.
[10/08/2024, 10:01:07] [homebridge-ring] Launched child bridge with PID 10558
[10/08/2024, 10:01:16] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 10:01:16] Loaded 0 cached accessories from cachedAccessories.0E7B1913CD5B.
[10/08/2024, 10:01:27] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:01:42] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:01:57] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:02:12] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:02:22] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 10:02:22] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 10:02:22] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 10:02:22] [homebridge-ring] Error connecting to API
[10/08/2024, 10:02:22] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 10:04:51] [homebridge-ring] Launched child bridge with PID 10994
[10/08/2024, 10:05:00] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[10/08/2024, 10:05:11] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:05:26] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:05:41] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:05:56] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[10/08/2024, 10:06:07] [homebridge-ring] Error: 
    at responseToError (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:38:19)
    at requestWithRetry (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:82:33)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:201:73) {
  response: {
    headers: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    },
    status: 401,
    body: {
      error: 'invalid_grant',
      error_description: 'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
    }
  }
}
[10/08/2024, 10:06:07] [homebridge-ring] Request to https://api.ring.com/devices/v1/locations failed:
[10/08/2024, 10:06:07] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[10/08/2024, 10:06:07] [homebridge-ring] Error connecting to API
[10/08/2024, 10:06:07] [homebridge-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 (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:196:15)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:199:32)
    at RingRestClient.getAuth (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/rest-client.js:240:29)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
[11/08/2024, 06:48:08] [homebridge-ring] Launched child bridge with PID 35585
[11/08/2024, 06:48:17] [homebridge-ring] Loaded homebridge-ring v13.0.1 child bridge successfully
[11/08/2024, 06:48:18] Loaded 0 cached accessories from cachedAccessories.0E7B1913CD5B.
[11/08/2024, 06:48:28] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[11/08/2024, 06:48:43] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...
[11/08/2024, 06:48:58] [homebridge-ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token.  fetch failed.  Trying again in 5 seconds...

Screenshots

Screenshot 2024-08-11 at 7 00 44 AM

Homebridge Ring Config

{
    "beamDurationSeconds": 3220,
    "_bridge": {
        "username": "0E:7B:19:13:CD:5B",
        "port": 41370
    },
    "unbridgeCameras": true,
    "alarmOnEntryDelay": false,
    "avoidSnapshotBatteryDrain": true,
    "refreshToken": "eyJydCI6ImV5SmhiR2NpT2lKU1V6STFOaUlzSW1wcmRTSTZJaTl2WVhWMGFDOXBiblJsY201aGJDOXFkMnR6SWl3aWEybGtJam9pTkdSak9EUXlaR0lpTENKMGVYQWlPaUpLVjFRaWZRLmV5SnBZWFFpT2pFM01URTNNek0zTlRNc0ltbHpjeUk2SWxKcGJtZFBZWFYwYUZObGNuWnBZMlV0Y0hKdlpEcDFjeTFsWVhOMExURTZZakF6T1dWa01HWWlMQ0p5WldaeVpYTm9YMk5wWkNJNkluSnBibWRmYjJabWFXTnBZV3hmWVc1a2NtOXBaQ0lzSW5KbFpuSmxjMmhmYzJOdmNHVnpJanBiSW1Oc2FXVnVkQ0pkTENKeVpXWnlaWE5vWDNWelpYSmZhV1FpT2pFeE5UTTFOalUxTlN3aWNtNWtJam9pWm10elMyTnBZVGxzWXlJc0luTmxjM05wYjI1ZmFXUWlPaUptTkRoaU1UTTBOaTB5TldFM0xUUmhOakF0T1RBeFlTMHlNRGxpTnpFMk1USTFZVGNpTENKMGVYQmxJam9pY21WbWNtVnphQzEwYjJ0bGJpSjkuSWZDV1M5enVvMjZocXZvMXJMdTdpYTh3ZnRwdFlVNmhSUjBLT2JvMEQzTjJhdWZScDJ0QzdHcTFpU2d6NXNuakFwLVJMaW9vUDVMRXllaDhLQ1JhYi1ZRzJJbkxsbEdOdnJpcFdWdmp4MlJabTJhTmpnLXpaSDhKZU5GejNiVlFRLXFiY0RrUk9CSXk3VEs5bXZpWVRYZG9QYjZ4MlJSUUU0UFgwQ3ZUN0JxV25fVjFrTGs3RzBOLUZVUUtEU3BDcUhPWTBiaGh0bkpiMmdEemR1VHdab2Q0UjBxNGx1TGNJRE1JM2MxQW9JUFpESDNDWm1DenN5MGRJTzNRd0dNam95UHZEVFBpdDFrS3dxdUV2dXJlUE1VbXBEQUN5R2owX2Etd21xZTNfaWdZOTRLUnlOWF9vTHhUUlZibTgwTXVLNlFXT2VrNVRNZTRIY3pUbzRGTDd3IiwiaGlkIjoiYWNkMjQyY2EtNTQ2Yy01ZTZhLWE5MzctN2JhNjFmMzQyODYzIiwicG5jIjp7ImdjbSI6eyJ0b2tlbiI6ImV4Um5fSldUVFNnOkFQQTkxYkZ2RTU2cUFYekQ1UURPVEw2RVNBdXBHSEVzMWJhWUlRR1ZuRkNnOWVJOEd0UGJ6S0RCQlBpNFAxS3Awa19aUkJ5UWo3R2tkVnEzc19rLUV0ejZFdDBDYmJXZXdIOUpqSGJfc1A5VmlCZEhTZnB3NDh4clpoS0NEbWVqZ29tOC13cFhwU2NKIiwiYW5kcm9pZElkIjoiNTcxMzI2MDM2NzE4NDAwNzYwOCIsInNlY3VyaXR5VG9rZW4iOiI4NDU1NTc5Njk0ODY2ODY5MDA1IiwiYXBwSWQiOiJ3cDpyZWNlaXZlci5wdXNoLmNvbSM2OWRkOTliZC1mNTVhLTQ4Y2QtOWM3ZC1iODE1NTQ4NzUwNGEifSwia2V5cyI6eyJwcml2YXRlS2V5IjoiTFZkNmpSeW1nU19qZ0tlRXB3QUt2ZWlaYWY3d3hYbEFVc3JzekpqZkxRdyIsInB1YmxpY0tleSI6IkJBLUxIdE9STXVlRElZV0xKUVFZWmlFSTRxREp6bjdrbS1WSk51LUQ0RVdYNXNEUDZ6QUJwS2RTdmxrRGlZVjNKVncwMUIwTHVuX2d4M2E5V1ltWVlGWSIsImF1dGhTZWNyZXQiOiJJMUxPckxzaDcxNDFJcWJZbFlyOEJBIn0sImZjbSI6eyJ0b2tlbiI6ImY4V1lueXFUYV9BOkFQQTkxYkhVY2l0OG1zV0o5QWR5bG1vNFZEX1U3U1Y3MDFxaGd3QS1pWHc5TS04M3ZVYVJGRlNBQTJyTEgyWk1sd1BkRHRVdVFIREJncTQ1WXZPa2p0TVloLUtCNEE0LWxVLWhNTnRNS1FNQzFyclg4Y0w2TEtJYS1MSy16WDk3OGVQS3ZIb2pTMXI1IiwicHVzaFNldCI6ImNUWkw1LWtkamxnOkFQQTkxYkVnTkdMZUFWdVdaS0huQ2U2ZWhtb1hHUGhNLTVDLTZVRnl2X3BQWHQ1TUlwZWYyMm10aV9nQVV5T0JpOXRpVG9RbUxzclFYQkstd1phVDRBUGJJNjBzaUVZYnk2ZVQ0aXdWaTFkTk1MRThQbk5mTy1Oc2VuQVlaTDUycTlSMS1XN0lCRDg0In19fQ==",
    "hideDoorbellSwitch": false,
    "platform": "Ring",
    "cameraStatusPollingSeconds": 20
}

Additional context

No response

OS

Raspian

Node.js Version

v20.16.0

NPM Version

not sure.

Homebridge/HOOBs Version

1.8.4

Homebridge Ring Plugin Version

13.0.1

Operating System

Debian GNU/Linux Bookworm (12)

tsightler commented 1 month ago

it's not a good idea to paste your refresh token in a public forum, that is your access to your account. In this case it probably doesn't matter since the token is likely the actual problem, but just information for the future. It's the equivalent of posting your password.

You should definitely try wiping out the token and then re-authenticating, the refresh token you posted doesn't even appear to be in the correct format for current tokens, but the message is really clear, Ring is saying your token is not authorized. Good luck!

tsightler commented 1 month ago

@peppers-newish No, that is not a similar issue, and your error message is completely different. You need to update your NodeJS version to at least v18, ideally v20. This is stated in the release notes for v13. I will mark you comment as off-topic since it is unrelated to this issue.

Also, HOOBS is not supported with the v13 plugin versions since they have not provided an update for the end-of-life NodeJS version. You should reach out to HOOBS support for assistance with HOOBS as we cannot help with that.

peppers-newish commented 1 month ago

@peppers-newish No, that is not a similar issue, and your error message is completely different. You need to update your NodeJS version to at least v18, ideally v20. This is stated in the release notes for v13. I will mark you comment as off-topic since it is unrelated to this issue.

Also, HOOBS is not supported with the v13 plugin versions since they have not provided an update for the end-of-life NodeJS version. You should reach out to HOOBS support for assistance with HOOBS as we cannot help with that.

My apologies. You are right that the error is not exactly the same. I have removed my comments. I will create a separate report. Though both have OAuth issue, the actual error has one word difference. Homebridge on Synology does have NodeJS v20 installed though so I don't know what is up there. Anyway, sorry. I will report a separate thread.

tsightler commented 1 month ago

@peppers-newish As I stated above, HOOBS is not supported by the v13 plugin and, unless you have unofficially updated NodeJS to v18 or v20, there is no way that the error message can be the same and there is zero chance that it will work with older NodeJS versions. If you have not upgraded your NodeJS on HOOBS to a supported NodeJS version, then there is no more reason to speak about it in this thread and it only adds confusion.

If you have logs from an environment with a supported NodeJS version (ideally v20, sounds like your Synology environment meets this requirement), please feel free to post them here, they are not "mumbo jumbo", they are detailed information about what is happening and are required to provide any insight into the issues you are having.

tsightler commented 1 month ago

@Shaun-C2 Can you please verify your install method? You list the Operating System as Debian, is that just x86 or ARM architecture? Are you using a based Debian install and the instructions from: https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Debian-or-Ubuntu-Linux?

So far I'm not able to reproduce your issue so seeking more detail. One suggestion would be to make sure your plugin is disabled for at least 24 hours and then try again as I've sometimes seen Ring block IP addresses if they attempting to authenticate with invalid tokens too many times.

Shaun-C2 commented 1 month ago

Thanks for looking at this. I shall reply Sunday when back home. However as I indicated i have two install on two different houses. At one house the plug in works fine and … i can also see accessories for the other house.I wonder if i need the same token at both sites ?Will try your suggestion. My install was using the raspberry pie installer from the pi website using the 64 bit homebridge variant.On 14 Aug 2024, at 5:48 AM, tsightler @.***> wrote: @Shaun-C2 Can you please verify your install method? You list the Operating System as Debian, is that just x86 or ARM architecture? Are you using a based Debian install and the instructions from: https://github.com/homebridge/homebridge/wiki/Install-Homebridge-on-Debian-or-Ubuntu-Linux? So far I'm not able to reproduce your issue so seeking more detail. One suggestion would be to make sure your plugin is disabled for at least 24 hours and then try again as I've sometimes seen Ring block IP addresses if they attempting to authenticate with invalid tokens too many times.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

tsightler commented 4 weeks ago

You definitely should not use the same token at both locations. You can use the same account, but each instance of ring-homebridge is effectively a separate device, the same as a device running the Ring app. If you had two phones, you might login to each using the same username/password, but they would not use the same token. Actually, the error above almost looks like it's attempting to use a token that was issued to a different device based on this error message:

'The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.'
tsightler commented 2 weeks ago

@Shaun-C2 Any update?

Shaun-C2 commented 2 weeks ago

I shut down the plug in for a week whilst i was overseas. Then renewed the token and re-enabled it. Same issue.My next plan is to unenrol the bell. Then re enrol with a separate log in and see if that works .It seems to identify the two sites but then i still get the cannot connect to server issue at one site.I shall be back at that house in a couple of weeks and will try then.On 29 Aug 2024, at 5:06 AM, tsightler @.***> wrote: @Shaun-C2 Any update?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

tsightler commented 2 weeks ago

It's a very strange problem for sure, but I don't think that it is a plugin bug. The code simply calls native fetch API built into NodeJS v20, and if the native fetch implementation cannot communicate with the Ring servers I'm not sure what we could possibly ever do about that.

I would maybe suggest, instead of installing from backup, just removing the plugin completely and re-installing.

Shaun-C2 commented 1 week ago

So I have deleted all the approved devices from the ring app.

I have a Pi zero which I have a clean reload with the ring plug in loaded

I have linked the ring account successfully …

The Rasp Pi appears as an authorised device on the ring app

Still no joy

[05/09/2024, 17:07:11] [Homebridge UI] [homebridge-config-ui-x] Failed to check registry.npmjs.org for updates: "timeout of 10000ms exceeded" - see https://homebridge.io/w/JJSz6 for help. [05/09/2024, 17:07:11] [Homebridge UI] [homebridge-config-ui-x] Failed to check registry.npmjs.org for updates: "timeout of 10000ms exceeded" - see https://homebridge.io/w/JJSz6 for help. [05/09/2024, 17:07:15] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:07:30] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:07:45] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:00] [Ring] Failed to reach Ring server at https://oauth.ring.com/oauth/token. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:23] [Ring] Found the following locations: [05/09/2024, 17:08:23] [Ring] locationId: e27e978e-2d8f-4216-ae78-550d251d0b19 - Te Anau [05/09/2024, 17:08:23] [Ring] locationId: af7bd812-b3f7-4ba5-b43a-2a50ea34bc69 - Scroggs Hill [05/09/2024, 17:08:29] [Ring] 404 from endpoint https://api.ring.com/clients_api/doorbots/412121515/motions_subscribe [05/09/2024, 17:08:29] [Ring] Session hardware_id not found. Creating a new session and trying again. [05/09/2024, 17:08:29] [Ring] 404 from endpoint https://api.ring.com/clients_api/doorbots/412121515/subscribe [05/09/2024, 17:08:29] [Ring] Session hardware_id not found. Creating a new session and trying again. [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/motions_subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:33] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:39] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/session. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/motions_subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:48] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:08:54] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/session. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/motions_subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:03] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:09] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/session. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://api.ring.com/clients_api/doorbots/420296495/motions_subscribe. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/e27e978e-2d8f-4216-ae78-550d251d0b19. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to reach Ring server at https://prd-api-us.prd.rings.solutions/api/v1/mode/location/af7bd812-b3f7-4ba5-b43a-2a50ea34bc69. fetch failed. Trying again in 5 seconds... [05/09/2024, 17:09:18] [Ring] Failed to connect push notification receiver [05/09/2024, 17:09:18] [Ring] TypeError: fetch failed at node:internal/deps/undici/undici:13178:13 at processTicksAndRejections (node:internal/process/task_queues:95:5) at retry @./push-receiver/src/utils/request.ts:17:16) at checkIn @./push-receiver/src/gcm.ts:24:25) at exports.default @./push-receiver/src/gcm.ts:18:21) at PushReceiver.registerIfNeeded @./push-receiver/src/client.ts:165:21) at PushReceiver.connect @.***/push-receiver/src/client.ts:93:9) at RingApi.registerPushReceiver (/var/lib/homebridge/node_modules/homebridge-ring/node_modules/ring-client-api/lib/api.js:177:13) { [cause]: ConnectTimeoutError: Connect Timeout Error at onConnectTimeout (node:internal/deps/undici/undici:2331:28) at node:internal/deps/undici/undici:2283:50 at Immediate._onImmediate (node:internal/deps/undici/undici:2315:13) at processImmediate (node:internal/timers:483:21) { code: 'UND_ERR_CONNECT_TIMEOUT' } }

Shaun Costello @.***

On 31 Aug 2024, at 11:30 AM, tsightler @.***> wrote:

It's a very strange problem for sure, but I don't think that it is a plugin bug. The code simply calls native fetch API built into NodeJS v20, and if the native fetch implementation cannot communicate with the Ring servers I'm not sure what we could possibly ever do about that.

I would maybe suggest, instead of installing from backup, just removing the plugin completely and re-installing.

— Reply to this email directly, view it on GitHub https://github.com/dgreif/ring/issues/1465#issuecomment-2322597881, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFFBIFRH2GXRDRFLAH43AITZUD6CDAVCNFSM6AAAAABMKB4XTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRSGU4TOOBYGE. You are receiving this because you were mentioned.

tsightler commented 5 days ago

@Shaun-C2 If you look at the logs you can see that not all of the failed to connect messages are from homebridge-ring, for example:

[05/09/2024, 17:07:11] [Homebridge UI] [homebridge-config-ui-x] Failed to check registry.npmjs.org for updates: "timeout of 10000ms exceeded" - see https://homebridge.io/w/JJSz6 for help.

This is from the homebridge-ui, although it is basically the same error. There is clearly some issue with that system being able to connect reliably to internet resources that is impacting not just hombridge-ring, but other services running on that host. There is little that any of us can do here as the plugin cannot work if it is unable to reach the internet.