tsightler
commented
2 months ago Hi, thanks for opening and issue and providing logs. The logs clearly show errors with the network connectivity. For the most part, having some errors polling the Ring API is normal, and not really indicative of a problem per-se, Ring API servers are sometimes slow to respond and the requests timeout but will just try again later, so having some of these messages is "normal", for example I see anywhere from a dozen, to 40-50 such messages in a day in my own installation. Certainly you seem to be having a higher than normal failure rate, but these would not cause the plugin to fail to function, unless they were failing every single time, and, even then, that would not likely impact alarm functions, which use a websocket for communications.
It's important to note that the plugin is not somehow doing something super special here, it is calling the fetch API built in to NodeJS and asking it to retrieve the URL. The fetch API either returns the data, or an error if it can't retrieve the data. If the fetch API fails to retrieve the data, there's nothing for the code to do except report the error and try again.
However, there is another interesting tidbit in the log, specifically this part:
[10/1/2024, 10:24:04 AM] [homebridge-ring] Reconnecting location socket.io connection
[10/1/2024, 10:24:05 AM] [homebridge-ring] Creating location socket.io connection - Home
[10/1/2024, 10:24:06 AM] [homebridge-ring] Ring connected to socket.io serverSo this is the websocket connection I mentioned above, all communications with Ring Alarm uses this websocket, not the HTTP requests. However, this log entry indicates that the websocket lost connection and had to be re-established. Again, this happening every now and then is no big deal, but if you are seeing this often, it's just another indicator that something is happening at the network layer. Note that it usually takes lost connectivity of longer than 60 seconds before the websocket will detect missed connectivity and restart, so this indicates significant network issues.
In summary, you have fetch API failing often, which indicates network issues, and websocket API disconnected, which indicate network issues. You will need to try to troubleshoot what network connectivity issue you are having. I would check the system logs on the host running Docker as a place to start, especially of this host is running in a VM based on KVM hypervisor (something like Proxmox, etc) as that recently had a known issues that was causes lots of dropped packets and created a lot of similar networking issues for users of ring-mqtt, which uses the same API. Alternatively, you can capture a packet dump with some tool like tcpdump or Wireshark.
markcarroll
owellsjr
benjorito
pcziesch
cknova1979
Is there an existing issue for this?
Describe The Bug
Getting "Failed to reach Ring server at https://api.ring.com/clients_api/ring_devices. fetch failed. Trying again in 5 seconds..." very frequently. It makes HomeBridge unusable (maxes CPU and memory) until I reboot the container. The HomeBridge docker container is running Node 20.
Note that rebooting doesn't actually fix the Ring plugin for long. I can change alarm state etc briefly after a reboot, but a couple of hours later it is broken again. Turning the alarm on or off will work immediately after a reboot, but given a couple of hours, any interaction with Ring will cause the error. It seems to put Homebridge into 9x% CPU and fills up memory so a full container reboot is needed.
To Reproduce
Just leave HB running. Container logs will show list of errors.
Expected behavior
It works like it used to.
Relevant log output
Screenshots
No response
Homebridge Ring Config
Additional context
homebridge-ring.log.txt
OS
Ubuntu Jammy (22.04.4 LTS)
Node.js Version
v20.17.0
NPM Version
?
Homebridge/HOOBs Version
Homebridge v1.8.4 · UI v4.57.1
Homebridge Ring Plugin Version
v13.1
Operating System
Docker