Hello everyone,
===== My Context =====
I adopted Gladys by installing it on a Raspberry 4 (bookworm + Deskpi Pro case + 120GB SSD)
I deployed the Switchbot integration to collect six “Meter plus” probes
Everything works perfectly.
To continue my experiments, I bought Matter devices from Ikea and deployed the MaterBridge extension
My Matter over Thread devices: a KAJPLATS bulb, a GRILLPLATS outlet, and two BILRESA remotes
To have a “Border Router Thread,” I deployed OpenThread in a Docker container and flashed an nRF52840 dongle (MakerDiary MDK USB Dongle) with the RCP firmware (openthread/ot-nrf528xx).
All necessary shell scripts and explanations are in the public repository “gladys_openthread” on GitHub
========= The Situation =========
I have a Gladys instance with MatterBridge deployed.
I have a functional OTBR (see the validation report)
I cannot “commission” my Ikea Matter devices
========= Why? =========
A Matter over Thread device (GRILLPLATS, KAJPLATS, BILRESA) receives its Thread identifiers during Matter commissioning, which begins with an encrypted exchange over Bluetooth LE (PASE) between the device and a commissioner.
This is exactly what Gladys cannot do, and what the OTBR cannot do either.
========= Solution? =========
My readings of documentation, forums, and discussions with Mistral lead me to the solution: chip-tool
I found this:
- chip-tool is the reference tool for the Matter project but is experimental: it works, it’s documented, it’s the path used by the Gladys community, but you’re off the beaten track.
- The 4 pairings must be done one by one, device by device (pairing mode on each).
- Once the devices are in Gladys, you will need to keep chip-tool installed (or at least its storage) for future needs (recommissioning after factory reset).
Has anyone here already experimented with chip-tool?
Thanks in advance for your help.
Olivier