A bit off-topic @cce66 
I invite you to create a separate thread so this one doesn’t go off in all directions.
I tried this fix(zigbee2mqtt): Redeploy zigbee2mqtt container in case of USB dongl… · GladysAssistant/Gladys@eee427c · GitHub
I’m building a Docker image to test in real-world conditions
@cicoub13 Well done, however I don’t think this will work, you’re missing one more:
dockerContainers = await this.gladys.system.getContainers({
all: true,
filters: { name: [containerDescriptor.name] },
});
once you’ve removed the container.
Otherwise, after that it won’t restart the container since it exists according to the first request
Most importantly, don’t pin the version, otherwise we will never benefit from the developments in future z2m releases — it would be a shame to miss out 
@pierre-gilles specific topic created 
@spenceur
Good catch, it’s added.
However, devices is not returned in the listContainers function (here).
Can I create a new function inspectContainer?
@cicoub13 Yes pour inspectContainer
1 Like
Good evening.
I have a test image fixing this bug here => cicoub13/gladys:z2m-usb-change
Tested on my machine and working, but I’m afraid there may be many possible combinations and I can’t test in development (no network=host mode on mac).
And the pending PR Feat zigbee2mqtt usb change by cicoub13 · Pull Request #1905 · GladysAssistant/Gladys · GitHub
@pierre-gilles @lokkie @cicoub13
I don’t know if this is normal but this weekend I rebuilt my NUC BT3Pro to install a clean, up-to-date version of Linux Lite
I reinstall everything then bring Gladys back up, I do a Gladys restore and everything is ok
then I bring up lokkie’s test image for node-red; I can access it fine, everything ok I go to the integrations page zigbbe2mqtt ok mqtt ok
I go back to Gladys — no more zigbee2mqtt nor mqtt — and then I try to restart the services mqtt zigbbe2mqtt and nothing works
I stop @lokkie’s Gladys image but that changes nothing when looking at the container settings in Portainer
I end up with this
Apparently this created a problem by having launched @lokkie’s image with these settings and afterwards the normal Gladys instance apparently can’t find its bearings anymore!
After stopping @lokkie’s image then removing the zigbee2mqtt and mqtt containers and their volumes with Portainer, I reactivate the zigbee2mqtt and mqtt services in Gladys and everything works again!
I think you got the wrong topic..
1 Like
Well, yes and no — because in this case my key seemed to no longer work or was recognized but the service remained down, so I thought
I don’t know if @lokkie’s test container overwrites those parameters in this case; in any case everything came back after deleting the container AND the associated volume, so by restarting the activation of the
Thanks @cicoub13 for the development, I’ll take a look and I’ll keep you posted 
@cce66 You’re mixing a lot of things: Node-RED test image, Gladys Plus backup, etc… be careful with your experiments though
I think we’ll stay focused on this topic here and on the corrective PR from @cicoub13.
If you ever have bugs to report related to production Gladys, create a specific topic. If you found a bug in a test image, reply in the test image’s topic.
If you mix everything together, it’s the best way to create confusion about PRs where there’s no problem, or conversely to miss a problem!
No, no, I’m not senile yet… well I think at least I hope! 
More seriously, I also have a Sonoff P dongle and I also had /dev/ttyACMO then rebooted the NUC and then dongle /dev/ttyUSB with dongle detected service active but instead of green checkmarks there were red crosses
and as I wrote in the previous message I had both instances running
gladys with the key recognized service active but red crosses
gladys-test-nodered:8010 with the key recognized service active but a green check
in both cases the volumes pointed to the directory /var/lib/gladys-test-nodered, impact or no impact on the bug or @cicoub13’s config I’m only reporting what I observed!
I just wanted to bring this additional info regarding this parameter change in case @cicoub13 also tested @lokkie’s image, I know there’s an additional bug related to Synology but since there are similarities between what I encountered and the issue this topic is about, I thought « you never know » and if it’s not the case well how would we know if we don’t mention it!!! And at first I thought my install or my key was corrupted, it’s thanks to Portainer that I saw this incorrect volume parameter in Gladys. 
PS: I’ll raise the info in the topic dedicated to the Node-RED integration by @lokkie for the record although I think he saw it 
By the way it’s the same for the eclipse-mosquitto container
[quote=« cicoub13, post:28, topic:8365 »]
I have a test image that fixes this bug here => cicoub13/gladys:z2m-usb-change
Tested on my machine and working, but I’m afraid there
I tested @spenceur’s case in real life (dongle port change and automatic container restart). Nothing else
Ok, that seems good to me, I trust you if you’ve run tests!
I want to merge your PR, however there are 2 files that are not related to the PR ( Feat zigbee2mqtt usb change by cicoub13 · Pull Request #1905 · GladysAssistant/Gladys · GitHub )
It’s fixed 
1 Like
It’s merged!
Thanks for the PR 
The bug where changing the USB port was not reflected in Zigbee2mqtt has been fixed and released in Gladys Assistant 4.30!
Thanks @cicoub13 for the fix 
1 Like