Home Assistant Matter Server 9.0: Migration And Post-Upgrade Proof
Tech GuruQuick Answer
Before moving to Matter Server 9.0, protect both Home Assistant and Matter controller data and identify the commissioned devices you expect to recover. Allow for first-start migration without treating a slow startup alone as failure. Then test existing device control, new commissioning, applicable OTA updates, and recovery. A running server or populated topology view does not prove the devices and automations work.
Evidence status: Home Assistant's June 23, 2026 announcement confirms Matter Server app 9.0 and automatic first-start migration to matter.js. No migration, device, OTA, or restore trial has been performed for this article, and no universal startup duration is established.
What To Check
The release announcement describes the app replacement and migration. Treat that as a supported product direction, not proof that every commissioned device or local automation survives unchanged.
Separate three questions: did controller data migrate, did the old devices reconnect, and can the new controller safely commission a device? Do not erase or recommission working devices simply because the first startup is slower than the old baseline.
Key Concepts In Plain Language
- Controller state: the Matter data needed to recognize and control commissioned devices.
- Fabric: the Matter trust grouping associated with commissioning; a visible device name is not a backup of that relationship.
- Acceptance test: an actual device action or recovery result, distinct from process uptime.
Technical Checklist
- Back up Home Assistant and the Matter Server datastore, record commissioned nodes, fabrics, controllers, versions, and a normal startup baseline.
- Schedule extra time for the first matter.js datastore migration and do not interrupt it only because startup exceeds the old baseline.
- Validate existing-node reconnection, new commissioning, OTA, controller recovery, certificate-revocation data, and topology visibility.
- Keep a tested restore path for both controller and Matter state; restoring only one side can leave devices commissioned but unreachable.
Interactive Operating Model
Use the planned checks below with this overview. No test result is implied by the diagram.
Before You Start: Safe Defaults
Protect the Home Assistant backup and the Matter datastore appropriate to your installation. Record commissioned nodes, fabrics, other controllers, app/Core versions, and startup observations. Know how to restore a consistent pre-change set before starting.
- Confirm the exact installed release, edition, repository, firmware, and add-on state instead of relying on the dashboard label alone.
- Export configuration and protect application data, credentials, certificates, and encryption material separately.
- Stage on a clone, spare node, canary device, or least-critical workload whenever the platform allows it.
- Define stop conditions and console access before the maintenance window begins.
Go, Hold, Recover, Or Escalate
Proceed on a recoverable installation when the data and device inventory are available. Hold additional changes during unexplained migration errors. Use logs and supported troubleshooting to distinguish work in progress from failure; never force success by deleting controller state or disabling commissioning checks.
Planned Checks And Recovery
Step 1: Preserve the commissioned state
Compare the backup coverage with the installed app's storage. Record the devices and automations that depend on Matter, and retain recovery material outside the system being upgraded. A Home Assistant-only copy is not assumed to contain every separate controller dependency.
Step 2: Observe first-start migration
Update using the supported path for the installation and retain the logs. Allow extra time without inventing a fixed timeout. If progress stops or errors repeat, investigate with Home Assistant support guidance before restarting or making further datastore changes.
Step 3: Exercise devices and commissioning separately
Control representative existing devices and run their dependent automations. Commission a supported test device, retaining the intended certificate restrictions. Check applicable OTA behavior and compare topology with known devices; a map alone is not a functional test.
Step 4: Rehearse consistent recovery
Recover the pre-change Home Assistant and Matter state together using the supported backup procedure. Confirm the same commissioned devices reconnect and their automations run. Record any device that requires intervention rather than claiming a complete restore from server startup alone.
Validation Checklist
- Expected existing nodes reconnect and report/control correctly; missing nodes are investigated individually.
- A supported test device commissions; certificate-related denial is investigated without weakening the default policy.
- Applicable OTA and controller-restart tests have device-level results, not just server logs.
- Restored controller and Home Assistant data operate the recorded devices and automations.
Troubleshooting
- Server starts but devices are missing: Compare commissioned-node inventory, migration logs, network reachability, and restored controller state before resetting a device.
- A development device will not commission: The announcement describes stricter handling of development/test certificates and revocation checks. Do not automatically classify denial as migration failure.
- Network map looks incomplete: Compare device-level control and available topology data separately; the view is diagnostic evidence, not proof of complete coverage.
Security, Privacy, Legal, And Recovery Boundaries
Security
Use official packages and release guidance, preserve signing and authentication controls, and do not expose a management plane to simplify migration.
Privacy
Configuration exports and support bundles may contain names, addresses, tokens, certificates, device identifiers, and user data; encrypt and restrict them.
Legal
Review software licenses, support entitlements, and retention obligations before copying production data into a test environment.
Recovery
A rollback is credible only when its media, configuration, keys, data, boot path, and restore order are available outside the system being changed.
Record any local exception, its owner, its expiration condition, and the evidence required to remove it.
What The Evidence Does Not Prove
No installed-release backup/restore sequence or maximum migration time is validated here. The repository's general README still contains beta language alongside the dated app announcement; use the installed app's release guidance rather than treating repository text as a universal deployment instruction. Tests on one device do not establish support for every Matter product.
Related TechGeeks Resources
- Linux and Homelab Notes: Start Here
- Homelab Backup Strategy: NAS, Offsite Copies, and Restore Tests
- How Do You Document a Homelab So Someone Else Can Recover It?
References
Next Action
Make the first acceptance record a comparison of commissioned nodes, actual device control, and recovered state. Keep new-device commissioning and OTA results separate from that baseline.
