How to Pair Smart Home Devices with a Home Automation Hub

What does a smart home hub actually do?

The hub as local controller and protocol translator

A hub acts as a local controller: it sends commands to devices over your home network and receives their status without a round trip to a manufacturer’s server. It also works as a protocol translator. Zigbee devices have no native Matter support, so a hub must bridge them. In the Homey workflow, a Zigbee device is paired with Homey first, and the Matter Bridge app then exposes only the devices you select. Apple Home or Google Home adds the bridged device by scanning the QR code shown in Homey. The device stays paired with Homey and needs no separate pairing with the other ecosystem (Homey (Athom), 2026).

The hub as automation engine

The hub’s second role is the automation engine, which evaluates rules and sends the resulting commands. Where a rule runs determines whether it still works during an internet outage. A rule executed on the hub may keep working without internet if the hub and the devices are local, while a rule executed by a manufacturer’s cloud depends on that service. Check each platform’s documentation to confirm which applies to a given automation.

Hub-based versus cloud-only control

Before you pair: hub, protocol and app checklist

Before starting any Matter pairing, confirm three things: the device’s logos, the phone’s operating system version, and the Wi-Fi network both devices will use. Home Assistant (Open Home Foundation, 2026) lists these as the main prerequisites, and a failed check here is simpler to fix than a failed pairing attempt.

Verify the logos

A device should carry the Matter logo together with a Wi-Fi or Thread logo. A Thread logo alone does not confirm Matter support, so a Thread-only product may not pair through a Matter-based workflow. Check the box and the device label before buying or opening the app, and confirm with a Canadian retailer or the manufacturer that the model is sold and supported in Canada.

Check the phone’s version

Home Assistant (Open Home Foundation, 2026) states these values. Use the recommended version when available, because the minimum is the floor for the protocol, not a guarantee of a smooth setup.

Confirm the network and Bluetooth

• Same 2.4 GHz network: For Wi-Fi Matter devices, the phone must be connected to the same 2.4 GHz network the device will join.
• Bluetooth on: Keep Bluetooth enabled on the phone and stay close to the device during setup.

How do you pair a Matter device with your hub?

Matter commissioning works in four handoffs: the setup code identifies the device, your phone passes network credentials to the device over Bluetooth, the device joins your Wi-Fi or Thread network, and the hub registers it. The Bluetooth step runs between your phone and the device. Home Assistant’s own server Bluetooth adapter is not used for this, according to Home Assistant (Open Home Foundation, 2026). The Bluetooth step runs from your phone.

The Bluetooth credential handoff

Commissioning follows the same sequence on any Matter hub:

Credentials travel over Bluetooth only during stage 3. After stage 4, the device communicates over Wi-Fi or Thread, not Bluetooth.

Scanning the QR code or entering the numeric code

Each Matter device carries a setup code, either as a QR code or as a numeric code printed on the device or packaging.

Photograph the QR or numeric code and store the image. You need it to commission the device again after a factory reset, and the code may not be legible later.

If the camera cannot read the QR code, enter the numeric code instead.

Choosing “Yes. It’s already in use.” for shared devices

A Matter device can be controlled by more than one hub. When a device is already paired with another platform, choose “Yes. It’s already in use.” in Home Assistant, as described by Home Assistant (Open Home Foundation, 2026). To add a device that is already on another platform, the hub asks for a share code from that platform instead of a fresh pairing.

Zigbee devices through Homey

Zigbee devices do not use Matter commissioning directly. Homey (Athom, 2026) describes this workflow:

• Pair the Zigbee device with Homey first.
• Enable the Matter Bridge app, which exposes only the devices you select.
• In Apple Home or Google Home, add a new Matter device and scan the QR code shown in Homey.
• The device stays paired with Homey and needs no extra pairing.

When discovery fails

Home Assistant (Open Home Foundation, 2026) identifies discovery problems as the common cause of commissioning failure. Its documented fixes are:

• Set IPv6 to Automatic or Static on the network.
• Keep Matter devices on the same VLAN as Home Assistant.
• Disable router features that filter multicast traffic.

Pairing Thread devices: border routers explained

Thread devices use a low-power mesh radio that does not connect directly to Wi-Fi, so they need a border router to join your home network and be controlled by your hub. Matter-over-Thread devices need at least one border router nearby during setup. Without one, the setup flow stops and the app shows the error “This device requires a border router.”

Named border routers by platform

According to Home Assistant (Open Home Foundation) (2026), these products act as border routers:

The Home Assistant option lets a Home Assistant install act as the border router, so you do not need an Apple or Google speaker or display for Thread devices.

What the error means

The “requires a border router” message means the phone cannot find a Thread border router that it can reach to join the device to a Thread network. The device itself is not necessarily faulty. Fix it by adding a supported border router from the table or by making an existing one reachable.

Confirming a border router is reachable

• Check placement: Keep the border router within range of the device you are commissioning, not only within range of the phone.
• Check status in the controlling app: Confirm the border router appears as online in the Google Home or Apple Home app, or that the OpenThread Border Router app is running on your Home Assistant system.

Adding Zigbee and Z-Wave devices through a bridge

Zigbee and Z-Wave devices do not use Matter commissioning from a phone. The only workflow verified here is the Zigbee-to-Matter bridge with Homey. For native Zigbee or Z-Wave inclusion, follow the instructions of your hub or coordinator.

Controller roles and inclusion

• Zigbee coordinator: the radio that forms the Zigbee network. Zigbee devices join the coordinator, not the phone or the platform app.
• Z-Wave controller: the equivalent role in a Z-Wave network. It holds the network and adds devices to it.

Adding a device means putting it into the inclusion or pairing mode described in its manufacturer’s instructions, then starting the matching mode on your hub or controller. Follow the instructions for your specific model.

Bridge route versus native Matter pairing

With a bridge, the Zigbee network stays on the bridge hub, and the hub then re-exposes selected devices to other ecosystems.

Tradeoffs

• Single owner: the bridge hub holds the Zigbee network, so those devices answer to that hub.
• Selective exposure: a bridge lets you choose which devices another ecosystem sees, while native Matter pairing exposes each device as it is added.

Can one device work with several platforms?

A Matter device can join more than one controller at the same time, a capability the standard calls multi-admin. Each controller holds its own separate relationship with the device. Non-Matter devices work differently: they stay tied to the vendor’s app or hub, so they cannot be shared in the same way.

What the five-fabric minimum means

A fabric is Matter’s term for one controller’s administrative domain. Each controller that commissions a device creates its own fabric on that device. Check the manufacturer’s specification for a given model before assuming it supports more.

Sharing between Home Assistant and voice assistants

The outcome depends on the order in which the device is added:

To share a Home Assistant device with another platform, use Share device in Home Assistant to generate a code.

Vendor lock-in on non-Matter devices

A device without Matter support has no shared-code mechanism. Its reach depends on what the vendor’s app or hub allows.

To avoid this limit when buying:

• Check the manufacturer’s instructions for any integration option before purchase, since non-Matter integrations vary by vendor.

Fixing pairing failures

Matter pairing fails at one of four stages: the Bluetooth handoff from phone to device, the device’s join to the network, the Thread join through a border router, or discovery by the controller. Matter commissioning sends network credentials from the phone to the device over Bluetooth, and the device then communicates over Wi-Fi or Thread. Identify the failed stage first, then apply the matching fix.

Diagnosing failures by stage

Bluetooth and range issues

Bluetooth problems can come from the phone or from the distance to the device. If the flow stalls at the handoff, turn Bluetooth off and on again on the phone, then restart the attempt from the beginning rather than resuming a half-finished pairing.

Network and discovery failures

A device that completes the handoff but never appears in the controller points to discovery, not pairing.

Thread stage failures

Do not treat the device itself as the cause until the border router is confirmed.

Recovering after a factory reset

A reset removes the device’s stored pairing, so the device must be commissioned again. Re-commissioning requires the setup code, which is the QR code or numeric code printed on the device.

Use these steps for recovery:

• Device still paired to another platform: In Home Assistant, choose “Yes. It’s already in use.” when prompted, so the device is added as an already-used device.

Next steps: rooms, names and first automations

Once a device is paired, it appears in your controller but is not yet usable in context. Assigning each device to a room, giving it a consistent name, and building one simple automation turns a list of paired devices into a working setup. The process takes the same steps in most platforms, including Home Assistant, Apple Home and Google Home.

Assign each device to a room

Room assignment determines where a device appears in the app, which voice commands target it by default, and which devices a room-level control affects. Assign rooms immediately after pairing, before you create automations, because automations and scenes are easier to build when devices are already grouped by location.

If a device covers more than one space, such as a hallway sensor that also sees a stairwell, assign it to the room where its trigger matters most and name it to reflect its actual coverage.

Use a consistent naming convention

Names are the identifiers you will type into voice commands, automation editors and scene definitions. A repeatable pattern prevents duplicate names and makes devices easy to find in long lists.

Combine the elements in the same order for every device, for example “Kitchen Light Ceiling” or “Hall Motion Stairs”. Keep names short and avoid special characters, which some voice assistants handle inconsistently.

Build a first motion-triggered automation

Start with one sensor and one light, since this exposes problems such as a wrong trigger or a slow response without interference from other logic.

1. Open the automation editor. In Home Assistant, this is Settings, then Automations & scenes. In Apple Home or Google Home, use the Automations or Routines section.
2. Set the trigger to the motion sensor changing to its active state.
3. Set the action to turn on the light in the same room.
4. Add a second trigger or condition that turns the light off after a period with no motion. Choose the delay that suits the room. A hallway usually needs a shorter delay than a bedroom.
5. Save, then walk through the detection area and confirm that the light responds and switches off as expected.

Test the automation at different times of day before you add conditions based on brightness or time, so you can confirm the basic trigger works first.

Group devices into scenes and routines

A scene stores a set of device states, such as “Evening: living room lights at 40% and plug on”, and applies them together when activated. Scenes are manual or called by another trigger, and they do not decide when to run.

A routine or automation is a sequence that runs on a trigger, such as a time of day, a sensor state or a device action. Use scenes when you want one tap or voice command to set several devices at once, and routines when the sequence should start without you.

Group devices into a scene only after they have clean names and room assignments, because a scene refers to devices by these identifiers. Limit each scene to devices that serve one purpose, so that changing one scene does not affect unrelated lights or plugs.

Related reading

• Reset a Zigbee Device Before Pairing Again: Step-by-Step
• Smart Devices Offline After Power Outage? Causes and Fixes
• Matter-Compatible Hub for Apple HomeKit Setup: Which Device?