Finally got around to setting up my Bond Bridge Pro last night. It is running firmware version 3.13.8. I am using Bond app V2.45.0 on iOS 16.4.1 (a). The initial Bond Bridge Pro setup went fine, but when it came time to add the bridge to HomeKit, I ran into issues.
Both the iOS device (iPhone) and the Bond Bridge Pro are on the same subnet. When following the Bond HomeKit integration instructions posted, it takes the iPhone a LONG time (5+ minutes) to find the Bond Bridge so I can attempt to add it to my home, and then after providing the setup code, the iPhone takes a LONG time to try and add the Bridge, and then eventually errors out with something to the effect of, “Accessory cannot be added because it cannot be found.”
Has anyone else run into this issue before? How can I fix whatever problem is plaguing my install so that I can add the Bridge to HomeKit?
Memorializing a fix in the absence of vendor support…
I originally had the BBP networked via wired connection. After the “HomeKit cannot even see the BBP” issue described in my second post, I decided to reset the BBP and switch it over to WiFi.
On the same network, but connected via WiFi instead of wired connection, I was able to add the BBP to HomeKit without issue.
Not sure if this is a BBP issue or a HomeKit issue, but my problem has been solved for the time being.
I know that it works with mDNS (Bonjour, the Apple implementation), but didn’t get into the details to know why it won’t work when wired connected.
I have the same problem. Thanks for the excellent post and for including your solution, @itswilly .
At least thanks to you I know it’s solvable. I wish I was an omniscient God so that I could know to read your post before I wasted 3 hours setting up the hub on Ethernet, properly statically routing it by its Ethernet MAC, configuring 14 shades by the right rooms and names to eventually slot cleanly into my HomeKit, running into your identical error, and finally doing all manner of troubleshooting (with nothing useful from Bond “documentation”) before arriving at your solution.
I wish I was even more omniscient so that I could have known not to idiotically spend $100+ EXTRA money on the Pro solely for Ethernet connectivity, were I to know that the very same Ethernet would render it useless / unreachable by HomeKit. False advertising aside (not legally probably, just spiritually), Endy and @residualimages , I see also that after nearly 2 years neither of you nor your employer have actioned on this nor provided further steps nor patches, despite having your customers pay more for an inferior “upgrade”. We’re in a down economy so I wish you both the best, but I also hope you both feel just a tiny a bit shittier about yourselves for the rest of your day, for disrespecting your user like this (which as a fellow technologist I view as the gravest crime of our profession).