[APP][Pro] HomeKit Device Bridge

You’re very welcome! I’m glad to hear the update completely resolved your air conditioning issue. Enjoy your Apple Home setup, and feel free to reach out if you notice anything else."

Looks perfect now!!!

Version 2.1.24 — Reliability: Standalone accessories (TVs) now retry with a new port if a port conflict occurs during streaming. Strengthening: The theoretically weak randomness backup mechanism in the HomeKit code generator on the settings page has been removed; it now always uses a cryptographically secure random source.

Version 2.1.26 — The issue of devices becoming inaccessible from the Home app due to an mDNS advertising error has been fixed.

Version 2.1.28
New Diagnostics panel in Advanced Settings: see at a glance whether the bridge is actually advertising, how many accessories are bridged, which devices Homey currently reports as unavailable (the ones showing “No Response” in Apple Home), whether any mDNS advertising errors occurred and when, whether auto-recovery ran, and whether the connection watchdog is ticking normally — a watchdog that has stopped is flagged in red, while one that simply has not run yet after a restart is shown as starting up.

Version 2.1.29

  • Improved HomeKit bridge discovery and mDNS reliability.

  • Fixed repeated service name conflict reports.

  • Reduced network-unreachable error reports during temporary connection changes.

  • Added safer automatic fallback handling for HomeKit advertisements.

Hey, I added your app to my Homey and it works fine for my devices.

One of the things I am struggling with is, is to get flows to trigger. What I did is:

  1. Create a Flow starter device in Homey
  2. Make sure that a button press of that Flow starter triggers my flow, through an extra flow
  3. Expose the flow starter buttons to Homekit, in the bridge settings.
  4. My Flow starters appear in Homekit

But in Homekit, when I press one of those buttons, it opens up the configuration page, saying that my button is not configured. In the Homekit Bridge settings, they are exposed as ‘Auto (Button)’.

In my Homekit configuration page I can assign stuff to ‘Press once’, ‘Press Twice’, ‘Long Press’, but that allows me to connect Homekit devices, instead of it triggering my Homey Flow.

I also tried changing the Expose as to ‘Switch’, to see if that does anything, but then the Switch turns on, and turns off quickly again, not triggering my flow.

Got any tips on how to get this working?

Hi , if you could send me your diagnostic log, it would help me determine the cause of the error.

Sure, this is my log id: be04ab31-730c-4c04-9e84-076b9a08b3f3

Test Version 2.1.30

  • Added support for creating multiple independent Flow Starter devices.

  • Each Flow Starter now appears as a separate HomeKit switch.

  • Fixed multiple Homey Flows being triggered by a single HomeKit button.

  • Improved automatic switch reset and state synchronization.

This works!

Test Version 2.1.31

  • Improved bridge startup recovery and overall reliability.
  • Prevented conflicts between publishing, syncing, and bridge reset operations.
  • Added automatic retries for devices that fail to publish temporarily.
  • Improved listener management to reduce duplicate events and resource usage.
  • Added secure, persistent setup codes for standalone accessories.
  • Preserved device selections during incomplete Homey startup states.
  • Completed settings and diagnostics translations.
  • Added new reliability, localization, and release integrity tests.

V 2.1.32

  • Improved HomeKit bridge reliability during temporary mDNS and network interface errors.

  • Added automatic bridge advertisement recovery.

  • Prevented the bridge from remaining incorrectly marked as published after announcement failures.

  • Improved watchdog-based self-healing.

  • General stability improvements and metadata consistency fixes.

Hi!.
Just wondering, are there any plans to support multiple bridges in the future?

For larger Homey installations, being able to split devices across two or more bridges could be useful, especially when approaching HomeKit’s accessory limit. For example, one bridge for lights and switches and another for sensors or other devices.

Hi! Support for multiple bridges is technically possible. If I receive enough requests from users with larger Homey setups, I might consider adding this in a future update.

HomeKit Device Bridge has been working really well with my Homey and Apple Home setup, and I’d like to thank @ugrbnk for the excellent support.

I had an issue with irrigation valves connected to Fibaro Double Relay Switch 2 modules: they worked when exposed as switches, but not as sprinklers. After I reported the problem, the developer investigated it, explained the cause, and quickly provided an update.

I’ve tested the update and can confirm that the valves now work correctly as sprinklers in Apple Home.

It’s great to see a developer who listens to feedback and follows through with a working fix. I’m very happy with the app and can recommend it to anyone looking to bring their Homey devices into Apple Home.

Thanks again for your work and the quick response!

What’s new

Version 2.1.35

  • Improved memory and connection management.

  • Fixed potential issues during reconnection and app shutdown.

  • Improved timeout and error handling for device controls.

  • Reduced unnecessary synchronization and discovery processing.

  • Improved error detection for HomeKit network announcements.

What’s new

Version 2.1.36

  • Improved error handling for garage door, siren, blinds, speaker, and air purifier controls.
  • Fixed a timing issue that could republish the bridge during shutdown.
  • Prevented outdated device updates from overwriting newer states or restoring deleted devices.
  • Reduced duplicate driver information lookups during simultaneous updates.
  • Fixed settings inconsistencies caused by overlapping changes or failed saves.

Really nice work on this, Uğur!

Getting Homey devices into Apple Home is already a great feature, but what I really like is that you didn’t just stop at basic devices. The support for different device types, especially TVs, and the way they show up properly in HomeKit are really nice touches.

For anyone using more than one smart home ecosystem, an app like this can make a huge difference. Being able to manage everything from one place instead of constantly switching between different apps is a big plus.

It’s also great to see that you’re not just releasing the app and moving on. You’re actively improving it, listening to feedback here, and taking the time to help people when they run into issues. That makes a big difference too.

Homey is already a powerful platform, but apps like this make it even more flexible and useful.

Great job, mate! Really looking forward to seeing how this develops with future updates. Keep it up!

Camera & HomeKit Secure Video Testing — Volunteers Welcome

Hi everyone,

I’m preparing a test release of HomeKit Device Bridge with camera support and would appreciate your help testing it across different Homey setups.

What’s included

  • Live video from compatible cameras added through the UniFi Protect Homey app, ONVIF Camera app.

  • Camera motion sensors in Apple Home.

  • HomeKit Secure Video (HKSV) recording for compatible streams.

  • Recorded audio through compatible AAC-LC passthrough, without continuous audio/video transcoding.

  • Separate ARM64 and x64 media packages.

Cameras are disabled by default. You can individually enable camera export, motion sensors and HKSV in the Cameras section of the bridge settings. HKSV compatibility depends on the camera stream and your Apple Home recording setup.

Live video, remote access, motion and HKSV have worked in my Homey Pro setup. However, real-world Self-Hosted Server testing is still needed, particularly on Intel/AMD x64 systems and Mac mini installations.

Please help test

  • Local and remote live viewing.

  • Multiple motion recordings over time, including recorded audio.

  • Camera switching and simultaneous viewing while HKSV is enabled.

  • Recovery after a camera disconnects or the bridge app restarts.

  • CPU and memory usage over 24–48 hours, including whether usage settles after viewing stops.

  • Whether existing non-camera devices and Flows continue working normally.

When reporting results, please include

  • Bridge app version and Homey model/SHS setup.

  • Camera model and Homey integration used.

  • Apple device/OS and active home hub.

  • What worked, what failed, and how to reproduce the issue.

The Download camera report option in the Cameras section provides an anonymized report. Please do not post passwords, HomeKit setup codes, full camera URLs or unsanitized diagnostic logs publicly.

This is a test release, so please keep a backup and avoid relying on it as your only recording system. Update your existing installation without uninstalling or resetting the bridge.

**Test version: HomeKit Device Bridge | Homey

Thanks to everyone willing to help. Feedback from different setups will help us identify compatibility issues before the wider release.