Thank you for your interest in my problem… after following a multitude of leads… I have come to the conclusion that my dongle has a small issue… at best, the green LED flashes while the red LED stays on… I have therefore decided to buy a new key…
Thank you again for your support
Hello Despite the new ZBDongle-E key and the Gladys, MQTT and ZIGBEE2MQTT services all green with no error messages … I can’t find the « normal » functions in Gladys … (being able to operate a remote switch from my phone or other) … It seems there is no dialogue … and in the dashboard « no recent value »… Should I be patient during the reconnection?
Continuation of my misadventures… The new dongle connected to the Silabs firmware flashing program returns: Connection failed. The running firmware could not be detected. Make sure the USB port works and if you are using a USB extension cable, make sure the cable can transfer data. Unplug the Sonoff ZBDongle-E and plug it back in to reset and try again…
I bought this ZBDongle-E on Amazon… It’s going back there…
I am now tempted to get one from Domadoo (at least I might have someone to talk to in similar situations).
If you have the possibility of having an Ethernet dongle instead of a USB one, I recommend you take a SMLIGHT, several of us have one on the forum.
For my part, I have a SLZB-06M that works perfectly with an external zigbee2mqtt.
What I can’t say is whether the Ethernet dongles are already available in Gladys with a local installation of zigbee2mqtt, can someone confirm or deny this?
Thanks, I’ll check it out
Hello Following the advice of cicoud13, whom I thank…
I reconnected the ZBDongle-E from Amazon… and lan
Response: Zigbee2MQTT container error: u[2026-09-24 05:33:58] error: z2m: MQTT failed to connect, exiting... (Connection refused: Not authorized)
The MQTT broker refused the connection: not authorized. Check the username and password of your MQTT broker, as well as the access rights of this client, then save the configuration again.
After disabling and reactivating the service… I get: Zigbee2mqtt interface URL: http://192.168.1.123:12000
But for the moment nothing better… Have a good day everyone
Sorry, part of the copy-paste got into the first part of the text…
I’m really not good at this…
Hi Jean-Jacques,
Don’t worry, you didn’t break anything, and you’re doing great! I’ll summarize where we are, because there have been many leads in this thread.
The « unauthorized » error is fixed. It came from restoring your backup: it put the old MQTT service passwords back into Gladys, even though the service had been created on your new PC with different passwords. By disabling and then re-enabling the integration, you recreated this service with the correct passwords, and that’s why the Zigbee2mqtt interface address is now displayed. 
For the next steps, avoid restoring a backup again: it’s no longer necessary.
Keep your new key, don’t send it back! It works: everything was green in Gladys. If the update tool can’t read it, that’s not a problem. As long as Gladys doesn’t display a warning on the configuration page, you don’t need to update it.
The real issue now: your devices don’t know the new key yet. The Zigbee network is stored in the key itself. When you change the key, the devices don’t always reconnect automatically. Here’s what I suggest, in order:
I advise you to test with one device first, for example a relay, and let us know how it goes. If it gets stuck, a screenshot of the Zigbee2mqtt configuration page in Gladys will help us a lot.
And don’t apologize at all for the copy-paste, it happens to everyone 
Hello and thank you very much for your support
The key hasn’t been sent back yet, it’s still on the USB extension
I think I configured it correctly:
After a power outage of more than 10 minutes
The devices testing a motion detector that had been in testing for some time. There, I changed the batteries …
et a connected IKEA Tradfri plug for which I performed a re-pairing …
The other devices are still present but not active …
I hope this helps … Thank you
Hi Jean-Jacques,
Thanks for the screenshots, they are very clear and they help us a lot! Good news: your configuration is correct. All three lights are green and « Started », and your new key works. Your motion detector is communicating well: we can see it in the recent activity of Zigbee2mqtt. And you did well to put the key on the USB extension.
What you still need to do: on your second screenshot, Zigbee2mqtt only knows 2 devices, the detector and the IKEA outlet. Your other devices have not reconnected to the new key, and they won’t do it on their own. You need to re-pair them one by one, as you did for the outlet. It’s a bit long, but it’s the last step!
Here’s how to do it, the order is important:
For each device: in Gladys, in the Discovery tab of the Zigbee2mqtt integration, click on « Allow pairing », then put the device back in pairing mode (see its manual). When it’s done, remember to disable pairing.
For your IKEA outlet: the red « Delivery failed » messages mean that the key can’t reach it, probably because it’s too far away: for now, there is no other device to relay the signal. Plug it in the same room as the key, a few meters away, redo the pairing, then put it back in its place. Once paired, it will in turn serve as a relay for the other devices.
Normally, the re-paired devices resume their place in Gladys, with their scenes and your dashboard. To check, go back to the Discovery tab: if the device appears there as already added (or with an « Update » button), it’s good. If it appears as a new device, let us know before deleting anything.
Keep us updated, you’re almost there!
Thank you so much… It’s finally resolved thanks to the last precious advice… Thank you for the availability of everyone but especially of Pierre-Gilles…
And for your always encouraging and positive way of communicating…
A suggestion, perhaps utopian, but could an AI, properly instructed, not advise for problems like mine, certainly very simple but insurmountable without wise advice… and thus relieve the team…
Have a good Sunday everyone
Glad to hear it’s working 
Not as utopian as you might think: this AI already exists, it’s called Claude Opus 5.5!
Little secret: a good part of my messages here are written with its help, or even entirely by it
Don’t hesitate to ask it your questions directly, giving it as much context as possible (your configuration, error messages, screenshots). For this kind of problem, it often works very well. And if you’re stuck, the forum is always here!
Thanks regarding Claude Opus 5.5… is it available « within Gladys » or elsewhere?
It’s not integrated into Gladys; it happens on a separate site: you just need an account on https://claude.ai 
To respond to forum users, I use the « Claude Code » tab (on the web), connecting it to Gladys’s GitHub repository. This way, it has access to all the source code, and I give it this prompt:
This is what makes the difference: instead of responding generically, it reads the code to understand exactly how Gladys works. It is generally more precise than I am: it digs deeper, takes the time to check everything, and it is very fast. Its responses are often much more relevant than what I would write alone, so today I run almost all my forum messages through it.
