Updated: 2026-10-05 · Applies to: Homebridge 2.x (2.4.0); Matter bridge from 2.2.0

Homebridge

What it is: A lightweight Node.js server on the home network that emulates the HomeKit Accessory Protocol (HAP). Through plugins it brings devices that don't support HomeKit into Apple Home and Siri: vendor clouds, cameras, TVs, thermostats. Homebridge docs It's a community, non-commercial open-source project not affiliated with Apple. From version 2, plugins can also expose devices over Matter, i.e. to Google Home or Alexa too. The current version is 2.4.0 (08/2026). Homebridge docs

Three ways into Apple Home: native HomeKit/Matter, Homebridge and Node-RED with NRCHKB. Own diagram (Synthesis) based on Homebridge docs, Apple Support and NRCHKB.

When Homebridge and when something else

Synthesis based on Homebridge docs, Apple Support and NRCHKB:

Situation	Path
The device supports HomeKit or Matter	add it directly to Apple Home
No HomeKit, a plugin exists, Apple Home automations are enough	Homebridge
The device needs logic, data or a combination of sources	Node-RED + NRCHKB

Expose each device through one path only, otherwise it shows up twice in the Home app.
A plugin is community code running with Homebridge's privileges. Pick maintained plugins with an active repo.

Installation

Officially: Raspberry Pi image, Linux (Debian/Ubuntu, RHEL, Arch), macOS, Windows (Hyper-V), Docker and NAS (Synology, Unraid, QNAP, TrueNAS). Homebridge docs
Umbrel: the homebridge app (image homebridge/homebridge, version 2.4.0), network_mode: host, runs as root, UI on port 8581. Umbrel sources
Synthesis: host networking is needed for HomeKit because discovery uses mDNS on the local network. Protect the UI with a password and don't expose it to the internet.

Adding to Apple Home

In the Home app: Add Accessory and scan the QR code from the Homebridge UI or log. Homebridge docs
Without plugins, Home says "Additional Set-up Required". That's fine; further devices then appear without re-pairing. Homebridge docs
Cameras and most TVs are paired separately as their own accessories. Homebridge docs
Automations and control away from home need a home hub (Apple TV or HomePod). Apple Support

Child bridges

A plugin runs as its own bridge in a separate process (from 1.3.0). Set up in the UI via Child Bridge Config. Homebridge docs

A crashing plugin doesn't take others down; Homebridge restarts it.
A slow plugin doesn't hold up others. When opened, Home queries the state of all accessories of one bridge at once.
Gets around the 150 accessories per bridge limit (a HomeKit limit).
Synthesis: for plugins on cloud APIs (flaky, slow), a child bridge is a sensible default.

mDNS and discovery

Homebridge announces itself on the network via mDNS. The advertiser can be switched: Homebridge docs

Bonjour-HAP: default, legacy and heavier.
Ciao: recommended outside Linux. In containers it may pick the wrong network interface.
Avahi: best on Linux. In Docker it needs D-Bus and the avahi-daemon socket mapped.
systemd-resolved: experimental, for advanced users.
A HomeKit announcement only reaches an iPhone in another VLAN through the mDNS proxy on the gateway, see VLAN.

Matter (Homebridge 2)

Per Homebridge docs:

Enabled per bridge (a matter block in the config), and the plugin must support Matter. Each Matter bridge pairs separately and supports multi-admin, so it can be in Apple Home and Google Home at the same time.
The implementation (matter.js) is not CSA-certified. The controller may warn during pairing; that's expected.
Pairing needs the same IP subnet, working mDNS and IPv6, just like HomeKit. Moving between controllers means re-commissioning.
The Matter bridge (from 2.2.0) runs its own mDNS responder on port 5353. If .local names stop resolving over IPv4, disableIpv4: true in the matter block helps.

Troubleshooting