aarons22 / homebridge-bond

Homebridge plugin for Bond
MIT License
64 stars 31 forks source link

Getting error "Unable to find Bond for IP Address" with proper IP address and Bond Token configured #229

Closed Nevs123 closed 1 month ago

Nevs123 commented 1 year ago

Describe the bug I am receiving a "Unable to find Bond for IP Address" error in my logs for Homebridge using a newly purchased BD-1000. I've tried everything I can think of (outlined below) and cannot get the bond to be picked up by Homebridge.

Information (please complete the following information):

Logs Log output is very limited. I tried running this in debug mode but it did not provide ANY further detail:

[21/12/2022, 14:36:38] [Bond] Unable to find Bond for IP Address: 192.168.2.61. Skipping this Bond. [21/12/2022, 14:36:38] [Bond] No valid Bonds available.

** Bond Info *** bondId: ZZFG32391 FW: v3.8.4 API: v2 (unsure how to check this) Make: undefined Model: BD-1000


rajiviyengar commented 1 year ago

I am facing the same error with my bond "Unable to find bond for IP address." I also copy and pasted the token to avoid mistyping. The bond bridge is set up using a static IP on my router. Pinging the bond is successful and bond is functioning normally via the app. Downgrading to version 3.2.9 did not solve the issue.

Nevs123 commented 1 year ago

I am facing the same error with my bond "Unable to find bond for IP address." I also copy and pasted the token to avoid mistyping. The bond bridge is set up using a static IP on my router. Pinging the bond is successful and bond is functioning normally via the app. Downgrading to version 3.2.9 did not solve the issue.

Glad to see I’m not the only one. I can even ping the IP address from the homebridge terminal and get a response back, but the plug-in for some reason is not able to recognize that the static IP is a Bond bridge.

Any guidance here or tests I should try? I’d like the keep the bond bridge but may send it back if I can’t solve this.

rajiviyengar commented 1 year ago

The bond bridge and homebridge plugin were working perfect for the past year. The error only started after my raspberry pi got corrupted, and I reinstalled homebridge and Raspbian.

Nevs123 commented 1 year ago

I dug into the API documentation and ran some of the commands from the terminal within homebridge itself. Maybe some of this is useful for troubleshooting? I've redacted a few details for privacy.

It seems I can perform all of the basic API calls directly from homebridge, so it's odd that the bond plugin can't seem to recognize the device I'm pinging.

Unlike @rajiviyengar, I've just purchased the bond device and have never actually got this work yet.

Token Command curl -i http://**[BOND IP ADDRESS]**/v2/token

HTTP/1.1 200 OK
BOND-Flags: 4
Content-Length: 214
Content-Type: application/json; charset=utf-8

{"locked":0,"pin_attempts_left":10,"token":"**[token provided here]**","nonce":"f50a964b8f2f74be","v1_nonce":"0000000000000000","account_code":"**[Account Code Here]**","v1_email":"","disable":false,"_":"bb32ff10","__":"bb32ff10"}

Version Command curl -i http://**[BOND IP ADDRESS]**/v2/sys/version

HTTP/1.1 200 OK
BOND-Flags: 4
Content-Length: 275
Content-Type: application/json; charset=utf-8

{"target":"zermatt","fw_ver":"v3.8.4","fw_date":"Thu Nov 10 15:16:25 UTC 2022","uptime_s":998,"boot_patch":"not first boot","make":"Olibra","model":"BD-1000","branding_profile":"OLIBRA_BD1000","bondid":"**[bond id here]**","upgrade_http":true,"api":2,"_":"8a969a0a","__":"8a969a0a"}

List Bond Devices Command I dont currently have any underlying devices configured

curl -H "BOND-Token: [BOND TOKEN HERE]" -i http://**[BOND IP ADDRESS]**/v2/devices

HTTP/1.1 200 OK
BOND-Flags: 4
Content-Length: 34
Content-Type: application/json; charset=utf-8

{"_":"00000000","__":"00000000"}

I am unsure if this is related, but I am also unable to configure Siri Shortcuts for some reason. If I configure the bond bridge with a ceiling fan, and configure a Siri shortcut for 1 of the commands, then attempt to run the shortcut from the shortcuts app, I get an error. This seems to happen for every control I've tried on my ceiling fan (3-speed, 1 light)

The operation couldn't be complete. (iOS_BondSD-K.BondResponseError error 1.)

patrickoleary1977 commented 1 year ago

Same issue here as well.

Multiple times per day, I need to reboot home bridge because any bond items in HomeKit stop working. When I check the log, it always shows the below. When I reboot, it fixes it 1/2 the time. Sometimes a 2nd reboot is necessary. When I check the bond app, the bond is available and I can control the devices from within Bond. I have the IP address of the device fixed for the bond. Thoughts?

Unable to find Bond for IP Address: 192.168.1.50. Skipping this Bond. [1/19/2023, 3:00:24 AM] [homebridge-bond] No valid Bonds available.

patrickoleary1977 commented 1 year ago

I think the issue with this is the Bond itself. Anytime the Home app doesn't work, I check the Bond app and it says it is Syncing....

If it gets out of Syncing status, and if I reboot Homebridge, it all works again. It just wont stay in Connected status.

rajohn96 commented 1 year ago

anyone made any progress on this? I see that the axios version included here is quite a bit behind the current release. As the error stems there maybe updating that component would solve it?

cptoaks commented 1 year ago

I have the same issue: [4/19/2023, 4:15:31 PM] [Bond] Unable to find Bond for IP Address: x.x.x.x. Skipping this Bond. [4/19/2023, 4:15:31 PM] [Bond] No valid Bonds available. Also bond bridge shows 'status: syncing...' continuously in the bond app.

88gts commented 1 year ago

noticing this too, device is online and connected via app, pulling the IP and Token from the app and Homebridge reports the following each time, despite the host pinging the IP.

[6/1/2023, 11:24:40 AM] [Bond] Unable to find Bond for IP Address: 10.0.1.79. Skipping this Bond. [6/1/2023, 11:24:40 AM] [Bond] No valid Bonds available.

patrickoleary1977 commented 1 year ago

I personally think it’s an issue with Bond. Even without Homebridge, I can’t get it to work now. On Jun 1, 2023, at 2:30 PM, 88gts @.***> wrote: noticing this too, device is online and connected via app, pulling the IP and Token from the app and Homebridge reports the following each time, despite the host pinging the IP. [6/1/2023, 11:24:40 AM] [Bond] Unable to find Bond for IP Address: 10.0.1.79. Skipping this Bond. [6/1/2023, 11:24:40 AM] [Bond] No valid Bonds available.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

droopdog7 commented 1 year ago

Well, I am coming here to report the same issue. Seems that there hasn't been a solution (sigh) but reviving this thread in case someone has it figured out.

88gts commented 1 year ago

it is working for me, i noticed that the device needs to be online and powered up before Homebridge initializes it.

droopdog7 commented 1 year ago

it is working for me, i noticed that the device needs to be online and powered up before Homebridge initializes it.

Can you be a little more specific. Also, I am not any kind of expert so go slow.

88gts commented 1 year ago

your bond unit must have power and be online through the app when Homebridge starts up.

droopdog7 commented 1 year ago

your bond unit must have power and be online through the app when Homebridge starts up.

Thanks. I've had the bond powered and online each time and still no joy. Sigh. Anyway, let me paste my config file in case someone sees an error. FYI, I have redacted a few characters here and there.

{ "bonds": [ { "ip_address": "192.1XX.4.XX8", "token": "7XXXX947aXXXX2cd" } ], "include_dimmer": true, "include_toggle_state": true, "fan_speed_values": true, "_bridge": { "username": "0E:38:X4:48:X2:X1", "port": 48379 }, "platform": "Bond" }

dxdc commented 1 year ago

I think I may have fixed the problem, which stems from:

https://github.com/aarons22/homebridge-bond/pull/252

Curious to know if this is working for anyone else, it seems to have fixed my system.

aarons22 commented 1 year ago

I published the fix from @dxdc into a beta release - https://github.com/aarons22/homebridge-bond/releases/tag/3.2.11-beta.1

I can't verify it myself, so if there is anyone here who can, that would be great :)

y0m1g commented 9 months ago

I faced this issue today (on 3.2.10); upgraded to 3.2.11-beta.2 and it's working fine again now! :)

mosherc commented 4 months ago

I don't know if this is exactly the same issue, but I can't get mine to work even on the new beta version. When I check my Netgear router, the bond bridge is not listed as an attached device (neither IP or mac address), but it is listed in access control. I set the IP address to the same as the one in access control in Netgear, in the iOS app. When I do ping ZZHE...2.local on my mac on the same network, I get cannot resolve unknown host, and of course an error in the homebridge logs. Anybody know what's up? The bridge works fine and connects over my 2.4ghz network fine.

I should add that the IP address I am using across the board works with the token in Home Assistant.

Edit: Actually just checked again in home bridge and it's showing there now. It's also showing up in my router attached devices, so I guess my router was a little slow.

aarons22 commented 1 month ago

Fixed in 3.2.1