Bond Online, IP Ping is good, Bond Plugin Says IP not found

[patrickoleary1977]

Describe the bug The Bond is online. The Bond works through the Bond app to control devices. In Homebridge, the log says the IP address is not found. However, the IP address is good and responds to a ping. I found the IP via the Bond app.

Information (please complete the following information):

• everything is on the latest. That is the first thing I checked.

Logs [11/7/2021, 3:50:47 PM] [Bond] Unable to find Bond for IP Address: 192.168.1.22. Skipping this Bond. [11/7/2021, 3:50:47 PM] [Bond] No valid Bonds available.

The bond is definitely available and working, just not in the plugin.

[jweber93]

I ran into this issue as well. Renamed the device from "Fan" to "Dining Room Fan" seemingly resolved the problem. Restarted Homebridge and the device showed up again.

[dkup79]

Same issue for me as the original poster. I am running through user homebridge and using homebridge UI. I am seeing this same issue on a fresh install strictly through the UI.

Previously i installed without the UI and had success reaching Bond when I launched homebridge as the pi user.

More info: homebridge-bond v3.2.9 Node.js Vesion - v16.13.1 npm version v8.3.0 user homebridge

HW: RasperryPi zero W - 16 GB card

[badxhabit]

I am getting the same issue. [1/26/2022, 1:38:51 PM] [Bond] Unable to find Bond for IP Address: 192.168.x.xx. Skipping this Bond. [1/26/2022, 1:38:51 PM] [Bond] No valid Bonds available.

However, works it works in the app.

[dkup79]

I had some success by downgrading a few items.

I was on RaspberryPi Zero which isn't fully supported in Node v16. So I downgraded to v14.18.3.

I'm also currently running homebridge-bond v3.2.6 (which I downgraded prior to dropping node to v14.

[davidmjerry]

I am having this issue every morning. It seems like overnight, the Homebridge and the fan stop communicating for some reason, and I have to reboot Homebridge to resolve the issue. The Bond app works just fine. I tried upgrading to latest beta firmware instead of latest stable for the fan, and that does not make a difference. IP address remains the same, and the devices wifi controller is always on.

[9/12/2022, 12:12:35 AM] [Bond] Erorr sending UDP message: Error: send ENETUNREACH 192.168.1.134:30007
[9/12/2022, 12:12:35 AM] Error: send ENETUNREACH 192.168.1.134:30007
    at doSend (node:dgram:705:16)
    at defaultTriggerAsyncIdScope (node:internal/async_hooks:465:18)
    at afterDns (node:dgram:651:5)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)
[9/12/2022, 12:12:35 AM] Got SIGTERM, shutting down Homebridge...
[Tuya] Socket had a problem and will reconnect to Desk Lights (Error: ERR_PING_TIMED_OUT)
[Tuya DEBUG] after error setting _connect in 5000ms
[9/12/2022, 12:12:40 AM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[9/12/2022, 12:12:45 AM] [HB Supervisor] Restarting Homebridge...
[9/12/2022, 12:12:45 AM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[9/12/2022, 12:12:45 AM] [HB Supervisor] Started Homebridge v1.5.0 with PID: 6401
[9/12/2022, 12:12:46 AM] Loaded config.json with 0 accessories and 3 platforms.
[9/12/2022, 12:12:46 AM] Loaded 2 cached accessories from cachedAccessories.
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loaded plugin: homebridge-bond@3.2.10
[9/12/2022, 12:12:46 AM] Registering platform 'homebridge-bond.Bond'
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loaded plugin: homebridge-tuya@2.0.1
[9/12/2022, 12:12:46 AM] Registering platform 'homebridge-tuya.TuyaLan'
[9/12/2022, 12:12:46 AM] ---
[9/12/2022, 12:12:46 AM] Loading 3 platforms...
[9/12/2022, 12:12:46 AM] [TuyaLan] Initializing TuyaLan platform...
[9/12/2022, 12:12:46 AM] [Bond] Initializing Bond platform...
[9/12/2022, 12:12:46 AM] [TuyaLan] Marked Desk Lights unreachable by faulting Service.Desk Lights.On
[9/12/2022, 12:12:46 AM] [TuyaLan] Starting discovery...
Setup Payload:
X-HM://0023UNYTBKAS5
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

    ┌────────────┐     
    │ xxx-xx-xxx │     
    └────────────┘     

[TuyaDiscovery] Discovery started on port 6666.
[TuyaDiscovery] Discovery started on port 6667.
[9/12/2022, 12:12:47 AM] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge 3353) is running on port 51273.
[9/12/2022, 12:13:00 AM] [Bond] Unable to find Bond for IP Address: 192.168.1.134. Skipping this Bond.
[9/12/2022, 12:13:00 AM] [Bond] No valid Bonds available.
[9/12/2022, 12:13:26 AM] [TuyaLan] Discovered Desk Lights (eb546bfb7d1ff8ca8e9igs) identified as RGBTWLight (3.3)

[chrismerck]

Why "Tuya" in the logs?

[davidmjerry]

Why "Tuya" in the logs?

Just wanted to show the whole picture. It looks like the Homebridge itself rebooted after an issue sending a UDP message to the bond ceiling fan.

I cleaned up the header part to start right where the Homebridge has the complication with the Bond product.

[wildman199]

I'm having the same issue. unable to find IP address. Is there a fix?

[brianhackel]

It looks like the throw at platform.ts:241 causes the whole process to crash.

[04/01/2023, 18:26:57] [Bond] UDP message sent to 10.0.1.81:30007 [04/01/2023, 18:26:57] [Bond] UDP Message received from 10.0.1.81:30007 - {"B":"ZZCC63460","d":0,"v":"v3.8.4"} [04/01/2023, 18:27:58] [Bond] Erorr sending UDP message: Error: send ENETUNREACH 10.0.1.81:30007 [04/01/2023, 18:27:58] Error: send ENETUNREACH 10.0.1.81:30007 at doSend (node:dgram:722:16) at defaultTriggerAsyncIdScope (node:internal/async_hooks:454:18) at afterDns (node:dgram:668:5) at processTicksAndRejections (node:internal/process/task_queues:84:21) [04/01/2023, 18:27:58] Got SIGTERM, shutting down Homebridge...

... snip! ...

[04/01/2023, 18:28:47] [Bond] Unable to find Bond for IP Address: 10.0.1.81. Skipping this Bond. [04/01/2023, 18:28:47] [Bond] No valid Bonds available.

Should this error be better handled (fail and retry later)? Then, when it comes back online, the bond is not found (guessing this was a temporary network error as most report above) and then it just skipped (Bond.ts:63). The result is that you lose all control to your bond silently behind the scenes all because of a simple network hiccup. Should this be a warn and retry as well?

[mcg]

New to Homebridge and was exited to see how easy it was to install and control my Bond fans. Then hit with this bug. #192 may also be related/dupe.