Increase in "No Longer Reachable" following Node & NPM updates

[JasonGoldenDDT]

Describe the bug
Noticed a change in behavior following recent software updates, checking to see if anyone else noticed. I use this plugin to manage a temperature trigger automation, it stands out when it fails.

Reviewing detailed log data I noticed an increase in "no longer reachable" messages. In a log that spans the 1/18/25-1/23/25, I see the message returning on the 20th, around the time I updated NPM and Node.

�[37m[1/20/2025, 11:54:15 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable after three attempts.
�[37m[1/20/2025, 11:54:15 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable after three attempts.
�[37m[1/20/2025, 11:54:15 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable after three attempts.
�[37m[1/22/2025, 5:38:02 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 5:59:09 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted10 redacted46) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 6:00:48 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 6:02:24 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted10 redacted46) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 6:53:55 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 7:34:10 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 8:52:52 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 9:40:09 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted10 redacted46) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:12 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:12 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:12 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:16 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 1)
�[37m[1/22/2025, 11:21:17 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable. (attempt 1)
�[37m[1/22/2025, 11:21:17 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 1)
�[37m[1/22/2025, 11:21:22 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable after three attempts.
�[37m[1/22/2025, 11:21:22 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable after three attempts.
�[37m[1/22/2025, 11:21:22 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable after three attempts.
�[37m[1/22/2025, 11:21:26 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:27 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 0)
�[37m[1/22/2025, 11:21:27 PM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 12:22:23 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 1:10:44 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 1:41:55 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 2:23:01 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted18 redacted8e) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 4:10:37 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 4:21:48 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 4:22:48 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted12 redactedeb) is no longer reachable. (attempt 0)
�[37m[1/23/2025, 4:55:00 AM] �[39m�[36m[Broadlink RM]�[39m Broadlink RM device at redacted17 redacted4c) is no longer reachable. (attempt 0)

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

Desktop (please complete the following information):

• OS: macOS 15.3
• Browser safari
• Version HB 1.8.5 , Node 22.13.1, NPM 11.0.0

Smartphone (please complete the following information):

• Device: iPhone 13 mini
• OS: OS 15.3
• Browser safari
• Version latest

Additional context
Add any other context about the problem here.

[zeromancer1972]

Same here, constantly disconnects and then reconnect. If I am lucky the device is connected at the time I want to control it...

[1/30/2025, 9:16:56 PM] [Broadlink RM] Broadlink RM device at 192.168.178.157 (24:df:a7:7a:e0:9a) is no longer reachable after three attempts.
[1/30/2025, 9:16:56 PM] [Broadlink RM] Broadlink RM device at 192.168.178.157 (24:df:a7:7a:e0:9a) has been re-discovered.

[JasonGoldenDDT]

Hey @zeromancer1972! Thanks for bringing this back unto the top for me. I have a few open issues I'm troubleshooting frequently with Homebridge. This is an ongoing challenge I make a habit of monitoring after updates.

I've configured my log retention to span multiple days, this has allowed me to see changed in behavior following updates.

To date I've learned these devices are sensitive QOS settings. It also needs an open connection to the internet. It will increase these disconnects if it can not connect to the company's servers. Not ideal, I keep my eye out for IR platforms.

I've also learned that common SSIDs can result in frequent hopping between radios in crowded radio environments. Instead I manually steer my IOT devices to specific APs and radios to minimize these disconnects where commands and responses can get dropped. This approach using 2 wired AP in a mesh configuration has improved my networks performance.

there are things you've likely considered, but I'll just point out that turning these settings minimized this disconnect events for me.

I've also noticed after updates to Node these invents can increase. Every free weeks I copy the log, view it through console and run through a short list of terms to see if those events appear more or less frequently after any given change to the system.

I have 4 RM devices, 1 is the RM Mini 4 - has a temp sensor - this one gets pinged a lot and can become unstable.

In my research found device firmware can impact it, I'm running V62092 came that way. Ensure your power supply is sized appropriately for the device and has stable power.

Moving this device to an IOT Specific SSID using its preferred frequency I saw a significant improvement in reliability. I also found most routers are biased to channels 1 and 11 on 2 Ghz, in my crowded radio environment with over 70 wifi radios and commercial sources, the wind can affect interference. Using inSSIDER to manually identify open channels brought my network experience up to a stable 88% from 83% and resulted in fewer dropped commands.

Installing a detected wired appleTV to use as the preferred hub also helped reduce "no response" messages.