[Ring] Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. getaddrinfo ENOTFOUND api.ring.com. about ring HOT 3 CLOSED

getaddrinfo ENOTFOUND api.ring.com

This is quite simple, the plugin is unable to resolve the hostname. This is not directly a plugin issue, it can be caused by network issues, DNS issues, conflicts with older, non-updated plugins that do things which break the internal NodeJS network functions, etc. but there's nothing than can be done to resolve this from a plugin perspective.

from ring.

Is there any way to fix this error by going into the plugin and making changes myself? This is an odd error that I cannot seem to resolve and I'm having no DNS issues from the homebridge terminal when using dig or ping. Only the ring plugin is having these issues. Is there a specific version of NodeJS is should downgrade to have better compatibility with this older plugin?

from ring.

Is there any way to fix this error by going into the plugin and making changes myself? This is an odd error that I cannot seem to resolve and I'm having no DNS issues from the homebridge terminal when using dig or ping. Only the ring plugin is having these issues. Is there a specific version of NodeJS is should downgrade to have better compatibility with this older plugin?

Figured out a nice little fix by caching DNS within the homebridge docker and adding additional nameservers. Now it's just a failed to reach server.

from ring.