Yes—But It Is Local IPv6, Not Internet IPv6

Home Assistant Matter needs IPv6 working inside your house. It does not require IPv6 service from your internet provider, and you do not need to expose Home Assistant or a smart device to the internet. Matter uses IPv6 as the local language that its controller—Home Assistant in this case—and devices use to reach one another over Wi-Fi, Ethernet, or Thread.

For a normal Home Assistant OS installation on one home network, the practical setting is simple: go to Settings > System > Network, open the network adapter Home Assistant actually uses, and set IPv6 to Automatic. Home Assistant's current Matter documentation explicitly says there is no requirement for an IPv6 internet connection or a DHCPv6 address server. It also says local IPv6 multicast—one message sent to nearby devices that need it—must reach the Home Assistant host.

Start with Home Assistant, Matter Wi-Fi devices, and the Wi-Fi or Ethernet side of your Thread border router on the same local network. If devices become unavailable after a restart, or pairing stops near the end, do not assume the accessory is broken. A missing local IPv6 route or blocked mDNS—the local discovery traffic devices use to find one another—can create the same symptoms.

The homeowner version: Matter needs an IPv6 hallway inside the house. It does not need an IPv6 driveway to the public internet.

The Three IPv6 Questions People Accidentally Mix Together

The word IPv6 describes several different parts of a network. Matter needs the local parts. That is why a router screen asking about your ISP can send you in the wrong direction.

Network piece Does Matter need it? What it means in the house What to do
IPv6 enabled on Home Assistant Yes Home Assistant can hold local IPv6 addresses, listen for discovery, and reach Matter devices. Use Automatic on the active Home Assistant network adapter unless you manage static routes.
Local IPv6 on Wi-Fi or Ethernet Yes Matter-over-Wi-Fi and Ethernet devices can communicate with the controller on the home LAN. Keep local IPv6 and multicast enabled; test on one flat LAN first.
IPv6 route to a Thread mesh Yes, for Matter over Thread The Thread border router tells the LAN how to reach battery sensors, locks, bulbs, and other Thread devices. Keep the border router reachable from Home Assistant and do not block its route or discovery announcements.
Internet-facing IPv6 from the ISP or WAN No Your internet provider does not have to give the house a public IPv6 range for local Matter control. Do not change WAN settings just to make Matter work.
Router's DHCPv6 address server No Matter can use automatically created local addresses and routes instead of waiting for a DHCPv6 lease. Do not add a DHCPv6 project to a simple home setup.
Port forwarding or an open inbound port No Normal Matter control stays local. Remote access is a separate controller or Home Assistant decision. Do not open router ports for Matter.

What to Set in a Normal Home Assistant OS Setup

This is the safest order for a homeowner with one router, one main LAN, and Home Assistant OS. It keeps the changes reversible and follows the current official documentation.

1. Update the supported Home Assistant path first

Use a current Home Assistant OS release, the official Matter Server app, and a current Companion app. Home Assistant moved the official server to its matter.js-based Matter Server 9 on June 23, 2026, with faster startup and recovery plus new network diagnostics. Updating first rules out issues that newer releases have already fixed before you redesign the network.

2. Set the active Home Assistant adapter to IPv6 Automatic

Open Settings > System > Network. Select the Ethernet or Wi-Fi adapter Home Assistant actually uses. Set IPv6 to Automatic if it is disabled or if you are unsure. Save the setting and let Home Assistant finish applying it. A static IPv6 address is not a reliability upgrade unless you also understand the prefixes and routes that must remain valid.

3. Put the first test on one simple LAN

Keep Home Assistant, the phone used for setup, Wi-Fi Matter devices, and the network side of any Thread border router on the same ordinary home network, or local area network (LAN), while testing. Avoid guest Wi-Fi, client isolation, a separate IoT network, or multicast optimization features for the first device. Once one device works and survives a restart, add complexity deliberately.

4. Check one Matter device before resetting anything

Go to Settings > Matter > Devices and open the device. Current Home Assistant shows its network type and IP addresses. Multiple IPv6 addresses can be normal. An address beginning with fe80:: is a link-local address: it works only on its local network link and is not a public internet address.

5. Match the symptom to the path

If every Thread device fails together and Matter Server reports address is unreachable or repeated timeouts, investigate the IPv6 route between Home Assistant and the Thread border router. If one battery sensor fails while the rest work, check that device's battery, wake procedure, and Thread coverage instead. A shared outage points to infrastructure; a single-device outage usually does not.

Why Matter Works Without IPv6 From Your ISP

The Matter specification separates local reachability from public internet access. On one Wi-Fi or Ethernet network, Matter devices can use automatically created link-local IPv6 addresses. The public Matter 1.4 core specification says that when all nodes are attached to the same Wi-Fi or Ethernet link, link-local addressing is sufficient and no additional IPv6 network infrastructure is required.

Home Assistant's documentation turns that technical rule into a clear setup instruction: no IPv6-enabled internet connection and no DHCPv6 server are required, but IPv6 support must be enabled on Home Assistant and local multicast must travel freely. The Connectivity Standards Alliance also describes Matter as a local connectivity technology. Internet access may still be used for remote control, account services, firmware downloads, voice assistants, or vendor-only features, but it is not the path for normal local Matter commands.

This distinction is also why disabling IPv6 after setup is not a valid privacy strategy. Bluetooth helps the phone perform the nearby handoff during pairing. Normal operation then moves to local IPv6. If you remove that local path, devices can fail immediately or appear to fail only after Home Assistant, a router, or a border router restarts and rebuilds its connections.

Matter over Wi-Fi and Matter over Thread Use IPv6 Differently

Matter over Wi-Fi or Ethernet usually stays on the same local network as Home Assistant. A link-local IPv6 address can be enough when both devices are on that one link. Local mDNS lets the controller discover the device, and encrypted Matter traffic carries the actual commands.

Matter over Thread crosses two local networks: the low-power Thread mesh and the home's Wi-Fi or Ethernet LAN. A Thread border router is the always-on device that connects those two IPv6 networks. Google and the Thread Group document that the border router configures local prefixes and routes, then publishes discovery records on behalf of sleepy Thread devices.

This creates an important troubleshooting clue. A Thread sensor can work perfectly in Apple Home or Google Home while Home Assistant cannot reach it. The radio mesh and device may be healthy; Home Assistant may simply be missing the local IPv6 route to that mesh. A Home Assistant Community report from May 25, 2026 showed exactly that pattern: Apple Home still worked while Home Assistant logged an unreachable Thread prefix.

Do not confuse the jobs: a Thread border router carries encrypted packets between local networks. A Matter controller such as Home Assistant, Apple Home, Google Home, Alexa, or SmartThings owns the device relationship and automations. One box can perform both jobs, but the jobs remain separate.

Use This Troubleshooting Order

Pairing stops at “Checking network connectivity”

  1. Confirm Home Assistant's active adapter is set to IPv6 Automatic.
  2. Update Home Assistant OS, Matter Server, and the Companion app.
  3. Move the phone, Home Assistant, Wi-Fi Matter device, and border router onto the same simple LAN for the test.
  4. If the phone or device is on guest Wi-Fi or an isolated IoT network, retry on the main household network. Do not weaken isolation settings unless you know how to restore them.
  5. Read the Matter Server log before factory-resetting the device.

If this is your exact symptom, use the focused “Checking network connectivity” guide for the phone, Bluetooth, credential, and QR-code checks that come before network surgery.

Several Matter devices become unavailable together

Look for what they share. If all Wi-Fi Matter devices fail, check the LAN, IPv6 setting, mDNS, and Matter Server. If all Thread devices fail but Wi-Fi Matter remains available, check the border router, its LAN connection, and the route to the Thread network's IPv6 address range. Do not delete and rebuild the device's Matter relationship—called its fabric—or create a second Thread network as the first fix. The Matter network map guide explains the current diagnostic view.

Apple Home or Google Home still works

That is useful evidence, not a contradiction. It proves the device and at least one controller path are alive. Check Home Assistant's IPv6 route and local network placement before touching the accessory. If Home Assistant sits on a separate server network while the border router sits elsewhere, a same-network test can strongly point to routing or multicast as the cause; it is not absolute proof. Moving a Home Assistant host can interrupt the app, integrations, and automations, so make a backup and use a maintenance window if you are not already comfortable changing its network.

Only one device is offline

Start with device power, battery, wake behavior, and signal. Do not blame the entire IPv6 setup when twenty devices work and one does not. For Thread devices, a powered Thread router in the same mesh may improve coverage; a Zigbee plug or a router on a different Thread network will not.

The Main Caveat: Separate Networks and Virtual Installations

Matter assumes a friendly residential LAN. A VLAN, or virtual local area network, separates devices into another network segment. Home Assistant's official troubleshooting section warns that VLANs, multicast filtering, and malfunctioning snooping features can break discovery or reachability. Router and switch pages may call those features IGMP snooping or, for IPv6 multicast, MLD snooping. A bad implementation or aggressive “optimization” can hide the announcements Matter needs.

Link-local IPv6 stays on one network segment. It does not cross a VLAN just because ordinary IPv4 routing and ping work. A multi-network design needs a real local IPv6 route, the required multicast discovery path, and firewall rules that allow only the intended traffic. Read the Matter and Thread IoT VLAN guide before separating the controller and border router.

A virtual machine (VM) is a software-hosted computer, while a container is an isolated software package running on a host. Both add another network boundary. Home Assistant OS with the official Matter Server app is the supported path. A VM should use a normal bridged connection to the LAN rather than a private NAT-only network. Running Matter Server as a standalone container is currently unsupported by Home Assistant and requires the host, container, IPv6 routes, and mDNS to be configured correctly.

Avoid copying a random sysctl, router advertisement, or static-route command from a forum without matching it to your installation. Those changes can solve one topology and damage another. First prove the device works on one flat LAN; then document the route you actually need.

Does Enabling IPv6 Expose the Smart Home?

Not when you follow the local setup described here. Matter does not ask you to enable IPv6 on the internet-facing side of the router, often called the WAN, request a public IPv6 prefix, forward a port, or allow unsolicited inbound internet traffic. A local link-local address is not reachable from the public internet.

If your household already uses IPv6 internet service for other reasons, keep the router's stateful firewall and device update practices in place. Public IPv6 security is a separate network-administration decision. It is not a prerequisite for Matter, so there is no reason to change that decision during a basic Home Assistant pairing session.

For locks, alarms, cameras, garage doors, heating and cooling, and safety automations, keep a manual control path available, tell the household before a maintenance window, and restart Home Assistant, the router, and the Thread border router only one at a time. Do not depend on remote access until the local path behaves predictably.

What to Avoid

  • Do not enable port forwarding for Matter. It is unnecessary and creates avoidable exposure.
  • Do not factory-reset every device after a shared outage. Preserve setup codes and check the controller's IPv6 route first.
  • Do not create a second Thread network to fix an IPv6 route. Separate meshes add credentials and coverage confusion.
  • Do not force a static IPv6 address because “static sounds stable.” A correct automatic route is better than a static address on the wrong prefix.
  • Do not assume an IPv4 ping proves Matter networking is healthy. Matter's device traffic still needs the local IPv6 and discovery path.
  • Do not turn an ordinary home into an enterprise network during first setup. Prove the flat-LAN path, then segment with a written plan.

Tara's Take

The right default is boring: Home Assistant OS, current Matter Server, IPv6 set to Automatic, one intentional Thread network, and the controller and border router on the same dependable LAN. That gives Matter the local IPv6 path it expects without making the smart home publicly reachable.

If a household needs VLANs, multiple network interfaces, or containerized services, treat IPv6 routes and mDNS as part of the installation—not as hidden router trivia. Tara's local-first approach documents who owns the Matter fabric, which border router carries Thread, where automations live, and what still works when the internet is down.

FAQ

Does Matter need IPv6 internet service?

No. Home Assistant needs IPv6 working on the local home network, but Matter does not require IPv6 service from your ISP, a DHCPv6 server, an open inbound port, or port forwarding.

Can Matter use IPv4 instead of IPv6?

Matter's operational device traffic uses IPv6. Your phone, Home Assistant web page, and other services may still use IPv4, but an IPv4 address does not replace the local IPv6 path Matter needs.

Should I set Home Assistant IPv6 to Automatic?

Yes for most normal home networks. In Settings > System > Network, open the active adapter and set IPv6 to Automatic. Use a static IPv6 setup only when you already manage the network's IPv6 routes intentionally.

Why do Matter devices work in Apple Home but not Home Assistant?

The device and Thread mesh may be healthy while Home Assistant has lost or cannot receive the local IPv6 route advertised by the Thread border router. Check Home Assistant's local IPv6 setting, network placement, border-router reachability, and Matter Server logs before resetting devices.

Can I disable IPv6 after a Matter device is paired?

No. Bluetooth helps with nearby setup, but normal Matter control continues over local IPv6 on Wi-Fi, Ethernet, or Thread. Disabling IPv6 can make devices unavailable after a restart or route refresh.