Having set up Gladys for the first time and used the “installation from Gladys” for the Zigbee2mqtt integration all is working well EXCEPT the connection to the Zigbee2mqtt container to see the network diagram does not work; neither does port 8080. There are no other containers running so there is not a port conflict and there is nothing in the logs to indicate a problem. So what have I not done or done incorrectly?
Hello @john and welcome to Gladys!
In the zigbee2mqtt integration, until everything is green, it won’t work:
Have you selected the correct USB port and the correct Zigbee USB stick?
Then I would advise setting 12000 for the port (that’s what I set at home to avoid identical port issues):
And did you start the service after saving the configuration?
Don’t hesitate to share your PC configuration and the model/reference of your USB stick.
You can also post a screenshot of the Configuration page of the zigbee2mqtt integration, I’ll be able to see more clearly.
Thanks for the response.
Everything appears to be working; Gladys is picking up ZIgbee devices, is collecting and displaying data - wonderful. And so easy to set up - unlike HomeAssistant!! However, the link that is shown above - “Zigbee2mqtt Interface URL: http://node-16:12001” is giving “ERR_CONNECTION_REFUSED”. I’ve tried changing the port number, saving and then disable/enable the service but the port number doesn’t change. I’ve tried accessing http://node-16:8080 from my browser and that gives the same error. When I look at the docker container for zigbee2mqtt it does not appear to be publishing any port, despite what it says in the configuration file. Anu ideas?
Best wishes
John Anderson
Good news for the config!
Have you tried changing node-16 to your Gladys’s IP address?
And then you directly put http://192.168.X.Y:12001 (well, the correct IP of your Gladys).
EDIT: @NoiZe also had access issues with the port and was able to resolve it: Use another port for Zigbee2MQTT dashboard? - #6 par NoiZe
I can’t change the “http://node-16:12001” on the Gladys implementation screen, but I have tried http://192.168.X.Y:12001 from my browser and still don’t get into zigbee2mqtt. I read the @NoiZe article and tried the ‘sudo ss -tunlp"‘ command and can’t see port 12001 nor can I see zigbee2mqtt in the list of processes, which adds to my theory that port 12001 is not being exposed.
I am currently running gladys on raspian OS lite on a Raspberry Pi 4 as a trial, but I’m going to move it to a mini PC running UBUNTU 24.04 server and I’ll see if that works.
‘docker ps’ also shows that zigbee2mqtt is not listening on any port
Regards
John Anderson
This was solution done by @NoiZe , let see if it works for you too.
By the way, with .X.Y I wanted to say that you should ping node-16 and get the IP address, not with X and Y. But if docker ps doesn’t show you z2m then it is not started.
Maybe after a reboot of your Pi4 it could appear.
Tried the reboot option, that didn’t work either. Gladys on the Rpi4 can find the Zigbee devices, and does all the good monitoring of data, it is just that when Gladys fires off the zigbee2mqtt container it either doesn’t set the port in the compose file or raspian OS ignores it. We’ll see!!
You can try to change the port in the file itself.
I did that too!!
Now here’s a thing; installed under docker wth UBUNTU 24.04 LTS and it works!! I can http://mynodename:12000 from my browser and can access zigbee2mqtt’s dashboard.
So my suggestion is that there is a problem with either Raspian OS or the zigbee2mqtt container for ARM.
Your thoughts?
Could be the case indeed.
Many thanks for the conversation and ideas
Best wishes
John Anderson
1 Like
I think we’ve found our culprits!
@john was your Raspbian 32-bit or 64-bit? because 32-bit
It was 64 bit - Debian 1:6.12.62-1+rpt1~bookworm (2026-01-19) aarch64