Can you give us more information?
What’s not working?
I can help you with anything related to Gladys on the Aqara M100, however I have no experience and you’ll have to look on the Aqara forums in my opinion 
Thank you. I summarize:
I was able to set up my Aqara M100 and import it into Gladys, that’s good, and it appears under « Settings ».
I then imported a device (in this case a water leak detector) and I thought it would appear under « Devices » and not under « Settings » as shown in my screenshot.
If you already have an explanation for this
As for the rest, I’m scouring the Aqara forums, but I can’t find anything and all the IKEA devices won’t connect. I really think these devices are unfinished, and I’ll look into replacing them.
For this sensor, it’s probably that this type of sensor is not yet supported by the Matter integration in Gladys.
If you provide the JSON file by clicking the « Download Matter Nodes as JSON » button and sharing it on https://pastebin.com/ I could confirm that for you
Thanks, it’s here: Gladys jcm - Pastebin.com
For information, note that this time the leak detector has been added as a child device of the M100; I don’t know if that makes a difference, and an air sensor has been added as a node:
and only one device is reported:
No, Matter doesn’t need Bluetooth
1 Like
Haha sorry, copy-paste issue and I did it quickly, didn’t check. I’ve just edited it. 
[quote=« jcmoriaud, post:40, topic:9512 »]
3. I’m trying to see if there’s anything interesting to take from this: https://majornetwork.net/2026/01/home-assistant-was-unable-to-add-ikea-matter-devices/ .
les IP non fixe c’est du DHCP
tu laisse le serveur DHCP (généralement géré par la box internet chez un particulier) attribuer une adresse IP aux périphériques qui le demande.
Ton périphérique, dans sa config réseau tu peux le configurer
- en IP fixe (tu force l’adresse IP de ton périphérique)
- ou en DHCP (tu laisse ton périphérique prendre l’IP que ta box va lui proposer au démarrage/à la mise en réseau)
ça réponds à ton interrogation ?
Ok I knew that, thanks
Ok, that too I knew but what I was saying is that, from my experience, you never put any kind of server on DHCP, it’s part of the best practices I used at work.
What I don’t know, however, is whether what the article proposes — i.e. putting your server on DHCP — would solve the pairing problem of Matter devices…
yeah your question is clearer now
sorry!
1 Like
but I had exactly the same issue with my IKEA DIRIGERA edge router
There’s nothing implicit about having to share a device to get a new ID in order to add it to Gladys (or others).
It’s not indicated anywhere and it’s not intuitive at all, I tell myself it’s impossible for the average person…
1 Like
Indeed, I got flak when I reported that on the forum, and on top of that it’s slow…
However, what about the dynamic IP?
I admit it doesn’t make sense.
That it wouldn’t have any impact, maybe, but that it doesn’t work on a static IP doesn’t make sense…
1 Like
Indeed, we don’t handle the water leak sensor in the Matter integration for now — could you create a feature request and put the link in JSON in the request?
Hi @4get9, do you think we could improve something in Gladys, or is it more on the Thread hub side that you find it poorly explained?
1 Like
I think it should be in Gladys.
Je m’explique : en tant qu’utilisateur quand je vais chercher à ajouter mon périphérique dans Gladys, je vais chercher à le faire depuis Gladys.
1er réflexe : je vais dans add a device et mettre l’ID du device.
je pense qu’environ 99% des gens vont faire ça, c’est la façon la plus intuitive de le faire.
Par contre si tu veux que Gladys aide l’utilisateur il faudrait :
-
indiquer ça dans cet encadré
en ajoutant un « attention, selon votre Border Router, vous devrez peut-être passer par l’interface de celui-ci pour partager le périphérique. Dans ce cas vous obtiendriez un ID de partage, qu’il faudra renseigner ici »
ou un truc dans le genre. -
En cas d’erreur d’ajout, indiquer une phrase similaire quitte à y ajouter « notamment pour certains produits IKEA », et je crois comprendre que AQARA c’est pareil d’après un autre message.
Qu’en penses-tu ?
1 Like
Sorry, Matter indeed does not « need » Bluetooth, but on the other hand, if you have Bluetooth on the server, you can directly pair a Matter/Thread device without going through an app (personally I use the poorly translated and buggy Aqara app).
I came across the segment of this video: https://youtu.be/ewb41hv39bg?si=1mOZXzV6xdW-REZW&t=727 which points to this one: https://www.youtube.com/watch?v=hztYjL5yU3E where it’s well explained for Home Assistant (HA).
What do you think?
It’s handy for a device you want to pair to a Thread Border Router, but as it stands, Gladys is not (yet) a Thread Border Router
But my Aqara M100 is a Matter Border Router, isn’t it?
Yes, your devices are already connected to your Thread router. Gladys is not a Thread router, and does not handle Bluetooth pairing.
That won’t do anything 
I’m the one who developed the Matter integration in Gladys, I know what I’m talking about 
As @pierre-gilles said, you don’t need Bluetooth right now.
Since your Aqara M100 is a border router, you must use the Aqara app to pair your different Matter Over Thread devices with the code provided with your device.
Then you can share your device with Gladys by generating a new pairing code. On the Gladys side you enter the code and it should work, if it’s recognized by Gladys.
If one day Gladys acts as a border router, then in that case yes Bluetooth will be necessary, but currently it is not necessary to have Bluetooth. And on that day there will also be no need for an Aqara key.
2 Likes