Node-red-contrib-ringdoorbell - alternatives?

Starting from around December 18, the ringdoorbell node has started throwing API errors. This node appears to have been abandoned by the developer, no responses to GitHub issues.

Maybe this relates to the scare about Ring account hacking recently? Does anyone know what the below trace means, how to fix? Or is there an alternative node to replace this abandoned node?

Thanks in advance. PS: since a new forum user, had to replace https in below with h:.
-Alan

Dec 22 12:32:25 neptune node-red[28755]: { Error: ring gave a seemingly valid authentication/authorisation, but the failed --caused-by-> problem GETing endpoint h://api.ring.com/clients_api/ring_devices --caused-by-> Request to ring API at h://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
Dec 22 12:32:25 neptune node-red[28755]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:22:19)
Dec 22 12:32:25 neptune node-red[28755]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/main.js:33:15)
Dec 22 12:32:25 neptune node-red[28755]: at process._tickCallback (internal/process/next_tick.js:68:7)
Dec 22 12:32:25 neptune node-red[28755]: ownMessage:
Dec 22 12:32:25 neptune node-red[28755]: 'ring gave a seemingly valid authentication/authorisation, but the failed',
Dec 22 12:32:25 neptune node-red[28755]: causedBy:
Dec 22 12:32:25 neptune node-red[28755]: { Error: problem GETing endpoint https://api.ring.com/clients_api/ring_devices --caused-by-> Request to ring API at h://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
Dec 22 12:32:25 neptune node-red[28755]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:22:19)
Dec 22 12:32:25 neptune node-red[28755]: at Object.authenticatedRequest (/home/node-red/.node-red/node_modules/ring-api/rest-client.js:166:23)
Dec 22 12:32:25 neptune node-red[28755]: at process._tickCallback (internal/process/next_tick.js:68:7)
Dec 22 12:32:25 neptune node-red[28755]: ownMessage:
Dec 22 12:32:25 neptune node-red[28755]: 'problem GETing endpoint h://api.ring.com/clients_api/ring_devices',
Dec 22 12:32:25 neptune node-red[28755]: causedBy:
Dec 22 12:32:25 neptune node-red[28755]: { Error: Request to ring API at https://api.ring.com/clients_api/ring_devices failed with "not authorized" --caused-by-> Request failed with status code 401
Dec 22 12:32:25 neptune node-red[28755]: at module.exports (/home/node-red/.node-red/node_modules/ring-api/propagated-error.js:22:19)
Dec 22 12:32:25 neptune node-red[28755]: at ringRequest (/home/node-red/.node-red/node_modules/ring-api/rest-client.js:71:19)
Dec 22 12:32:25 neptune node-red[28755]: at process._tickCallback (internal/process/next_tick.js:68:7)
Dec 22 12:32:25 neptune node-red[28755]: ownMessage:
Dec 22 12:32:25 neptune node-red[28755]: 'Request to ring API at h://api.ring.com/clients_api/ring_devices failed with "not authorized"',
Dec 22 12:32:25 neptune node-red[28755]: causedBy: [Error],
Dec 22 12:32:25 neptune node-red[28755]: isPropagatedError: true },
Dec 22 12:32:25 neptune node-red[28755]: isPropagatedError: true },
Dec 22 12:32:25 neptune node-red[28755]: isPropagatedError: true }

Most likely they have changed the api "how to login". You see in the log that you get many "not authorized"

As you say, the recent account hackings has most likely forced them to improve security, including the login service I would assume

2 Likes