Apple Home (HomeKit)
What it is: Apple's Home app and HomeKit platform for controlling a smart home from iPhone, iPad, Mac, Apple Watch and via Siri. At its heart is the home hub (Apple TV or HomePod), which enables automations, control away from home and sharing with other people.1 Devices get into Apple Home natively (HomeKit, Matter) or through bridges such as Homebridge and Node-RED with NRCHKB.2,3
The home hub and three ways for devices into Apple Home. Own diagram (Synthesis) based on Apple Support1, Homebridge docs2 and3.
Home hub
Per Apple Support1:
- Enables control away from home, sharing control with other people and automations.
- A home hub can be an Apple TV, HomePod or HomePod mini. iPad can't be a home hub on the latest version of Apple Home.
- With several hubs, one is active and the others are standby. A preferred hub can be chosen manually (turn off automatic selection).
- Synthesis: for a smart home, always plan a home hub. Without it, neither automations nor remote access work. A wired Apple TV is more stable than one on Wi-Fi.
Apple Home update (new architecture)
- Improves accessory performance and adds guest access, robot vacuums and Activity History.1
- Requires iOS / iPadOS 16.2, macOS 13.1, tvOS 16.2, watchOS 9.2 or later. Devices on older software lose access to the updated home until they're updated.1
Matter and Thread in Apple Home
Contradiction
1 (09/2025) says a home hub is required to add Matter accessories.1 (05/2026) says that with iOS 18 or later Matter can be added even without a hub, but recommends one. The newer article applies; a hub is needed for automations anyway.
- Thread devices need a Thread-enabled home hub: Apple TV 4K (for the 3rd generation, the Wi-Fi + Ethernet model), HomePod 2nd generation or HomePod mini, or a compatible third-party border router.1
- A Matter device paired in another app can also be added to Home (multi-admin). Add by scanning the code or holding the iPhone near.1
- Matter needs local IPv6 and mDNS. The home hub, Matter devices and border routers therefore belong in the same VLAN (see VLAN).4
Ways for devices into Apple Home
Synthesis based on Homebridge docs2, NRCHKB3 and1:
| Path | For what | Pros | Cons |
|---|---|---|---|
| Native (HomeKit, Matter) | devices with a HomeKit or Matter label | no extra server, vendor support | certified devices only |
| Homebridge | devices without HomeKit that have a plugin | thousands of plugins, simple | logic only in Apple Home, plugin = third-party code |
| Node-RED + NRCHKB | anything Node-RED can control (HA, Zigbee, MQTT, SQL) | full logic and data in the flow | more work, dependency on NRCHKB (see Node-RED) |
- Expose each device through one path only, otherwise it appears twice in Home.
- Homebridge and NRCHKB are bridges for HomeKit. For Google Home or Alexa, Homebridge 2 can also do Matter.2
Network
- HomeKit bridges and the home hub announce themselves via mDNS. Matter pairing (including Homebridge's) needs the same IP subnet, working mDNS and IPv6.2
- With VLANs: phones in a network other than IoT need the mDNS proxy (HomeKit
_hap._tcpservices are in Auto mode) and a firewall rule from the main network to IoT.5 Procedure in VLAN. - Siri is a cloud service, and device changes reach it via iCloud with a delay.2
Related
Sources
- Apple Support: home hub, Matter in the Home app, Apple Home update โ โ home hub, Apple Home update, Matter and Thread.
- Homebridge: README and wiki (child bridges, mDNS advertiser, Matter) โ โ HAP, pairing, mDNS, Matter in Homebridge 2.
- node-red-contrib-homekit-bridged (NRCHKB): README, npm, issues โ โ HomeKit nodes for Node-RED.
- Home Assistant: Thread and Matter integrations โ โ Matter, IPv6 and VLANs.
- UniFi Help Center: VLANs, ports, mDNS proxy, zone-based firewall, isolation, IGMP โ โ mDNS proxy and firewall in UniFi.
Intellihome