4.32.7 HomeKit Broken / Regression - Accessory Out of Compliance

1

Hi Bond Support, @merck

I’m experiencing what appears to be a HomeKit/HAP regression immediately following today’s Bond Bridge firmware + app update to 4.32.7

This setup worked reliably for years prior to today’s update.

Environment:

  • Bond Bridge: BD-1000

  • Network: flat single subnet, no VLANs

  • Router: Netgear RS700

  • Bond on 2.4 GHz Wi-Fi

Apple ecosystem:

  • iPhone on latest iOS 18

  • iPad Pro on latest iPadOS 26

  • Apple TV (Ethernet)

  • 4 HomePods

Important:

  • Native Bond app local control works perfectly for all shades/screens

  • Only HomeKit integration failed immediately after today’s update

Original symptom:

  • Existing HomeKit devices went “No Response”

  • Removed Bond Bridge from Apple Home

  • Re-pair attempts hung indefinitely during “Adding Accessory”

Troubleshooting performed:

  • Isolated all Home Hubs (Apple TV + HomePods unplugged)

  • Verified Bonjour/mDNS functionality

  • Verified HAP advertisements via macOS dns-sd

  • Verified Bond API access via local token

  • Cleared HomeKit state using:
    curl -X DELETE -H "BOND-Token: " http:///v2/api/bhk

Key findings:

Bond initially advertised:

  • sf=0

while Apple Home no longer had the accessory paired.

After DELETE reset:
API correctly showed:

  • “enabled”: false

  • “paired”: false

After re-enabling HomeKit:
dns-sd showed:

  • sf=1

and HomeKit discovery immediately improved.

However:
Both iPhone and iPad now fail with:

  • “Accessory is out of compliance”

After the failed pairing attempt:
Bond immediately reverts to:

  • “paired”: true

and advertises:

  • sf=0

This appears to indicate either:

  • stale/corrupted persistent HomeKit pairing state

  • HomeKit compliance regression introduced in 4.32.7

  • failed cleanup/reload of persistent HAP controller records

Additional technical observations:

  • Bonjour/mDNS resolution works correctly

  • _hap._tcp advertisements resolve normally

  • HAP endpoint reachable on port 4567

  • No evidence of multicast/network isolation issues

  • Multiple Apple clients reproduce identically

Sample advertisement after clean reset:

  • sf=1

  • pv=1.1

  • md=BD-1000

  • c#=1

Sample advertisement after failed onboarding:

  • sf=0

  • paired=true restored automatically

Questions:

  • Any known HomeKit regressions in 4.32.7?

  • Is there a deeper HomeKit reset path beyond /v2/api/bhk DELETE?

  • Is firmware rollback possible?

  • Is there hidden persistent HAP database state surviving DELETE/reset?

Happy to provide additional logs/screenshots or jump on a diagnostic session if useful.

2 Likes
HomeKit Issues after Firmware Upgrade
2

I had exactly the same problem. I ended up doing a factory reset on my bond and then re added it to HomeKit. Also tried to do a backup and restore of the config after the reset however this reintroduced the compliance error. Performed another reset and manually re added all my devices. Painful experience as far as HomeKit automations go however I created dummy devices (fans and blinds) with homebridge and moved my automations across to these before I reset my bond, then moved them back to the newly created bond instance.

1 Like
3

The new firmware works fine for my two hampton bay fans. The homekit can expose the fan and light controls but have some issues. For example dimmer control for light is missing, it became only toggle. 6 speeds fan became only 3 speeds. So I just disabled the homekit and use the Home Assistant Bond integration instead which provides more controls.
Will try it again in the future with my apple tv