🚀 Matter & Gladys Assistant: Here we go!

[pierre-gilles]

@Terdious I get the impression there’s only one type, « TemperatureMeasurement », so no way to discriminate at that level.

Do you have anything locally—if you look at the device object—that could indicate to me that it’s not an ambient temperature sensor?

[pierre-gilles]

@mutmut I made some fixes!

1. Search and sorting now work both in the device list and for devices « paired but not added to Gladys ».
2. Only one back icon
3. The « Settings » tab indicates whether the Gladys instance has access to an IPv6 interface. Could you test this part since you experienced it? Disable / then re-enable IPv6 to see if you get an error message?

Available in the Docker image!

To update, as usual:

sudo docker pull gladysassistant/gladys:matter-integration

sudo docker stop gladys
sudo docker rm gladys

Then restart the container with the same docker run command as before.

[Terdious]

@pierre-gilles

Do you have anything locally if you look at the device object that could indicate to me that it is not an ambient temperature sensor?

Indeed, I think not; there is no distinction, at least not yet. They are labeled « TemperatureMeasurement ». Maybe the deviceTypeList property which is [ { deviceType: 770, revision: 2 } ] on all three, but I don’t think we want to go through that.

The best solution would probably be to be able to edit the device like for switches (Lighting/Plug) and select between the two types of temperature features.

[pierre-gilles]

Darn, indeed we’d only be able to do it like that if that’s the case

In the Matter spec, I don’t see a deviceType specific to internal temperatures either:

https://handbook.buildwithmatter.com/howitworks/devicetypes/#pressure-sensor

I’d be curious to see how this kind of device appears on an iPhone in the Home app!

[mutmut]

Hi @pierre-gilles, thanks for the fixes!

@pierre-gilles

1. Search and sorting now work both in the devices list and in the devices « paired but not added to Gladys ».
2. Only one back icon
3. The « settings » tab indicates whether the Gladys instance has access to an IPv6 interface. Could you test this part since you had the case? Disable / then re-enable IPv6 to see if you get an error message?

1. Perfect, but you need to type slowly because the search starts immediately as soon as you type a character → so this might happen when you have a large number of devices, well it’s not blocking at all
2. icon
3. here it gets a bit complicated and I’ll skip a line

I updated Gladys and I have IPv6 interfaces are available on this machine ✅ (ipv6 enabled on the syno)
I disabled IPv6 on my syno with a reboot of Gladys and reboot of the 2 Matterbridges (syno and lxc): I still have the same message

I tried to decommission the matterbridge lxc: no decommission. I stop Matter, I restart Matter: the matterbridge lxc is still there so I click decommission again: still nothing.
I go to the devices and I find the devices from the matterbridge lxc duplicated then triplicated (I don’t remember the actions I performed but there were a lot of decommissions).
I then re-enabled IPv6 on the syno, rebooted Gladys and the 2 matterbridges: I was able to decommission the matterbridge lxc and everything returned to normal regarding the devices.

In short, I must admit I’m a bit lost with my actions but having a host in IPv4 only is not ideal at all, that’s for sure.

[mutmut]

A remark on recommissioning a matterbridge and its devices.

I had a saved device (a Sonoff Zigbee relay added to Gladys as Matter) from the first commissioning, no issues with the switch on/off and state reporting.
I decommission the matterbridge, the devices disappear and this device remains (since saved).
I recommission this matterbridge, therefore with a new pairing number, and I find this Sonoff again in the list of devices I can add to Gladys, and then I end up with 2 devices: one saved and one paired.

(I added « terrace » to differentiate them)

Would it be possible to automatically « reattach » the matterbridge device that still has the same Unique ID and Serial Number (which is actually the IEEE in Z2M) but a different Matter bridge (Node ID), to the device already saved earlier?

[pierre-gilles]

I have good news: Matter.js 0.13 is out!

On the agenda: support for Matter 1.4, and especially support for custom loggers, which will allow us in Gladys to avoid putting Matter’s very verbose logs into our Gladys logs

CHANGELOG here

I’ll test it all and get back to you!

@mutmut

I disabled IPv6 on my syno with a reboot of Gladys and reboots of the two Matterbridges (syno and lxc): I still have the same message

Thanks for testing!

What I do in the code is list the available interfaces in Gladys (a bit like running ifconfig on your machine), and if there is at least one IPv6 interface, I display « IPv6 interfaces are available on this machine  ».

In your case, that means there is still an IPv6 interface available, even when you disable IPv6, but it’s hard to know what disabling IPv6 does on your syno!

@mutmut

Would it be possible to automatically « attach » the Matterbridge device that always has the same Unique ID and Serial Number (which is, by the way, the IEEE in Z2M) but a different Matter bridge (Node ID), to the device already saved previously?

@Terdious had already made that remark, I’ll look into doing that

[pierre-gilles]

@mutmut @Terdious You’re going to be happy, I developed the feature to use the uniqueId when available to replace existing devices!

Tested on my setup, it works perfectly. Available on the Docker image if you want to test it

Also, I set the Matter.js « Log level » to « notice », so the logs are much less verbose.

Do you see anything else missing for a first version of this integration?

[pierre-gilles]

I posted a message on Reddit r/MatterProtocol to get feedback

Open Source: Looking for feedback on our new Matter integration (Gladys Assistant)

[pierre-gilles]

Ok, following feedback from a Reddit user, I improved the integration’s overall UX:

• Warning on all screens when the integration is not enabled
• Spinner when adding a new device with a short message to warn that this may take several minutes (like on iOS)
• Propagation of the error message coming from Matter in case of an add error

@pierre-gilles

@mutmut @Terdious You’re going to be happy, I developed the feature to use the uniqueId when available to replace existing devices!

Bad news, it doesn’t work well because currently some devices with a single uniqueId are split into multiple Gladys "device"s. I’ll look into fixing that

[pierre-gilles]

There was a new Matterbridge release 2 days ago, and on my end I haven’t been able to pair since

[pierre-gilles]

Ok normally I’ve solved all the issues, and now the « devices » with the same uniqueId are grouped into the same Gladys device, it looks better

Don’t hesitate to test and give me feedback!

[pierre-gilles]

I improved the deviceFeatures title, because in the latest version of Matterbridge they used as examples devices that have multiple features in the same device (for example: a cooktop with 4 burners)

Strangely, I can’t find a name for each of these clusters, but I have at least added the endpoint number, which allows them to be distinguished!

[Terdious]

Hello @pierre-gilles, I just tested (image uploaded at 14:10.

On

[Terdious]

Very strange indeed … I was on 3.0.1 and it offered me an update to 3.0.0 that I have just installed …

[pierre-gilles]

Ok, I’ll look into all of that, thanks for the test!

[pierre-gilles]

I’m building a new image, I’m splitting the devices again like before — it was handy to be able to assign a different room to each childDevice, and it also lets me put the endpoint in the device name.

However, I removed device replacement via unique_id; that’s no longer possible, and anyway it never fully worked, because I have no way to identify a child_device, only the physical device. Inside the device, each endpoint number can change, so it’s impossible to match everything, especially for devices with the same feature multiple times!

[pierre-gilles]

Build completed!

[pierre-gilles]

Really strange, since Matterbridge 3.0.0, everything on the Matterbridge side is really exploding, I can’t control anything anymore…

Earlier it was working, now it isn’t

My physical Matter devices don’t have the issue

[Terdious]

I’m going to pick up my daughter, I’ll check later with the physical matterbridge!
Did you try the matterbridge-eve plugin then?