Hey everyone!
The Matter protocol is becoming more and more interesting — we’re finally starting to see stable and convincing devices on the market.
As I mentioned in my “Plans for 2025” live stream, I have high hopes for Matter and I think Gladys Assistant could benefit a lot from it.
In the long run, a single smart home protocol might take over, and if that’s Matter, it would greatly reduce the differences between Gladys and other platforms in terms of integrations. The main focus would then shift to user experience — which happens to be Gladys’ biggest strength!
Our Matter integration
I’ve been working on a Matter integration and I’ve integrated a few features.
Now, I’m looking for your feedback to help me integrate more devices!
I’ve published a custom Docker image with the Matter integration:
gladysassistant/gladys:matter-integration
What works
- Control and state feedback of binary devices (smart plugs, bulbs)
- Control and state feedback of Shutters
- State feedback from illuminance sensors
- State feedback from motion sensors
- State feedback on temperature sensors
You can use Matter as a “bridge integration” to help you integrate with devices not currently supported by Gladys, like Shelly devices, Tahoma Somfy.
You can use Matter with real Matter devices, like the Eve Energy Smart Plug, Eve Motion, or any Matter devices
How I launched Gladys and Matterbridge with the Matter integration
I launched Gladys like this:
sudo docker run -d \
--log-driver json-file \
--log-opt max-size=10m \
--cgroupns=host \
--restart=always \
--privileged \
--network=host \
--name gladys \
-e NODE_ENV=production \
-e SERVER_PORT=80 \
-e TZ=Europe/Paris \
-e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /var/lib/gladysassistant:/var/lib/gladysassistant \
-v /dev:/dev \
-v /run/udev:/run/udev:ro \
gladysassistant/gladys:matter-integration
(It’s just the docker run from the website, modified with the correct image.)
Then I launched Matterbridge like this:
sudo docker run --name matterbridge \
-v /root/matterbridge/docker_data/Matterbridge:/root/Matterbridge \
-v /root/matterbridge/docker_data/.matterbridge:/root/.matterbridge \
--network host --restart always -d luligu/matterbridge:latest
(Of course, replace /root/matterbridge/docker_data with your own local path depending on your system. On my test server, the user is root*, so I simply created a* matterbridge folder:)
Then, in the Matterbridge interface (the URL is in the Matterbridge logs — for me it’s http://192.168.0.99:8283/), I found the pairing code:
I copy-paste it into Gladys:
And after that, all my devices show up correctly:
If I add a device to Gladys:
I’m able to control it from my dashboard: