Short Answer: Usually Yes, but the Matter Server App Must Be in the Backup

A Home Assistant backup can normally restore Matter devices without re-pairing them when it includes both Home Assistant settings and the Matter Server app data. The Matter Server is Home Assistant's local Matter controller. Its saved data holds the secure controller identity, fabric credentials, and paired-device records that let Home Assistant prove it is trusted by the accessories. A Matter fabric is the private trust relationship between one controller and its devices.

Home Assistant's official backup instructions let a restore include Home Assistant plus selected apps, while the official Matter Server app keeps its controller state in persistent app storage. Put those two facts together and a complete restore should preserve the Home Assistant fabric. This is a well-supported recovery path, but Home Assistant does not publish an unconditional promise that every Matter network will return automatically.

The other half is reachability. Matter uses IPv6, the local network addressing it needs, and mDNS, the local “I'm here” announcements that help controllers find devices. Those messages travel over Wi-Fi, Ethernet, or Thread. If the fabric restores but the Thread border router, radio, Wi-Fi, IPv6, or local discovery path is broken, the accessories can still appear in Home Assistant as unavailable. That is a network problem until proven otherwise, not a reason to scan every QR code again.

The practical rule: preserve the controller data first, preserve the network path second, and re-pair only after both have been checked.

Why a Normal-Looking Backup Can Still Miss the Important Part

Home Assistant shows a Matter accessory as a device with one or more entities—the individual light, switch, sensor, lock, or control records used on dashboards and in automations. Those records are useful, but they are not the secure trust relationship that lets Home Assistant control the hardware.

The secure relationship lives in Matter Server. Home Assistant's developer documentation says an app's /data directory is persistent storage, and the Matter Server starts with its storage path set to that location. The current matter.js server documentation describes the same mounted data directory as the home of Matter fabric information. If a restore brings back only Home Assistant settings and leaves out that app data, Home Assistant may remember names and automations while the new Matter controller lacks the keys the accessories trust.

Current support threads show both sides. A May 24, 2026 Raspberry Pi rebuild left Matter devices unavailable after the app portion did not restore as expected. By contrast, users in a June 23 Matter Server 9 discussion reported restoring a pre-update backup and recovering their paired Matter devices. Those reports are not a guarantee. They are a useful warning to inspect what the backup contains instead of treating every .tar file as identical.

The Five Pieces You Are Actually Protecting

Piece Where it lives What to preserve If it is missing
Home Assistant setup
Entities, integration entry, names, areas, automations		 Home Assistant settings and configuration Include Home Assistant in the backup and restore selection. The dashboard and automation records may be incomplete even if Matter Server still knows the devices.
Matter controller and fabric
Controller identity, trusted keys, paired-device records		 Matter Server app persistent data Include and restore the Matter Server app. Confirm it appears in the backup details. The new controller cannot authenticate to devices that trusted the old fabric.
Home Assistant-owned Thread network
Thread credentials and border-router state		 Home Assistant Thread settings and OpenThread Border Router app data Include the OpenThread Border Router app and reconnect or officially migrate the Thread radio. Matter may restore while Thread devices remain unreachable on their old mesh.
Apple, Google, Amazon, or vendor Thread network The external ecosystem, its border routers, and its phone/account credential flow Keep those hubs powered, enrolled, and unreset. Home Assistant cannot clone their platform state in its own backup. Home Assistant may retain its Matter fabric but lose the route to Thread devices.
Physical accessory membership and setup code The accessory itself and its printed label or documentation Do not factory-reset it during the move. Save a photo of the Matter QR and numeric code somewhere private. A reset removes network and fabric membership; the code is then needed to commission again.

Before You Move Hardware or Rebuild Home Assistant

  1. Check that Matter works now. Open Settings > Matter and note the device count. Test one mains-powered device and one battery device so the backup represents a known-good state.
  2. Identify who owns Thread. In Settings > Devices & services > Thread, note whether the preferred network belongs to Home Assistant, Apple, Google, or another platform. Thread is the low-power mesh that some Matter accessories use; the border router connects that mesh to the home LAN.
  3. Create a manual backup with the right parts. Include Home Assistant and Matter Server. Include OpenThread Border Router when Home Assistant runs the Thread network. Selecting everything is the safest migration default when storage allows.
  4. Open the backup details. Verify that the named apps are actually present. A backup policy that excludes large apps or uses a partial selection can quietly omit what this recovery needs.
  5. Download the backup off the host. Keep a second copy on a computer, NAS, or another backup location. A backup stored only on the failed SSD is not a recovery plan.
  6. Save the matching emergency kit. Home Assistant's emergency-kit documentation is unambiguous: without the correct encryption key, an encrypted backup cannot be restored after the old instance is gone.
  7. Save the Matter setup codes. The Matter documentation recommends photographing the QR or numeric setup code when it is only in the paperwork. Store those images privately because they are onboarding credentials.
  8. Change one layer at a time. Avoid changing the Home Assistant host, router, Wi-Fi name, rules between separated IoT networks (often called VLANs), Thread border router, and radio on the same day. A calm migration has far fewer possible causes.

The Safe Restore Order

  1. Shut down the old Home Assistant host. Do not leave the original and restored Matter Server running on the home network together. A restored copy carries the same controller identity, so two active copies can compete to talk to the same devices.
  2. Restore during onboarding. Install Home Assistant on the replacement hardware, choose Upload backup or Home Assistant Cloud on the welcome screen, and select all relevant parts and apps. The official restore flow reinstalls Home Assistant Core and the selected apps.
  3. Reconnect the radio carefully. If Home Assistant owns Thread, attach the same adapter or follow the official supported adapter-migration procedure. Confirm the correct adapter and official radio settings before forming any new Thread network.
  4. Restore boring local networking. Keep Home Assistant, Matter-over-Wi-Fi devices, and Thread border routers on a home network where IPv6 and the mDNS local-discovery messages can travel. Copying the old IPv4 address is not a substitute for this.
  5. Let Matter Server finish starting. Matter Server 9, released on June 23, 2026, automatically migrates older server data and performs a full check of every device on its first start. The official migration FAQ says this can take time and that the log shows progress.
  6. Check the paired-device list before dashboard entities. Open Settings > Apps > Matter Server > Open Web UI and inspect Nodes, Matter Server's list of paired devices. If the expected nodes exist there, the fabric data probably survived. If Home Assistant cards are still gray, allow reconnects and troubleshoot the integration or network path.
  7. Wake sleepy devices. Battery sensors may take time to check in. Use the product's normal wake action or a safe power cycle for one affected device. Do not reset a batch.
  8. Test the house, not just the page. Test one Wi-Fi Matter accessory, one Thread Matter accessory, notifications, and any critical automation. Keep manual control available for locks, garage doors, HVAC, alarms, leak shutoffs, and exterior access.

If the Devices Are Still Unavailable

What you see Most likely meaning Try before re-pairing
Matter Server app is missing The app was not selected, could not be restored on this installation, or has not finished reinstalling. Open the known-good backup and restore the Matter Server app portion. Then verify version compatibility and start the app.
Matter Server opens, but the expected nodes are absent The controller's persistent app data may not have restored. Stop. Restore the Matter Server app data from the known-good backup before deleting integrations or commissioning replacements.
Nodes exist, but all are offline The fabric probably survived, while IPv6, mDNS, firewall, Wi-Fi, or Thread routing is broken. Check the main network connection, local IPv6, local-discovery traffic, rules between separated networks, border-router power, Thread network identity, and radio selection.
Wi-Fi Matter works; Thread Matter does not Matter Server is alive, but the Thread route or dataset is wrong. Confirm the original Thread network still appears, its border router is reachable, and Home Assistant's OpenThread Border Router app and radio were restored.
Devices still work in Apple Home, Google Home, Alexa, or SmartThings The accessory and transport still work; only Home Assistant's controller relationship or route is affected. Repair the Home Assistant restore first. If its fabric is truly gone, use that working platform to create a fresh Matter sharing code and add the device back without a factory reset.
Device was added after the backup date The restored Matter Server never knew that later node. Share it from another surviving controller or commission it again with the saved setup code.

Home Assistant's Matter documentation says random unavailability is commonly caused by local IPv6 or mDNS traffic not moving freely. The visible symptom is the same whether the cause is a restore, a firewall change, an access-point setting, or a Thread border router. Diagnose the path before erasing the trust relationship.

A Home Assistant Backup Does Not Contain Every Thread Network in the House

When Home Assistant owns Thread

Home Assistant's Thread documentation says the Home Assistant-managed network is not stored only on the USB adapter. That is good news for radio replacement, but it does not make the OpenThread Border Router app data optional. Include the app, restore the Thread settings, and use the documented adapter migration when hardware changes.

If the Matter fabric returns but Home Assistant creates a brand-new Thread network, old Thread accessories remain on the original mesh. A matching network name is not enough; the encrypted Thread credentials—technically called the operational dataset—must match.

When Apple, Google, or another platform owns Thread

That external border router and its ecosystem remain outside the Home Assistant archive. Keep the HomePod, Apple TV, Nest hub, Google router, Echo, eero, SmartThings hub, or vendor border router powered and enrolled while Home Assistant is restored. The restored Home Assistant fabric can use that route when local IPv6 connectivity works, but the backup does not rebuild the other platform.

This is also why Matter multi-admin is useful but not a Thread backup. Multi-admin lets one accessory trust several Matter controllers. If Apple Home still controls the device after Home Assistant loses its fabric, Apple can usually open a temporary sharing window so Home Assistant can join again. It does not recreate a lost Thread mesh by itself.

Home Assistant Container Needs a Separate Matter Server Backup

The supported homeowner path is the official Matter Server app on Home Assistant OS. Home Assistant's Matter page describes custom Matter Server containers as an advanced, unsupported-at-your-own-risk setup. In that arrangement, the Matter fabric lives in the external server's mounted storage, not inside the Home Assistant Core container.

The current matter.js Docker documentation uses a mounted /data path for fabric information. Back up that volume with the same care as Home Assistant's configuration, and restore the exact volume before starting the new container. A normal Home Assistant backup cannot reach an unrelated Docker volume unless you deliberately placed and protected it within the backup plan.

When Re-Pairing Is Genuinely the Right Answer

  • The Matter Server app storage was omitted, corrupted, or lost and no usable backup remains.
  • The accessory was factory-reset or the Home Assistant fabric was removed from it.
  • The device joined Home Assistant after the backup was made.
  • A Home Assistant-owned Thread dataset was lost and no compatible copy or surviving border router can restore it.
  • An external Thread platform was reset and its network cannot be recovered.
  • A Matter bridge was reset and now presents a new Matter identity.
  • The fabric, app data, local IPv6, mDNS, Wi-Fi, radio, and Thread path have all been checked and the node still cannot be recovered.

If another Matter controller still works, use a fresh multi-admin sharing code before factory-resetting the accessory. That often avoids physical access to a buried plug or ceiling sensor. Home Assistant may still create new device or entity mappings, so inspect automations afterward instead of assuming their old targets followed automatically.

Make the Backup Usable, Not Merely Green

Home Assistant recommends a 3-2-1 pattern: three copies, two kinds of storage, and one off-site. Automatic backups are useful, but add a manual backup immediately before a Matter Server, radio, or hardware migration. Open its details and verify the apps rather than trusting the timestamp alone.

Home Assistant Cloud is an optional off-site location, not a requirement for local Matter control. Whether the backup sits in Home Assistant Cloud, on a NAS, or on another provider, keep the matching encryption key outside the Home Assistant machine. Since Home Assistant 2026.4, new backups use Home Assistant's newer audited encryption format; older backups remain readable, but each encrypted backup still needs the correct key.

Finally, record who owns Thread, which radio Home Assistant uses, where the Matter setup codes are stored, and which other ecosystems are Matter administrators. That one-page household note is often more valuable during a failed restore than a folder full of screenshots with no explanation.

Tara's Recommendation

For a homeowner-ready installation, treat Matter Server and Thread as first-class recovery assets. Schedule encrypted off-device backups, include Matter Server every time, include the OpenThread Border Router app when Home Assistant owns Thread, and take a fresh manual backup before any major update or move. Then test the recovery plan while the old hardware and setup codes still exist.

During a migration, keep the scope boring: one new host, the same working LAN, the same Thread owner, and the old system powered off but untouched. Restore, wait, inspect Matter Server nodes, and test the house. A reset is a last step, not a troubleshooting opener.

If you want Tara to package the recovery plan with the smart-home design, the configurator can capture the hub, radio, local-control path, backup destination, and handoff requirements before the hardware is installed.

FAQ

Will a full Home Assistant backup restore Matter devices without re-pairing?

Usually, when it includes both Home Assistant settings and the Matter Server app data, and the restored system can still reach the same Wi-Fi or Thread network. It is not an unconditional guarantee, so verify the app, nodes, and network before resetting devices.

What should I include in a Home Assistant backup for Matter?

Include Home Assistant settings and the Matter Server app. If Home Assistant runs your Thread network, include the OpenThread Border Router app too. Download the backup and its matching emergency kit off the Home Assistant host.

Does the restored Home Assistant need the same IP address?

The old IPv4 address is not a replacement for the Matter fabric. Matter relies on local IPv6 and mDNS discovery, so working local reachability matters more than copying one IPv4 address. Keeping the same general LAN during the move still makes troubleshooting much easier.

Does a Home Assistant backup restore an Apple or Google Thread network?

No. Apple- and Google-owned Thread networks live in those ecosystems and border routers. Keep those hubs and credentials intact. The Home Assistant backup restores Home Assistant state, not the external platform.

What if the Matter Server data was not backed up?

If another Matter platform still controls the device, generate a fresh sharing code there and add it back to Home Assistant. If Home Assistant was the only controller and its fabric data is gone, factory-resetting and commissioning again may be necessary.