So, it’s been 24 hours and, being impatient by nature, I can’t help but leave a comment.
For now, it tells me that the image is up to date.
I pull this image from Docker Hub: gladysassistant/gladys:v4
Do I need to change something? Is the v4 too much for the day when we want to upgrade to v5?
In Gladys, what version are you on? (Settings => Systems => Version)
The v4 is not excessive, and if one day we move to v5, it will be a « breaking » update, so we must not automatically update the clients as it will break everything for them ^^
But we are not at risk of moving to v5 
I am on v4.7.3
Yes, I was thinking maybe in 10 years on the same instances, you never know!
So I don’t know if I don’t update because it doesn’t check the Docker Hub and therefore I have to do something on the Unraid side or if it’s on the Gladys side…
Either we make no breaking changes in the next 10 years, and we’ll stay on v4 (I’d say that’s great)
If we ever want to change major versions, it’s necessarily that we break something and in that case it makes sense to change the tag.
Are you using watchtower? How does the Unraid UI work?
I don’t use Watchtower, it’s not available on unRAID.
Does Watchtower update all the containers on the host or only those that are designated to it?
I can port Watchtower to unRAID, it’s particularly easy, is it worth it?
After that, on the UI, I don’t know if « up to date » should be indicated by a configuration or something else, I’ll check.
Both are possible, you can pass the list of containers to update as arguments to watchtower. By default, it updates everything.
That’s something to see indeed, I couldn’t help you with that, but it’s good to know!
On UNRAID, you have a plugin that can update the containers you choose at the frequency of your choice. (I don’t remember the name, but something obvious like « Unraid docker auto-updater »)
So it was actually quite simple to update:
Advanced View → force update and that was it. I’ll still deploy Watchtower on unraid because it’s not overly difficult, but after that, I don’t think I’ll enable all available options.
For information, I resumed work this afternoon on Unraid/Synology compatibility.
I am working on this PR for those interested:
I started a VM and I am doing my tests inside it.
This PR modifies the Zigbee2mqtt integration and the MQTT integration at the same time, with the aim of being able to use a custom volume on the host side 
I will keep you informed when I have an image to test.
I’ve built a fix (dev, not prod), available on the following Docker tag:
gladysassistant/gladys:fix-zigbee2mqtt-get-container-id
I’m looking for testers with custom installations to install this image and see if it resolves the issue for launching the Zigbee2mqtt integration and the MQTT integration.
I’m also looking for « classic » testers to verify that it hasn’t broken normal functionality
The image can be tested like this for example:
--log-opt max-size=10m \
--restart=always \
--privileged \
--network=host \
--cgroupns=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:fix-zigbee2mqtt-get-container-id```
To test with a custom install, you need to modify the volume (this line: `-v /var/lib/gladysassistant:/var/lib/gladysassistant \`) to set the host directory you want to use :)Great!
I’ll test this on my side on unraid tonight
It’s incredible, it works perfectly, it’s really great!
Super job!
You’re talking about Gladys Plus or did you get the topic mixed up with Unraid? 
Thanks anyway!
I made a mistake with unraid, too many gladys tabs open!
So it works great with Unraid
I just moved your response to the Unraid topic so that it is readable for everyone.
Great I will merge tomorrow then.
After some thought, my last point is that Zigbee2Mqtt uses port 8080, which is very well-known and could probably be used on the user’s machine and cause issues as a result…
What do you think?
If I’m not mistaken, 8080 is the default port for Sabnzbd (and probably others, but less known), which is very widespread… So if a user already has Sabnzb installed, the installation of z2m will indeed fail.
Likewise, it is the default port for Keycloak, less used but it’s still a problem.
@jgcb00 What would you recommend for port 8080? An environment variable that you would define in the Unraid template?
For this « issue » with the port, it could be addressed by creating a network on Docker and placing Gladys with the other Docker containers. We stop hitting port 8080 on the machine, but we only go internally on the Docker side.
And if the need is potentially to check the logs of z2m, we can also assign a random port above 49XXX (the ports that are said to be « free »), right?