It’s a section because otherwise it’s too long, but the last lines may be explicit.
So, first of all it would be safer if you modified your message to:
- remove your IP address which is visible to everyone (the second-to-last line)
- you can use code tags to make it easier to read: at the very beginning and at the end of your code you can use this marker: ```
As for your log, there is indeed an error; unfortunately I don’t know how to debug it:
Error: connect ECONNREFUSED xx.xx.xx.xx:9007
at TCPConnectWrap.afterConnect [as oncomplete] (node@pascal_sapin didn’t you configure your zigbee2mqtt container with a custom MQTT URL? From the z2m UI or manually in the configuration.yaml file?
Sorry but I don’t understand, I didn’t touch anything, I don’t know YAML configuration, could it be a port problem? The only thing I did was add a Wi‑Fi camera but it’s not compatible with RTSP or Gladys, and a USB repeater for the garden.
What is the brand of your dongle?
I see other people who have similar problems on the z2m GitHub, but it’s about extensions… that we don’t handle natively.
it’s a sonof zbdongle -P
it has always worked
There doesn’t seem to be any particular configuration for this dongle…
I’m running out of leads…
Have you tried the pro’s technique? Restarting the PC? 
yes I restarted the router, the Pi, the PC — everything that could be restarted, nothing, still the same message!
Don’t lose patience, we’ll figure it out… but it’s nice outside right now, so I’ll get back to it later 
lol yes I understand, I have time anyway, it’s raining here but no big deal, we have work outside, 33 ares of land, plenty to do lol
@pascal_sapin could you give me the list of files you have in the folder /var/lib/gladysassistant/zigbee2mqtt/z2m?
ls /var/lib/gladysassistant/zigbee2mqtt/z2m
I get this
pi@gladys:~ $ ls /var/lib/gladysassistant/zigbee2mqtt/z2m
configuration.yaml database.db log
coordinator_backup.json extension state.json
Actually I no longer have Zigbee data from my sensors either.
Perfect, it’s the « extension » that’s causing the problem!!!
Rename it, or move it
mv /var/lib/gladysassistant/zigbee2mqtt/z2m/extension \
/var/lib/gladysassistant/zigbee2mqtt/z2m/extension_bak
And tell me if that helps!
okay I’ll test this right away
mv /var/lib/gladysassistant/zigbee2mqtt/z2m/extension \
/var/lib/gladysassistant/zigbee2mqtt/z2m/extension_bak
mv: cannot move ‹ /var/lib/gladysassistant/zigbee2mqtt/z2m/extension › to ‹ /var/lib/gladysassistant/zigbee2mqtt/z2m/extension_bak ›: Permission denied
I don’t think this is good ???
Could we use the chat? It would be better if you have a little time.
Following a private chat with @pascal_sapin,
removing the folder /var/lib/gladysassistant/zigbee2mqtt/z2m/extension solved their problem.
The solution comes from Crash due to connection to external IP (Strato AG???) · Issue #17550 · Koenkk/zigbee2mqtt · GitHub.
Once the folder is deleted and the container restarted, everything returns to normal.
Thanks @guim31 for your contribution
@pascal_sapin if it happens again, keep us informed, and try to remember if you performed any specific actions on the zigbee2mqtt interface.
If we can reproduce it, we can fix it, or have it fixed.
If it appears for no reason, maybe a third party is messing with your instance… to check:
- that port 8080 is not publicly accessible on the internet
- that a member of your household / network isn’t causing trouble by accessing the z2m interface and, not being familiar with the application, clicking in the wrong places.
For your information, password access to the z2m application will be configurable from Gladys « soon ». Development is underway, along with other nice features
2 Likes
Now that you’ve done the teaser, we want to know more!! 
For your information, @AlexTrovato added in Gladys Assistant 4.23 a new setting in the Zigbee2mqtt integration: the model of the Zigbee dongle.
This can be selected during configuration, which allows configuring Zigbee2mqtt directly, without leaving Gladys 
The details of this release are in this article:
I’m closing this thread which was getting a bit long and a bit of a catch-all, now that the original problem is resolved
If you have further feedback / other bugs about Zigbee2mqtt, don’t hesitate to create another thread!
Thanks to @AlexTrovato for this development 
2 Likes