That’s what bothers me the most, actually
1 Like
On my side I tested Sonoff Matter
I tested a Nous Matter WiFi plug.
I had to install the Nous App, share the plug and I was able to add it in Gladys.
Except that Nous doesn’t use the latest version of Matter for this plug model, so for the consumption reporting they did it their own way. So it doesn’t show up in Gladys.
So for now really not convinced… but I’m not losing hope
I managed to do something with matterjs-server that I put on the same machine as the OpenThread border router :
Here is the docker compose for matterjs-server :
services:
matterjs-server:
container_name: matterjs-server
image: ghcr.io/matter-js/matterjs-server:latest
network_mode: host
restart: unless-stopped
environment:
BLUETOOTH_ADAPTER: 0
volumes:
- ./matterjs-server:/data
- /run/dbus:/run/dbus:ro
Then :
docker compose up -d
Then install the missing modules for Bluetooth :
docker exec -it matterjs-server sh
apt update
apt install python3 make gcc g++
npm install @stoprocent/noble
exit
Restart the container :
docker container restart matterjs-server
Then retrieve the dataset from your openthread docker with the following command:
sudo docker exec -it openthread-otbr-1 sh -c "sudo ot-ctl dataset active -x"
Click here :
The dataset we retrieved in the previous step is requested :
Then enter the code shown under the QR code of your device here :
Watching the logs with the following command you can see the progress :
docker logs matterjs-server -f
We can see that our device is added to matterjs-server :
You can also see it on OTBR in the topology section :
To add it to Gladys you need to get a sharing code which is found directly in the device on the matterjs-server web interface :
For now when I enter the code provided by matterjs-server and put it in Gladys it does not work.
I haven’t found a solution yet but I will edit this post when I find it
Edit :
I think Gladys must be able to see the device directly so I had to find its IPv6 address via the command :
avahi-browse -r _matterc._udp
Pinging the address fd6c:741e:2136:1:b534:6559:d9c1:c09c from my OTBR machine worked but not from Gladys.
For the ping to this IP to work with Gladys I had to add the following to the file /etc/sysctl.conf (I don’t know if everything is necessary but I will modify as needed):
(https://raw.githubusercontent.com/openthread/ot-br-posix/refs/heads/main/etc/docker/border-router/setup-host)
net.ipv6.conf.ens18.accept_ra = 2
net.ipv6.conf.ens18.accept_ra_rt_info_max_plen = 64
net.ipv6.conf.wpan0.accept_ra = 2
net.ipv6.conf.wpan0.accept_ra_rt_info_max_plen = 64
net.ipv6.conf.all.forwarding = 1
net.ipv4.ip_forward = 1
Now Gladys can reach my device over IPv6 but it’s still impossible to link Gladys with the code provided by matterjs-server
OpenThread indicates that the discriminator is: 1605
Whereas Gladys seems to indicate 6 :
Yet with the command :
avahi-browse -r _matterc._udp
it’s clearly 1605 :
2 Likes
I think I have some of the answers:
@pierre-gilles Do you have any thoughts? 
For me, I think we should develop the Bluetooth integration part and add an OTBR integration section for the Thread part
1 Like
While I think it’s very complicated to set up, I also think that if Gladys integrates this natively, it will be a game-changer against the competition 
2 Likes
I even think it’s becoming mandatory if you want to attract beginners, especially now that Matter and Thread are becoming the standard.
1 Like
I also tried to install Gladys on the same machine as OTBR and matterjs-server but I got the same result 
Thanks for all the investigation @prohand, that’s all very interesting
Regarding your issue, I don’t have an immediate answer; I see several possible avenues:
- Either matterjs-server and Gladys can’t communicate with each other (network configuration issue?)
- I see that matterjs-server uses matter.js 0.16.9, on the Gladys side we use 0.13.0, I’d be surprised if the Matter spec changed between these two versions, but maybe there’s an incompatibility…
@prohand for info, the creator of Matter.js (and of matter-js-server) is very responsive. I talk to him on Discord (apollon77), but he should also be active on GitHub.
Feel free to tell him about your issue 
Otherwise, we can always debug this together if you want.
Thanks for your reply
I’ll try to contact the creator of matter.js sometime this week on Discord to see if a spec has changed.
Is a matter.js update planned for Gladys?
Depending on the response, we’ll probably debug it together because I don’t have any leads left.
Otherwise, do you think we could implement an OpenThread border router as well as adding to the Thread and Matter networks via Bluetooth?
I meant more to tell him about your issue in general I should point out that he’s not French so you need to talk to him in English.
We can do it if needed
For now, we didn’t have a specific need to update it.
It takes quite a bit of testing time, so my philosophy is to prioritize stability, and to only update to safe versions (the most recent ones very often have bugs), testing extensively that nothing breaks.
That could come to Gladys, yes, but for now I admit I’m more of a spectator of the Thread ecosystem than an active participant on this point, because I don’t feel we’ve reached a reasonably good maturity of the dependency chain.
I invest time in a technology only when I have the guarantee that it’s fully stable, and that it won’t change over the coming years 
While Matter is completely stable, I get the impression that the Thread side of all the discussions on this subject is not ready yet — what do you think?
Besides, I’ve never tested it so you are definitely more of an expert than me on all these points!
I also wonder about the hardware: in the long run, won’t everyone have a Thread router at home? Which would make such development unnecessary.
I know that’s not the case for everyone today, but I wonder if, in the long run, everyone won’t have a Thread router at home (internet box, router, smart speaker, etc…) Among people I know, 100% already have a Thread router, but that might just be my circle.
Chez moi c’est l’inverse. Et je ne mettrais jamais de google home, Amazon Alexa ou Apple…
Donc je risque d’attendre longtemps avant de pouvoir utiliser mes capteurs matter over thread si je compte sur ces solutions.
J’avais acheté au depart une cle ethernet smlight zigbee et thread en pensant que thread allait être encore plus simple que le zigbee, mais je me rend compte que non, surtout si tu fais des installations perso…
1 Like
Je suis exactement dans le même cas !
Si j’ai pris Gladys c’est aussi pour le côté sécurité et local, pas pour mettre des sniffers de paroles connectés aux aspirateurs de données mondiaux.
1 Like
Thanks for your feedback! I’m in the Apple ecosystem, privacy-respecting and fully local, but indeed for those who are not on Apple currently the options are mostly with data sniffers
In the future I was thinking more about Wi‑Fi routers that will probably be Wi‑Fi + Thread.
Exactly, before implementing anything in Gladys someone from the community first needs to get this setup working
Otherwise, it just means it’s not mature yet.
I work on it when I have time
2 Likes
I’m in it too, almost 100% (the remaining % run on Linux ).
With an internal network on Ubiquiti UniFi, Thread will take a bit of time to arrive at my place, so for now I’m not ready to change my gear again (which works wonderfully) :slight.smile:
Besides, I’m not sure we’ll see routers (Asus, TP-Link, etc.) that are both Wi‑Fi and Thread anytime soon, at least not until they have a full Matter/Thread lineup to launch.
For TP-Link, for example, they have Matter/Wi‑Fi devices but you need their Tapo app to do the initial pairing. And otherwise they still talk about the Apple Home ecosystem, Google Home, Amazon Alexa and SmartThings.
We had already discussed that on another post about Matter/Wi‑Fi and the brands’ apps.
I bought Sonoff Matter/Wi‑Fi and didn’t need to go through their app to connect the devices to the Wi‑Fi network. However I did it with the Home app on my phone and it worked great (you just have to be on a 2.4GHz network only…).
Then I shared from Home to Gladys.
So I think Wi‑Fi router manufacturers won’t implement Thread anytime soon as long as they can play with (and keep) users within their software ecosystem.
De mon côté au contraire, quand on suit concrètement l’implémentation technique de tout ce que fait Apple, c’est très loin d’être du « privacy-washing », c’est concrètement incomparable à ce que fait Google (j’ai des dizaines d’exemples précis mais c’est pas le sujet ici 
)
Top merci beaucoup @_Will_71 !
Yes yes I understood
Also I think there’s not much missing for me to have a fully functional installation but with @_Will_71 we should manage since he’ll also take time to look
Do we have the possibility of a test image with the update to check whether that would solve my problem or not?
Yes I agree with you, for the moment Thread isn’t completely stable
On my side I have a somewhat atypical setup where I have multiple VLANs and my Apple devices are on a different VLAN than Gladys’s, so making Thread/Matter devices communicate from one VLAN to another isn’t simple.
That’s why I went for an installation with an OpenThread border router on the same VLAN as Gladys.
However I manage to make Gladys and HomeKit communicate without any problem
Even if I manage to add this device to my Apple TV for example and then it ends up duplicated in HomeKit. I don’t know if you see what I mean @pierre-gilles
The best would have been for Gladys to allow integration of a Matter device via Bluetooth but I’m not sure that’s what @pierre-gilles is looking for so as not to lose users.