@mutmut I wanted to be sure everything works so I did a test on my development mini-PC at home, and it works fine!
I started 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 site modified with the correct image)
Then, I ran 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, the /root/matterbridge/docker_data volume you should change to the local path on your system), on my system the user is « root » so I just create a matterbridge folder:
Then in the Matterbridge interface (the URL is in the Matterbridge logs, on my system it’s http://192.168.0.99:8283/), I find the pairing code:
I copy-paste it into Gladys:
And then I have all the devices:
