Hello everyone.
After a few weeks off I’m getting back to Gladys (driven by the arrival of Matter).
I still have my IPv6 issue but strangely I can still connect to my Shelly and Zigbee devices thanks to MatterBridge.
I still notice some bugs in device recognition.
The multi-socket device and 0x540f57fffef5f20b are actually the same.
It’s not very problematic, but it looks a bit messy.
If you can tell me why for these two mysteries…
Thanks in advance.
Hello @l.dolle
are you routing your Shelly AND your Zigbee network through Matter?
And your Lidl modules are Zigbee, right?
Personally I’d leave Zigbee managed by Gladys and the z2m integration, so you have all features available because if they’re not in Matter, we won’t be able to integrate them until Matter releases a new version with those features. Whereas on the z2m and Gladys side we (well, the devs
) can integrate them very quickly.
Otherwise, regarding your duplicate modules, Gladys only retrieves what Matterbridge exposes so you need to check what Matterbridge shows you in Devices,
Hi @mutmut — Actually, I think MatterBridge picks them up from Z2M, because as I reconnected the devices on z2m, they also automatically appeared on Matter
Matterbridge pulls directly from MQTT, not from Zigbee2MQTT (z2m).
Dans la config on indique le serveur Zigbee2MQTT (z2m) juste pour basculer dessus quand on clique sur le device Zigbee.
Hello everyone,
To add to my comments from yesterday, the duplicate display has finally disappeared. 
However, can someone tell me what the functions related to MatterBridge are for? Is it possible to restart and update MatterBridge from Gladys? Is that right?
I just discovered the work done to modify the devices interface — well done to the team for this excellent work.
Yes! MatterBridge added this in the latest version.
Thanks 