How to Set Up Matter in Home Assistant in 2026

Before you scan the QR code on a Matter device, make sure three things are already true: Home Assistant can run the Matter integration and Matter Server, IPv6 is enabled on the Home Assistant network, and your phone is ready to do the commissioning. If the device is Matter-over-Thread, add a fourth requirement: a real Thread border router must already be present.

That is the practical core of setting up Matter in Home Assistant in 2026. Matter itself is no longer the unusual path inside Home Assistant, but the setup still fails in boring places: a disabled IPv6 toggle, an Android permission that looks unrelated, or a Thread device being treated like a Wi-Fi bulb.

The phone requirement is not optional theater. Matter commissioning uses the phone as the device that scans the setup code, talks to the new device over Bluetooth, and hands it the network details it needs. Home Assistant’s Matter documentation lists Android 8.1+ or iOS 16+, Bluetooth, and the latest Companion app as commissioning requirements; Android also needs Location permission because Android restricts background access to Wi-Fi SSID information.[1]

The IPv6 requirement is the one that catches experienced users because it sounds like an internet-provider issue. It is not. Matter uses local IPv6 communication, including link-local IPv6, so Home Assistant needs IPv6 enabled on the local network even when the ISP does not hand out public IPv6 addresses.[1]

Why Matter setup is smoother in 2026

Matter Server 9.0 is the reason setup can be more procedural and less apologetic than earlier Matter walkthroughs. Home Assistant released the stable upgrade on June 23, 2026 as a drop-in replacement using matter.js, based on Matter 1.5.1. Existing data migrates automatically on first start, and the release notes call out faster start-up, better OTA reliability, and native network visualization.[2]

That does not make every Matter device good, and it does not erase Thread credential weirdness between ecosystems. It does mean the Home Assistant side of the stack is less likely to be the fragile part than it was. If you are setting this up in July 2026, the new server is not just a background dependency; it changes the amount of friction you should expect from restarts, device updates, and seeing what the Matter network thinks is connected.

Matter is also no longer a niche integration among people who opt in to Home Assistant analytics. As of mid-2026, the Matter integration appears in 38.8% of active installations that report analytics, making it the 12th most-used integration in that dataset.[3] That figure should not be stretched into universal adoption, because analytics is opt-in, but it is enough to say this is now a mainstream Home Assistant setup path.

The three layers you are actually setting up

Matter vocabulary gets muddy because people use “hub” to mean several different things. In a Home Assistant setup, separate the layers by what they do during setup, not by what the box is called on the product page. If that language is already annoying, the deeper explainer on the three meanings of a Home Assistant Matter hub is worth reading before buying hardware.

The Matter integration is the Home Assistant-facing piece. It is what you add from Settings > Devices & services, and it is what makes the finished device appear as entities you can automate. It is not, by itself, a radio and it is not a Thread border router.

Matter Server is the controller service behind the integration. On Home Assistant OS, that normally means the Matter Server add-on. This is the piece that owns the Matter fabric from Home Assistant’s side. A fabric is the trusted Matter network membership: the controller, credentials, and devices that are allowed to talk to each other. You do not need to love the term, but you do need to know that sharing a device with Apple Home or Google Home later means adding it to another fabric, not “pairing it again from scratch” in the old Bluetooth sense.

The Thread border router is a different job. Thread is a low-power mesh network used by many battery sensors, buttons, locks, and some bulbs. A Thread border router connects that mesh to your normal IP network. Home Assistant can provide this with supported hardware such as Home Assistant Yellow or a ZBT radio running OTBR, but Apple, Google, IKEA, and Aqara hardware can also be the border router if it is already reliable in your home.[4][5]

For hardware selection, do not buy a USB stick just because a device box says Matter. Matter-over-Wi-Fi and Matter-over-Ethernet devices do not need a Thread radio. Matter-over-Thread devices do. If you are still choosing the controller and radio pieces, compare the current options in Best Matter Hubs and Hardware for Home Assistant in 2026 and the dongle-specific guide, Choose the Right Home Assistant Matter Dongle for Your Setup.

Pick the right setup path before the device starts blinking

A Matter QR code does not tell you everything you need to know. The first split is the transport: Matter-over-Wi-Fi or Ethernet versus Matter-over-Thread. The second split is ownership: fresh commissioning into Home Assistant versus sharing a device that already belongs to Apple Home, Google Home, or another controller.

If you are new to the protocol distinctions, keep the short version close: Matter is the application layer, Thread is one possible network underneath it. Zigbee and Z-Wave devices do not become Matter devices just because Home Assistant can control them, although bridges can expose some non-Matter devices through Matter in specific cases. The broader protocol comparison is covered in Home Automation Hub Protocols Explained.

Step-by-step: commission a new Matter device into Home Assistant

1. Prepare Home Assistant and Matter Server

Update Home Assistant first, especially if this installation has not been touched since before the June 2026 Matter Server 9.0 release. On Home Assistant OS, open Settings > Add-ons and install or update the Matter Server add-on. Then go to Settings > Devices & services and add the Matter integration if it is not already present.

If Matter Server already exists, let it start cleanly before commissioning. Matter Server 9.0 migrates existing data automatically on first start, so the right move is patience, not deleting old data because the start-up takes a moment after the upgrade.[2]

2. Verify local network and IPv6

In Home Assistant, open Settings > System > Network and confirm IPv6 is enabled. Do this even if your home internet plan is IPv4-only. Matter’s local behavior depends on IPv6 on the LAN, and disabling it can make commissioning or later control look randomly broken.[1]

Also check the ordinary network problems before blaming Matter. The phone should be on the same home network you expect Home Assistant and the device to use. Avoid guest Wi-Fi, client isolation, and VLAN rules that block local discovery unless you have deliberately designed the network to pass the required traffic. Matter is local-first, but local-first still needs the local network to allow devices to see each other.

3. Prepare the Companion app

Install or update the Home Assistant Companion app on the phone you will use for commissioning. Enable Bluetooth. On Android, open the app permission settings and set Location to Allow all the time before starting. The permission name is misleading in this context; the practical issue is that Android gates Wi-Fi SSID access behind location permissions, and Matter commissioning needs that network information.[1]

Use the phone that is actually signed in to your Home Assistant instance and can reach it locally. Commissioning is not the moment to discover that the app is only configured for remote access through a URL that is currently failing.

4. If it is a Thread device, confirm the border router

For a Matter-over-Thread device, make sure a Thread border router is already online. Home Assistant’s Thread documentation describes Thread border routers as the bridge between Thread networks and the rest of the IP network.[4] Common practical options include Home Assistant Yellow or supported ZBT hardware running OTBR, Apple TV 4K, HomePod, Google Nest Hub, IKEA Dirigera, and Aqara M100, depending on what you already own and how you want credentials managed.[5]

This is where purism wastes time. If an Apple TV 4K or Nest Hub is already the most stable Thread border router in the house, use the stable thing. If you want Home Assistant to own the Thread infrastructure, use supported Home Assistant hardware and place the radio sensibly. The same placement instincts from Zigbee apply: do not bury a USB radio behind a noisy server and then act surprised when the mesh behaves badly. The placement tradeoffs in USB Zigbee Dongle vs PoE Coordinator for Home Assistant are not identical to Thread, but the RF lesson carries over.

5. Put the device in pairing mode and commission from the phone

Now put the Matter device into pairing mode. Open the Home Assistant Companion app, start adding a Matter device, and scan the QR code or enter the setup code. The phone talks to the new device, passes the required network or Thread information, and hands the result back to Home Assistant through the Matter Server.

For Wi-Fi Matter devices, the commissioning flow usually includes handing over Wi-Fi credentials. For Ethernet Matter devices, the device is already on the network, so the flow is more about proving trust and adding it to the fabric. For Thread devices, the phone and border router need to agree on Thread credentials. That last part is where Apple, Google, and Home Assistant setups can still feel inconsistent in the real world, especially when credentials have lived in one ecosystem for a while.

If the timer is running down and nothing happens, stop changing five things at once. Check Bluetooth, app permissions, phone network, IPv6, and the border router in that order. Factory reset should be a later move, not the first reflex.

6. Verify the device inside Home Assistant

After commissioning succeeds, open Settings > Devices & services and inspect the new Matter device. Confirm the expected entities appear, name the device clearly, assign it to the right area, and test basic control from Home Assistant before building automations around it.

Expect Matter to expose the common device functions first. A bulb may expose on, off, brightness, and color temperature, while a manufacturer app may still hold specialty effects or vendor-specific settings. That feature stripping is not imaginary; it is one of the recurring frustrations in 2026 Matter criticism and community reports.[6]

7. Share to another ecosystem only after Home Assistant works

Once the device works in Home Assistant, decide whether it also needs to appear in Apple Home, Google Home, Alexa, or a vendor app. Matter supports multi-fabric setups, which means one device can belong to more than one controller environment. In practical terms, one controller generates a sharing code and the next controller uses that code to join the same device.

Do not use multi-fabric sharing as a troubleshooting shortcut. If the device is unstable in Home Assistant, adding another ecosystem usually gives you two confusing views of the same problem. Get one fabric working, then share.

What to expect after setup

A clean Matter setup in Home Assistant should feel local and ordinary: devices respond without a cloud round trip, entities can be used in automations, and the Matter Server keeps the controller side in one place. Matter Server 9.0’s faster start-up, OTA reliability work, and network visualization should reduce some of the old guessing around whether the server, device, or network is the weak link.[2]

There are still limits worth knowing before you replace a working setup. Some Matter lights still show the “popcorn effect,” where several lights turn on one after another instead of together. Some devices expose only their basic Matter features and leave advanced options in the manufacturer app. Camera and doorbell support has improved in the Matter 1.5.1 era on the Home Assistant side, but ecosystem support across Apple Home, Google Home, and Alexa can lag behind the specification.[2][6]

Thread is the other place to keep expectations grounded. Thread 1.4 credential-sharing improvements are promising, but mixed Apple, Google, and Home Assistant environments can still disagree about which Thread network a device should join or how credentials are shared. For a first Matter setup, fewer border routers and a clear owner for the Thread network usually makes life easier than every ecosystem trying to be helpful at once.

When setup fails, diagnose the layer

Matter failures are easier to diagnose when you place them in the layer where they occur. If the Matter integration will not connect, look at Home Assistant and Matter Server. If commissioning never starts, look at the phone, Bluetooth, permissions, and network discovery. If only Thread devices fail, stop debugging Wi-Fi and inspect the Thread border router. If the device pairs but exposes fewer controls than expected, check whether those controls are actually part of its Matter implementation.

If you are already stuck, use Home Assistant Matter Hub Not Working? Diagnose the Real Cause rather than repeating the pairing process until the device locks you out or the QR code starts to feel personal.

Should you buy more Matter devices for Home Assistant?

For new purchases in 2026, Matter is a reasonable default to consider, not an automatic upgrade over every stable Zigbee, Z-Wave, or native integration you already have. Matter-over-Wi-Fi plugs and bulbs can be simple if your Wi-Fi is solid. Matter-over-Thread sensors and buttons can be excellent when the Thread border router situation is clean. Bridges and cameras need closer inspection because support can differ sharply between the standard, Home Assistant, and the big consumer ecosystems.

If you are still deciding what to buy, start with Which Matter Devices Are Worth Buying in 2026?. For the bigger adoption question, Matter in 2026: An Honest Status Review is the better place to weigh whether Matter deserves space in a setup that already works.

For the setup itself, the answer is narrower and more useful: Matter in Home Assistant is a realistic 2026 path with Matter Server 9.0, but it is only straightforward when IPv6, the Companion app, and Thread infrastructure are ready before commissioning begins.

References

1. Matter, Home Assistant
2. The Matter upgrade you've been waiting for, Home Assistant, June 23, 2026
3. Home Assistant Analytics, Home Assistant
4. Thread, Home Assistant
5. Best Thread Border Routers for Home Assistant, SmartHomeScene
6. Why Matter Still Sucks in 2026, Terry White