Just installed the new 8.2.0 version of the HA Matter server add-on and when I switch on the beta setting to enable matter.js all my nodes are gone. Switching back to Python brings them back. The release notes say they should be migrated automatically. Anyone had a similar experience?
1 Like
My experience is that it took a few minutes for the matter.js server to start up, during which everything was gone - but eventually things came back up.
The immediate advantage of the new server was that I finally could update the devices, something that hadn’t worked with the Python server.
It took about 30 seconds to install the npm and then everything was back up.
Looks like identified the problem, but not sure of the solution yet:
2026-01-22 22:32:43.323 INFO LegacyDataLoader Loaded legacy chip.json with 2 fabric(s)
2026-01-22 22:32:43.325 ERROR LegacyDataLoader Expected exactly one fabric with index 1, found indices: [1, 2]
2026-01-22 22:32:43.325 WARN MatterServer Legacy data error: Expected exactly one fabric with index 1, found indices: [1, 2]
I think I’m seeing the same issue, with the caveat that my Matter Python server isn’t working now either! It appears that when I paired a new device this morning, a new Matter fabric was created. Now Matter JS won’t start at all, and Matter Python starts with Fabric #2 which has only my newly-paired Node.
Here are the logs that prevent matter.js from starting:
2026-01-25 16:53:14.358 INFO CertificateAuthority Loaded stored credentials with ID 1 and ICAC with ID 2
[crashed-dependency] MatterController unavailable due to initialization error
at crashedError (/opt/matterjs/node_modules/@matter/general/src/util/Construction.ts:623:32)
at handleRejection (/opt/matterjs/node_modules/@matter/general/src/util/Construction.ts:325:69)
Caused by: [implementation] Fabric with index 1 is already present but not under the control of the Fabric Authority
at <anonymous> (/opt/matterjs/node_modules/@project-chip/matter.js/src/MatterController.ts:385:27)```