Thanks @pierre-gilles
You’ll let me know when I can test again on:
gladysassistant/gladys:upgrade-matter-latest
1 Like
There’s not enough work on Gladys’ side, now @pierre-gilles is handling other people’s code to speed things up 
Well done! 
5 Likes
@prohand Hop, Appolon77 released matter.js 0.16.11 this morning, based on my fix. I just built a new version 
Available now on:
gladysassistant/gladys:upgrade-matter-latest
If you encounter any errors, copy everything and send them to me so we can iterate 
Thanks for your tests 
Thanks, I just tested and I still have the same issue
I’ll send you the logs in a private message
It’s strange, in your logs, there is no migration error, but Ignoring resumption record for fabric 0x01 and index undefined because we cannot find a matching fabric:
2026-04-10 11:57:03.675 WARN SessionManager Ignoring resumption record for fabric 0x01 and index undefined because we cannot find a matching fabric
2026-04-10 11:57:03.691 WARN BasicInfor~ionServer Using development values for some BasicInformation attributes: vendorId: 65521 vendorName: Matter.js Test Vendor productId: 32768 productName: Matter.js Test Product hardwareVersion: 0 softwareVersion: 0
2026-04-10 11:57:05.867 WARN Commission~ontroller BLE is not enabled on this platform
2026-04-10 11:57:05.870 NOTICE Node matter-controller-data going online
2026-04-10 11:57:05.878 NOTICE Node matter-controller-data is online
As if the data on the disk was corrupted/absent.
Can you confirm that you have indeed launched Gladys on a Matter folder that was working with the old version?
Actually, there is a file migration that is executed to go from the old version of Matter.js to the new one, and if the migration does not pass, it cannot work.
In this case, is there a way to start from scratch with the matter plugin on Gladys?
I’m afraid all the manipulations I did have messed things up 
I think I saw something in the Matter.js code that’s problematic… I sent a message to Appolon77, I’ll get back to you.
Ah ok thanks, in any case to answer the question yes I started from a functional version of matter with the old version
For information I am on vacation tonight and for 1 week I will not be able to do many manipulations 
According to Appolon77, there is indeed a bug in the migration, but it is « temporary. » In fact, the migration loses some information but keeps the device’s IP, and normally, all devices should reconnect gradually after the migration.
I will make a PR on Matter.js to fix the bug, but in fact, they have deployed this update in production for a long time and it hasn’t caused major issues according to him.
@prohand, are you sure that after waiting 5 minutes, all your devices come back and are then usable?
Yes I’m sure I left them all the time at noon and they didn’t come back up
And are they displayed as « disconnected » in Gladys?
If you want to test in a clean environment, you delete the « matter » folder, you restart in the current version of Gladys, you pair your devices again, and then you launch the new version on the matter folder
After that, since you’re going to do that, if you are the only one affected by the bug, is it really worth it? And wouldn’t it be better to reset your Matter integration in the new version of matter.js to start with a clean, non-migrated base?
If there are other testers, that would be great!! @Terdious, you who had issues with the current version, I would be curious to have your feedback!
Yes, they are disconnected
The goal was to test a migration from the old version to the new version
1 Like
@prohand Appolon77 spent quite a bit of time this afternoon on your case He tested with your ZIP file, and normally the migration works well (in the state the ZIP was in when you sent it to me).
So yes, perhaps by doing so many migrations, you corrupted your storage. According to Appolon77, you probably interrupted a migration in progress, maybe due to the previous crash that is now fixed…
So yes, retesting from scratch is a good lead!
1 Like
Yes, I am retesting from scratch.
However, deleting the contents of the matter folder does not seem to reset matter.
Is this the correct folder?
Oh no, not at all, you’re in the code there!!
You did a great job recreating the files ^^
Can you show me how to properly delete the correct matter folder please?
The matter folder is in /var/lib/gladysassistant/matter, you will find a folder matter-controller-data.
You need to delete this folder matter-controller-data.
In my case:
gladys@gladys:/var/lib/gladysassistant/matter$ ls
matter-controller-data
If I wanted to delete, I would do:
sudo rm -rf /var/lib/gladysassistant/matter/matter-controller-data
And then, restart Gladys!
(This folder is on the host, depending on your Docker volume definition)
Thank you
It seems to restore a backup for me:
2026-04-10T15:41:27+0200 <info> matter.init.js:20 (MatterHandler.init) Matter.init: storagePath: /var/lib/gladysassistant/matter
2026-04-10T15:41:27+0200 <info> matter.init.js:30 (MatterHandler.init) Matter.init: no files in storagePath, restoring backup...
2026-04-10T15:41:27+0200 <info> matter.restoreBackup.js:21 (MatterHandler.restoreBackup) Matter.restoreBackup: backup found, restoring...
2026-04-10T15:41:28+0200 <info> matter.restoreBackup.js:30 (MatterHandler.restoreBackup) Matter.restoreBackup: backup restored
Any idea how to delete this backup?