Bond Bridge Pro + HomeKit Feedback Please

Hello. I’m requesting real-world feedback on how the integration of shades directly into HomeKit is going for Bond Bridge Pro users now that this feature looks to be out of beta. I currently have 25+ Somfy blinds and awnings integrated into Google Home and HomeKit (via HOOBS) using two Bond Bridges. However, I am becoming increasingly frustrated at the unreliability of the HomeKit integration, and would like to take the HOOBS out of the chain. Before I spend the unbelievably high price of the Bond Bridge Pro here in Australia, I’d really like some reassurance that this is going to be a positive move.

Glad to hear from users also, but I can say that we are actually not recommending the built-in HomeKit support for users with more than 20 shades. The local API (which aaron22’s HomeBridge driver uses) should be reliable, but the built-in HomeKit support has some issues at larger number of shades.

@merck, that is disappointing to hear, especially for a controller that is rated for 50 devices. I suppose that “more that 20 shades” limitation could be spread across two Bond Bridge Pros, but that would be an awfully expensive solution? Anyway, I don’t understand what you mean by the phrase: “The local API (which aaron22’s HomeBridge driver uses)” - what is “the local API” and what does a HomeBridge driver have to do with Bond Bridge?

I assumed this was via HomeBridge, but perhaps HOOBS has it’s own implementation of a driver for the Bond Local API? Or is HOOBS using the HomeKit API?

Sorry, I know it’s disappointing. We are supposed to take a look at improving this a bit in the next month, so we may be able to “get it out of beta” and up to the 50 device limit for the early January firmware release, but it’s not certain yet.

I too am thinking of getting a Bond Bridge Pro, but in my case, I have 18 shades to control and probably not be getting any more. And I’m not using HOOBS, just Homebridge. Is the 20 shade limit a hard limit or just things could go wonky after 20 shades? Is that a limit of the Homebridge plugin or of the Bond Bridge Pro?

@jupiterone, this thread is about direct integration between Bond and HomeKit, WITHOUT the HomeBridge/HOOBS intermediary. HomeBridge and HOOBS can both integrate many blinds and awnings (and fans, etc) being controlled in a Bond Bridge, but it is an extra step in the chain that I was trying to [partially] avoid with this new Bond Bridge Pro feature.

Understood. Did you ever get an answer to your question about the 20 shade limit being a limitation of HomeKit or is it a limitation of the bridge? I too have Somfy blinds and am trying to decide of I should pull the trigger on a Bond Bridge Pro.

I didn’t ask that question, but I can confidently say that it is not a HomeKit limitation as I currently bring all of my blinds and awnings into HomeKit through HOOBS using just the basic Bond Bridge.

Any chance we could get a way to control what’s exposed to HomeKit? I would prefer to just have the bond groups instead of the individual shades. When grouped in HomeKit it doesn’t send the group signal out, just each shade individually.

That’s a reasonable ask. I’ve often thought that for Alexa/GH we could do similar. But then would it be an account-level, or Bridge-level setting? Or would you be able to adjust this for every Group or Shade? You see, it has a complexity to it.

What we are doing on the Alexa/GH side is implementing Scenes, and you can have a Scene control a Group and thereby send out a single aggregated signal (for technologies like Rollease Acmeda or Gaposa USA that support such aggregation).

Honestly you probably wouldn’t see this until Scenes support in Matter, unless someone adds it to a community HomeBridge driver. (GitHub - aarons22/homebridge-bond: Homebridge plugin for Bond or similar)

Sadly, there is the issue with having a large number of shades. That’s what I’m hoping the groups could help with. I’m currently using homekit integration, but I’m worried that once I get more of my shades on Bond I’ll start running into the “unresponsive” issue. I already get that with the Automate Pulse 2 hub…

Makes me wonder if the issue is really more of a homekit problem vs a driver or integration piece.