Homebridge: Bringing Non-HomeKit Devices into Apple Home

Apple’s smart home ecosystem is genuinely good once everything is in it - one app, real end-to-end encryption, and automations that don’t depend on a cloud server staying online. The problem is getting everything into it in the first place. A huge number of decent, cheap devices - especially older Zigbee and Wi-Fi kit, and plenty of budget brands that never bothered with Matter or HomeKit certification - simply don’t talk to Apple Home natively. Homebridge is the tool that closes that gap, and it’s been doing it for years, well before Matter existed.

What Homebridge Actually Does

Homebridge is free, open-source software that runs on a small always-on computer on your network (a Raspberry Pi is the classic choice, but any low-power always-on machine works) and presents itself to Apple Home as a HomeKit bridge - a single “device” that actually represents dozens of underlying devices behind it. Individual “plugins” - community-maintained integrations, over 2,000 of them at this point - handle the translation for specific brands and protocols: TP-Link Kasa, Govee, Broadlink, MQTT-based devices, even other smart home platforms like Home Assistant itself. Once a plugin is installed and configured, the devices it exposes show up in the Apple Home app exactly as if they were natively HomeKit-certified, complete with Siri control, automations, and the Home app’s own widgets.

Crucially, Homebridge runs entirely on your local network. It doesn’t route your device data through a third-party cloud service to make the HomeKit translation happen - it’s a local bridge, which matters both for privacy and for the “does it still work if the internet’s down” test that a lot of cloud-dependent smart home setups fail.

What You’ll Need

• An always-on computer on the same network as your Apple devices - a Raspberry Pi 4 or 5 (£40-80 in the UK) is the most common choice, though a spare mini PC or an existing Home Assistant box works too
• An iPhone, iPad or Mac running a reasonably current OS version, to add the bridge to Apple Home
• Your devices’ existing apps or accounts already set up and working (Homebridge plugins generally connect to the same accounts/APIs those apps use, not to the devices directly over a different protocol)

Installing Homebridge

The current recommended route for most people is the official Homebridge Raspberry Pi image, which comes with the Homebridge service, Node.js and the web-based configuration UI already set up - you flash it to an SD card with Raspberry Pi Imager the same way you would a normal Raspberry Pi OS image, boot it, and it’s ready. If you’d rather run it on an existing Linux box, macOS machine or inside Docker, the official `hb-service` installer script and Docker image both handle the setup in a few commands.

Once it’s running, open a browser on any device on the same network and go to `http://homebridge.local:8581` (or the Pi’s IP address if `.local` resolution isn’t working on your network). This loads Homebridge Config UI X, the web interface you’ll use for everything from here - installing plugins, editing configuration, and viewing logs when something isn’t behaving.

Installing a Plugin

From the Config UI X dashboard, the Plugins tab has a search box that covers the full public plugin registry. Search for your brand or protocol by name - “TP-Link”, “Govee”, “Broadlink”, “MQTT Thing” are all genuinely popular examples - and install the top result from a verified publisher (look for the “Homebridge Verified” badge, which means it’s been checked against basic quality and maintenance standards, not just uploaded once and abandoned).

Most plugins have a settings form right there in the UI rather than requiring you to hand-edit a config file - you’ll typically enter account credentials (for cloud-connected brands) or local network details (an IP address or MAC address for local-only devices), then restart Homebridge from the same dashboard for the change to take effect. Some plugins - MQTT-based ones especially - need a bit more manual JSON configuration, and their GitHub README is the reliable source for the exact fields required, since these details vary a lot between plugins and change as devices get firmware updates.

Adding the Bridge to Apple Home

Open the Home app on your iPhone or iPad, tap the “+” to add an accessory, and it should discover “Homebridge” as a nearby device automatically (make sure your phone is on the same Wi-Fi network, not on mobile data). Tap it, and you’ll be asked for a setup code - this is shown on the Homebridge dashboard’s status page, or printed to the terminal/log on first boot. Enter it, and every device exposed by your installed plugins appears in Apple Home as individual accessories, ready to be renamed, assigned to rooms, and used in automations exactly like native HomeKit devices.

Splitting Devices Across Multiple Bridges

HomeKit has a hard limit of 150 accessories per bridge. It sounds generous until you remember that some devices expose multiple accessories at once - a single smart plug with energy monitoring might count as two or three - and a household running Homebridge alongside a large Home Assistant instance or a big Govee setup can hit that ceiling faster than expected. Config UI X supports “child bridges,” where individual plugins run as their own separate bridge process with their own pairing code, each with its own 150-accessory allowance. If you’re running a lot of plugins, enabling child bridges for your largest ones (from each plugin’s settings, under “Bridge Settings”) is worth doing proactively rather than after you hit the limit and devices mysteriously stop appearing.

Keeping It Reliable

Because every device in Apple Home now depends on this one bridge staying online, a few habits make a real difference to reliability. Give the Homebridge machine a static IP or a DHCP reservation on your router, so it doesn’t silently change address and break the pairing. Enable automatic updates for Homebridge itself and your plugins from the Config UI X settings, but check the release notes before major version bumps - occasionally a plugin update changes its configuration schema and needs a manual tweak afterwards. And if you’re running it on a Raspberry Pi, use a proper power supply and a good quality SD card (or better, boot from a USB SSD) - flaky power and cheap SD cards are a disproportionately common cause of “Homebridge just stopped working overnight” reports.

Frequently Asked Questions

Does Homebridge replace Matter, or do I still need it once my devices support Matter?

Matter is gradually reducing the need for Homebridge on newer devices, since a genuinely Matter-certified device can join Apple Home directly without a bridge. But most existing devices, and a lot of new budget devices, still aren’t Matter-certified, so Homebridge remains the practical option for a very large slice of what’s actually on the market.

Will my devices still work in their original app if I add them to Homebridge?

Yes - Homebridge plugins generally connect alongside your existing app or account rather than replacing it, so the manufacturer’s app keeps working as normal. The exception is a small number of local-only integrations that take over direct control, which their individual plugin documentation will flag clearly.

Can I run Homebridge on the same Raspberry Pi as Home Assistant?

Yes, and it’s a common setup - many people run Homebridge specifically to expose their existing Home Assistant entities to Apple Home, using the “Homebridge Home Assistant Plugin” alongside a normal Home Assistant install, often on the same machine without issue.