@prohand, you’ve made more progress than I have on this one.
You’re not the only one with a setup like this with multiple VLANs ![]()
@prohand, you’ve made more progress than I have on this one.
You’re not the only one with a setup like this with multiple VLANs ![]()
So it really was a version problem
Is it possible to include the update in the next Gladys release or not?
Excellent! In that case yes, but we need to run more tests first, notably we need to test the migration from 0.13.0 to 0.16.8, because the CHANGELOG specifies that there is a file migration and I want to make sure it doesn’t break existing installations ![]()
Could you run those tests?
I’d like to, but how can I run these tests?
Given that I don’t have any other Matter devices ![]()
I could try with a copy of my database, but not until the end of the week.
Knowing that I don’t have any other Matter devices
With Matterbridge you can do it! There’s a plugin that creates lots of virtual devices
I am testing:
So with the current stable version I can reach matterbridge and add devices:
I also have these errors in the Gladys logs:
After updating to matter.js version 0.16.8 the devices are still visible:
I did the same procedure to pair my device as before and I now get this message:
And I no longer have this in the settings view:
When I go back to the stable version I end up with this in the settings:
There must be some action to take, I suppose on the matter.js side
@pierre-gilles Do you have the details of the file migration and how to perform it?
Thanks
I also have these errors in the Gladys logs:
These errors are normal, you’re receiving states for devices that you haven’t added
After updating to matter.js version 0.16.8 the devices are still visible:
And are they still fully functional? Are you still receiving values? Are they controllable?
I performed the same procedure to pair my device as earlier and I have this message now:
Ah, there’s code to fix apparently. Can you copy the error code for me? (not just a screenshot)
When I go back to the stable version I find this in the settings:
Yes that’s normal, you can’t go back, the migration only exists in one direction (ancien → nouveau)
In Gladys it’s the same, you can’t go from a new version to an old one.
Ah, there is code to fix apparently. Can you copy the error code for me? (not just a screenshot)
Here it is:
2026-02-09T21:53:23+01:00 \u003cinfo\u003e matter.pairDevice.js:38 (MatterHandler_pairDevice) Commissioning device with options: {\"commissioning\":{\"regulatoryLocation\":0,\"regulatoryCountryCode\":\"XX\",\"regulatoryLocationType\":0},\"discovery\":{\"identifierData\":{\"shortDiscriminator\":7},\"discoveryCapabilities\":{\"ble\":false}},\"passcode\":23138390,\"commissioningTimeoutSeconds\":90,\"commissioningAttempts\":4,\"commissioningRetryDelayMs\":1000}
2026-02-09 21:54:07.067 WARN ClientEventEmitter Received event for unsupported endpoint #5 on matter-controller-data.01@a18a450138dee8d3
2026-02-09T21:54:07+01:00 \u003cinfo\u003e matter.pairDevice.js:42 (MatterHandler_pairDevice) Successfully commissioned device with nodeId 11640192058443884755
2026-02-09T21:54:08+0100 \u003cwarn\u003e errorMiddleware.js:68 (errorMiddleware) TypeError: device.childEndpoints.map is not a function
at convertDevice (/src/server/services/matter/lib/matter.getNodes.js:19:48)
at /src/server/services/matter/lib/matter.getNodes.js:53:16
at Array.map (\u003canonymous\u003e)
at /src/server/services/matter/lib/matter.getNodes.js:52:24
2026-02-09T21:54:08+0100 \u003cwarn\u003e errorMiddleware.js:68 (errorMiddleware) TypeError: Cannot read properties of undefined (reading 'get')
at handleDevice (/src/server/services/matter/lib/matter.handleNode.js:29:76)
at /src/server/services/matter/lib/matter.handleNode.js:87:13
at tryCatcher (/src/server/services/matter/node_modules/bluebird/js/release/util.js:16:23)
at Object.gotValue (/src/server/services/matter/node_modules/bluebird/js/release/reduce.js:166:18)
at Object.gotAccum (/src/server/services/matter/node_modules/bluebird/js/release/reduce.js:155:25)
at Object.tryCatcher (/src/server/services/matter/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/src/server/services/matter/node_modules/bluebird/js/release/promise.js:547:31)
at Promise._settlePromise (/src/server/services/matter/node_modules/bluebird/js/release/promise.js:604:18)
at Promise._settlePromiseCtx (/src/server/services/matter/node_modules/bluebird/js/release/promise.js:641:10)
at _drainQueueStep (/src/server/services/matter/node_modules/bluebird/js/release/async.js:97:12)
at _drainQueue (/src/server/services/matter/node_modules/bluebird/js/release/async.js:86:9)
at Async._drainQueues (/src/server/services/matter/node_modules/bluebird/js/release/async.js:102:5)
at Immediate.Async.drainQueues (/src/server/services/matter/node_modules/bluebird/js/release/async.js:15:14)
at processImmediate (node:internal/timers:485:21)
These errors are normal — you’re receiving states for devices you haven’t added
Noted, thanks ![]()
Yes, that’s normal: you can’t go back, the migration only works one way (old → new)
It’s the same in Gladys, you can’t downgrade from a new version to an old version.
So what I meant is that this menu is missing in the new version — basically the Matter nodes are not visible; it shows this on the new version:

So what I meant to say is that this menu is missing in the new version, basically the Matter nodes are not visible, it shows this to me on the new version:
Oh no!
Well, given the various points, the migration isn’t as straightforward as that — there’s development work to be done.
@prohand Do you think you can take a look (maybe with the help of AI?) or is it really beyond your skills?
It’s a bit outside my expertise ![]()
But if you tell me where you saw the file migration I can try to take a look, because I couldn’t find that information in the changelog
It’s indeed in the CHANGELOG, version 0.16.0 : https://github.com/matter-js/matter.js/blob/main/CHANGELOG.md#0160-2026-01-12
« The storage location of controller base data has moved » :

They say it’s automatic but I don’t know how to check if it’s been done properly or not ![]()
There are other breaking changes apparently but no idea if that has any impact on Gladys’ code
So I confirm it’s completely beyond my abilities ![]()
2 messages have been split into a new topic : Create tutorial for connecting SMLIGHT to Gladys Z2M?