🚀 Matter & Gladys Assistant: Here we go!

[mutmut]

@pierre-gilles

If you want to see the result of the command on your machine, you can open your browser’s inspector and select this request:

I have 17 IPv6 even though it’s disabled on the Synology ??!??

Looking at my Docker containers, I have 18 running; if I remove Gladys that makes 17. And if I stop another one, I drop to 16 so that corresponds to the local IPv6 (fe80: of my containers.
Is that the normal result you expect from your command?

If I enable IPv6 on the Synology, I go to 19 interfaces (2 more) and I notice that objects 0 and 1 are actually the Synology’s external and local IPv6:

[mutmut]

@pierre-gilles

Not sure I understand the question? I develop on a Mac and my Gladys runs on a Beelink mini S12 Pro

so it’s therefore on a PC, not on a NAS like a Synology or QNAP which might do things we have less control over.

[mutmut]

@pierre-gilles

That said, you should still see it in the list under « Settings », right?

no, it’s gone

[pierre-gilles]

@mutmut

Looking at my dockers, I have 18 running, if I remove Gladys’s that makes 17. And if I stop another one, I drop to 16 so that corresponds to the local ipv6 (fe80:: ) of my containers.
Is that the normal result you expect from your command?

Thanks for the feedback, I think that’s the issue: your Synology NAS still keeps local ipv6 interfaces (fe80::) even when you disable ipv6 on your Syno.

When ipv6 is disabled, can you confirm that you only have addresses starting with fe80::?

If so, I can filter those addresses and not use them, would that work in your case?

[mutmut]

@pierre-gilles

I just pushed a new Docker build with automatic matching this time based on the pair « UNIQUE_ID + position » (imperfect solution, I remind you, but « good enough »)

![image|248x500

[mutmut]

@pierre-gilles

When IPv6 is disabled, can you confirm that you only have addresses starting with fe80::?

yes, that’s correct.

@pierre-gilles

If so, I can filter out those addresses and not use them, would that work in your case?

That works for me

I have to step away, I’ll retest tonight, thanks for your huuuuge work!

[pierre-gilles]

@mutmut

And after the update I get this shift:

Yes, it’s not a bug, unfortunately the unique identifier in Gladys changes if you decommission then recommission a device, and so you have to modify the scenes and dashboards that use that device.

In truth, the only thing we can preserve with « smart matching » is the history of sensor values, but that’s the only thing!

[pierre-gilles]

@mutmut

yes, that’s right.

I’ve made a new Docker build that excludes local addresses from the calculation, so it should better reflect the IPv6 situation

[pierre-gilles]

@pierre-gilles

Yes, it’s not a bug, unfortunately the unique identifier in Gladys changes if you decommission and then recommission a device

I’m thinking about that, I wonder if we couldn’t find a selector (the unique identifier used in Gladys internally) that would be a mix of the device name, the feature, and a bit of randomness, and that would be set in stone (even in case of decommissioning + recommissioning), which would not require recreating your dashboards / scenes!

[pierre-gilles]

Ok good news — I found a solution for dashboards/scenes that need to be redone, I’m using a selector as described in the previous message

I’ve pushed it as a new Docker image!

@mutmut @terdious You’ll need to remove the devices currently added, but after that it will work I’d appreciate your feedback!

[mutmut]

Perfect, we’ll keep it!
IPv6 disabled:

IPv6 reactivated:

Can you make everything singular or plural for the interfaces depending on the number found? I know, I’m asking a lot

[pierre-gilles]

@mutmut

Can you make everything singular or plural for the interfaces depending on the number found? I know I’m overdoing it

Yes I’ll change that

[pierre-gilles]

Hello everyone

Apart from this small syntax change, is there anything else missing in your opinion?

I’ll be working on Gladys tomorrow, Friday, and this weekend, so it’s a good time if you have any feedback

[mutmut]

Hello,
I haven’t tested your latest build and the selectors yet; I should be able to do so tomorrow.

[pierre-gilles]

New Docker image built!

Fixed the text about IPv6 to use the singular form
Implemented the code that will allow the interface to detect when a device update is available; this will be useful for upcoming Matter releases when we add new features!

[mutmut]

I’m resuming my tests with a fresh Gladys (spoiler alert: long blah blah but … ).

I go to the Matter integration and I get to:

I click on Ajouter un appareil and I get this:

Notes:

• if Matter is not enabled then we should be redirected:
  • directly to the Settings tab by default (and this for all integrations in my opinion because we always land on Devices)
  • or a button Enable Matter (which links to Settings) instead of Ajouter un appareil
  • or remove the Ajouter un appareil button

In Settings, by default we don’t see the IPv6 message.
I had to enable Matter and the message appeared afterwards.
If we disable Matter, the message remains and doesn’t go away.

@pierre-gilles

Fixed the text about IPv6 which changes to singular

Perfect!

At the UI level (for novices), it’s not really clear what to do to get started right now because it says Aucun noeud Matter trouvé and there is no action that contains the word Node. It should:

• either have a button to add a Matter device/node and switch to Ajouter un appareil
• or a text that says you need to go to Ajouter un appareil to be able to start.

Ok, I set up my shutters, everything works.
Disable the plugin in Matterbridge … re-enable the plugin → all devices have new Endpoints:

In Gladys, no change in the names:

I go back to my dashboard, I try to raise/lower the shutters → KO
I add a paired shutter, I test raise/lower → KO
I decommission, I recommission.
The devices appear with their new Endpoints and request an update for the saved ones:

I test raise/lower WITHOUT doing the update → KO
I test raise/lower AFTER the update → OK
For info, the names of saved devices do not change and keep the one from the first save.

@pierre-gilles

Implemented the code that will allow the interface to detect when an update for a device is available, this will be useful for the next Matter releases when we add new features!

Awesome!
But a small remark, or rather a big one: you have to decommission and recommission the Matterbridge server after every modification in Matterbridge.
That means if you add a new physical Somfy module, Matterbridge will pick it up (by itself?) and then you’ll have to decommission and recommission Matterbridge … I find that a bit annoying when you see the simplicity with z2m and zwavejs-ui where new modules appear naturally after adding them.
Sure, we’re not going to install a new shutter every day but for Shelly modules (e.g.) you can install them gradually and it will be the same story to see them in Gladys.

In any case it works very well captain @pierre-gilles

EDIT: small issue with refresh or fetching the info after action open II close but the shutters’ positions are wrong and should have the values in red, and I think it worked fine before:

[pierre-gilles]

Thanks for your very detailed feedback @mutmut!

@mutmut

if Matter is not enabled

Ok I’ll rework that screen if Matter is not enabled.

@mutmut

In Settings, by default we don’t see the IPv6 message.

Ok that’s strange, I’ll investigate.

@mutmut

• either a text that says you need to go to Add a device to get started.

Good catch! I’ll change that

@mutmut

But a small remark, well rather a big remark: you have to decommission and recommission the Matterbridge server for every modification in Matterbridge.
That means that if you add a new physical Somfy module, Matterbridge will pick it up (by itself?) and then you’ll have to decommission and recommission Matterbridge …

I don’t know exactly how the Matterbridge-somfy plugin works, but I imagine that if you add a new roller shutter at your place, there’s no need to reconfigure the plugin; it will be added automatically and Gladys will pick it up in the list of "paired devices not added to Gladys".

From what I read about Matterbridge, that’s kind of the software’s overall philosophy: a single pairing code for all your devices!

If that’s not the case, you’ll have to complain to Matterbridge-somfy For Gladys’s part, we don’t control that side; we "see" a list of Matter devices on the network.

@mutmut

In any case it works very well captain @pierre-gilles

Great! I think after the small fixes above we’ll be good for a release

@mutmut

EDIT: small issue with refresh or retrieving the info after action open II close but the positions of the shutters are wrong and should have the values in red, and I think it worked fine before:

This part hasn’t changed, are you sure everything is fine on the Matterbridge side?

[elfedagger]

That really makes me want to. I’m looking for a second-hand Somfy (Tahoma mini) connectivity kit to migrate my shutters to that setup. Thanks for this work.

[mutmut]

@pierre-gilles

I don’t know exactly how the Matterbridge-somfy plugin works, but I imagine that if you add a new roller shutter at your place, there’s no need to reconfigure the plugin; it will be added automatically and Gladys will pick it up in the list of « paired devices not added to Gladys ».

I just tested with the matterbridge-zigbee plugin.
I added a new module via z2m; this module did appear in matterbridge but nothing in Gladys unless I decommission and recommission to fetch the new list of devices — there is no real-time update of paired devices.

I asked the question here.

@pierre-gilles

That part hasn’t moved, are you sure everything is OK on the Matterbridge side?

Everything is fine on the Matterbridge side regarding the values, except that we’ve moved to 3.0.1 instead of 3.0.0.

[mutmut]

You can get a Tahoma v2 (io, RTS), Tahoma switch (io, RTS, zigbee) or Connexoon (that’s what I have, io only) but not the Connectivity kit (cheap but no local API, that’s a shame).