Back to Home Assistant Guides
Home Assistant

How Do I Set Up Matter in Home Assistant?

Home Assistant GuideSmart Hubs
hard difficulty 30 min 345 views 10 found helpful Where this fix applies: Global Updated
This guide applies to: Home Assistant Home Assistant (All Models)
At a glance — most common causes
  • Matter Server add-on not installed/healthy
  • Commissioning done off the local network
  • No Thread border router for Thread devices
30 min13 solutions coveredhard level

Expert Review & Technical Scope

DeviceHome Assistant Home Assistant
Model CoverageAll Models
Fix Time30 min
DifficultyHard
Required ToolsEthernet cable
Network / ProtocolMatter, Thread

Problem Description

You're setting up Matter in Home Assistant and a device won't commission or comes up unavailable. HA supports Matter via the Matter Server add-on and needs a compatible commissioning path (often the Companion app on the same network), plus Thread devices need a border router, so setup issues cluster around those pieces.

Why This Happens in Real Homes

Matter in Home Assistant relies on a few moving parts: the Matter Server add-on running healthy, commissioning done on your local network (usually by scanning the code in the Companion app), and — for Thread devices — a working Thread border router. Missing one is why devices won't commission or go unavailable.

Start by confirming the Matter Server add-on is installed and healthy and that HA core is current, then commission the device on the same network with the app. Matter also expects IPv6 on your LAN; for Thread gear, make sure a border router is present, and factory-reset any device already bound to another ecosystem.

Symptoms

  • Matter device will not commission
  • Device unavailable after adding
  • Pairing code rejected
  • Thread device not joining
  • Commissioning times out
  • Device drops offline
  • Matter Server errors
  • Works then disconnects

Recognize these? Here's what usually causes it.

Common Causes

  • Matter Server add-on not installed/healthy
  • Commissioning done off the local network
  • No Thread border router for Thread devices
  • Device already commissioned to another fabric
  • 2.4GHz interference
  • IPv6 not enabled on the network
  • HA core out of date
  • Companion app needed for commissioning

Most fixes happen in the first 3 steps.

Warning

Do not factory reset your hub unless absolutely necessary as this removes all paired devices, automations, and settings. You will need to re-pair every single device from scratch which can take hours for a large setup. Always try a simple restart first.

Tools & Requirements

Ethernet cable
Recommended Tools for Home Assistant

These tools will help you complete this fix.

As an Amazon Associate we earn from qualifying purchases.

Step-by-Step Solution

1

Verify Home Assistant version and Matter add-on readiness

Update Home Assistant core and confirm Matter integration/add-on is installed and healthy, because outdated builds frequently fail commissioning workflows.

2

Confirm Thread border router and network prerequisites

Check whether your target devices require Thread and verify border router availability, since missing Thread infrastructure blocks many Matter device joins.

3

Prepare device in fresh commissioning mode

Reset target device and clear previous fabric bindings before adding, because devices already bound to another fabric commonly reject new commissioning attempts.

4

Complete pairing with QR/manual code close-range

Use official setup code while keeping controller proximity stable, because BLE handoff reliability drops quickly when distance or interference is high.

5

Validate entity control and persistence after restart

Test entity commands, automation triggers, and post-restart state retention so you can confirm setup is production-stable rather than temporarily paired.

Quick Solutions

Install and confirm the Matter Server add-on is healthy
Commission on the same local network (use the app)
Provide a Thread border router for Thread devices
Factory-reset a device bound to another fabric
Reduce 2.4GHz interference
Enable IPv6 on your network
Update HA core
Use the HA Companion app to scan the pairing code

Still having issues? This is usually the deeper cause below.

If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.

Pro Tip

Place your hub in a central location in your home, elevated off the floor and away from your WiFi router by at least 3 feet. This provides the best Zigbee and Z-Wave signal coverage to all corners of your house.

Real-World Insight

Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.

What Usually Goes Wrong
  • Matter Server add-on not installed/healthy
  • Commissioning done off the local network
  • No Thread border router for Thread devices
  • Device already commissioned to another fabric
  • 2.4GHz interference

Official Manufacturer Manual

Home Assistant provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Home Assistant.

View Home Assistant Online Manual

Source: home-assistant.io

Need More Help? Home Assistant Support

Note: The contact information below connects you directly to Home Assistant's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.