I have two IKEA BILRESA dual-button Matter buttons. I added them to Gladys (via the Matter integration),
That’s cool you managed to integrate them into Gladys, I still haven’t. What’s your Matter border router?
For info: in: Intégration d'un hub Thread Aqara M100 - #44 par jcmoriaud, I noted last night that I have the same problem with the Bilresa on my Home Assistant test instance where I was able to add them, but there is a « blueprint » on HA that brings the functionality.
You know, I’m a knowledgeable hobbyist, not a geek: I’m discovering the term « border router » 
.
If that answers your question, I use Apple’s Home app and an Apple TV acts as my hub.
As I wrote, Gladys did accept the two buttons via Matter but they are not in the list of paired devices: I can’t use them! And I have the same problem with
Do you have a « share » option in the device options (from the App you use to manage them)?
They are already shared. But they are invisible in Gladys.
These buttons may not yet be « defined » in Gladys — that’s why they don’t appear (yet).
I think you’ll need to send a JSON file to @pierre-gilles for the integration.
This file is normally found in the Matter integration Settings.
Thanks, I see where that file is (it’s about Matter nodes). I’ll wait for @pierre-gilles to ask me for it if he needs it.
Indeed, these IKEA buttons are brand new and I think you’re one of the first to have them in Gladys 
We’ll add it, don’t worry!
Could you provide us the JSON file you get by clicking on this button:
You can host it on https://pastebin.com/ for example, and don’t worry there is no sensitive information in this file, it’s just generic information about the functions exposed by your device
@pierre-gilles, explain one thing to me. The Matter protocol standardizes messages, so why do we have to add this device specifically? Or is it the first « message » of this type that Gladys needs to integrate?
It’s like with Zigbee, Z-Wave and others: just because the protocol knows the device and its features doesn’t mean Gladys can use them without any work, even if an integration exists.
You have to tell Gladys (i.e., develop) that a switch should react like this, a motion sensor sends information like this, a light can have functions such as brightness, color, on/off, etc.
And that has to be done for each protocol.
Zigbee is an « old » integration and therefore has many known generic devices (switch, light, energy consumption and power, etc.) that have been developed.
If a new device with new features comes onto the market and no one on the forum buys it, development and real tests will be difficult to carry out and it will take time.
For Z-Wave, an integration younger than Zigbee, few people have it so there are few device additions with their features. I come from Jeedom and I have devices that were implemented in Gladys after I provided the information for the integration.
For Matter it’s the same, and it’s even younger.
All the tests and the integration were carried out (unless I’m mistaken) thanks to matterbridge which exposes certain devices in demo mode.
In real-world use we’re only just starting, so there are still gaps and we will be able to enrich the device and feature database thanks to people who buy hardware.
Where it can get complicated is that manufacturers of Matter-compatible devices integrate a version of Matter that may be older than the current one, and some features are not supported by the device (for example, reporting of information), and you only discover that after your purchase and when operational problems occur.
And you need to keep in mind that a device’s features are not transmitted from one integration to another; unfortunately they are separate « worlds ».
I hope my explanation is clear enough, I may not have reviewed it very well 
2 Likes
Thank you for this very thorough explanation.
I would add that Matter mainly standardizes messages by device type. Unlike with other Zigbee and Z-Wave systems, you no longer have to create an integration per device/brand but per device type.
A bulb will « normally » always have the same features and therefore the same message.
Indeed you don’t yet support all device types from Matter 1.5. There will still be quite a bit of work.
I wonder whether an LLM could manage to integrate new devices into Gladys based on the Matter specs. But that’s another subject.
si tu partages le périphérique, tu récupère un ID
il faut ajouter cet ID dans Glagys (Integration / Matter / Add a device)
C’est du moins la méthode que j’ai appliqué avec mon DIRIGERA et mes devices IKEA Matter
d’où ma question. Regarde si tu ne dois pas procéder comme moi.
I sent it to you via Direct Message (I used Smash): did you receive it?
C’est ce que j’ai fait (cf mon message initial). En fait, ces boutons IKEA et le détecteur d’ouverture Aqara Door and Window Sensor P2 ont besoin d’une mise à jour de Gladys pour pouvoir être utilisés.
ok I misunderstood, sorry!
I don’t understand anything anymore. Now, in the Matter integration Settings, I no longer have a Matter node: « No Matter node found. You can add a Matter device by going to the « Add a device » tab. » (Matter is, of course, enabled).
And, in the Devices section of that same Matter integration, I no longer have any « Paired devices not added to Gladys ». I only have the devices that I had already added to Matter!
And to top it all off, there’s a thermometer that no longer reports any information: « No temperature recorded recently ».
Exactly yes! All smoke detectors have the same API, but you do need to integrate at least one so that afterwards we can manage them all
Received!
Indeed, in the JSON there are 2 Matter « clusters » that we don’t yet handle on the Gladys side: « Boolean » (in the « Aqara Door and Window Sensor P2 ») and « Switch » (in the « BILRESA dual button »)
I created 2 requests:
I’ll look into it! (Unless someone wants to give a hand :D)
Did you change anything? Are your devices still connected and functioning on your Border Router? Is your local network working properly?