You may have interference between your Zigbee network and your Wi-Fi network.
Yes, as I was saying to @jean_bruder, for me Zigbee is a real pain in the home setup: I have 4 indoor Wi-Fi antennas + 3 outside and Zigbee disconnects all the time even with plugs located 2/3m away. Some devices, however, have no issues…
A bit annoyed when I see that it works perfectly for the majority ^^ but I’ve gotten used to it!! I do a mix, then, with what works!! :sweat_sm
Good evening @Hizo I’d be happy to make a tutorial, but that would go against the recommended practice proposed by @pierre-gilles. IMHO, it would be better to evolve Gladys in that direction so as not to start tinkering and going off in all directions: the developers of this project demonstrate every day their commitment and their willingness to advance Gladys to make it suitable for as many people as possible 
I think it’s always good to have a fallback option; for the moment Gladys doesn’t allow it, so it’s worth having some explanations if we end up in that situation.
Zigbee est sur le canal 11 par défaut Zigbee network | Zigbee2MQTT
Selon la box internet voir si il est possible d’éviter ce canal (sur les Freebox c’est en automatique par défaut) ou le modifier dans le paramétrage du fichier configuration.yaml
Il y a également
Before going into detail, it is worth reminding that in your home automation installation, it is strongly recommended to keep your Zigbee dongle sufficiently far from your box/router WiFi, but also from your home automation box depending on the quality of its electronics. On Pi4s, the USB 3 ports are not well shielded and directly disturb your Zigbee coordinator. This can be avoided by adding a USB extension cable or a powered USB hub. So if you have Zigbee, WiFi or Bluetooth transmitters/receivers, you should, as much as possible, keep them away from each other.
From the radio signal side, the ideal is to avoid overlap between the WiFi channel and the Zigbee channel.
You therefore need to take into account the bandwidth used by your WiFi channel so as not to overlap your Zigbee channel. Except that in practice it’s not necessarily so simple because there can be constraints.For WiFi, devices are capable of using all channels, but for Zigbee, some manufacturers have locked their products to a single Zigbee channel (Legrand on channel 11 only, Livolo on channel 26 only), so you need to be careful about the Zigbee hardware you use.
For Zigbee, the range is less than WiFi, so there’s little risk of a neighbor’s Zigbee interfering with yours… but with the neighbor’s WiFi, it’s less certain. It depends on the distance between dwellings.
C’est vrai qu’il est pratique d’avoir l’installation et le démarrage des containers (zigbee2mqtt, mqtt, node-red) en automatique pour les newbies autant il serait bien d’avoir la possibilité de lier Gladys à un existant juste en entrant les paramètres (IP, port, identifiants) de ces containers !
Yes, I’d welcome any PR on the topic to add the ability to connect to an external broker
There was an initial PR proposal by @AlexTrovato that didn’t come to fruition due to lack of time. The PR is on GitHub; if anyone wants to pick up the development I’ll gladly merge it!
There — I finally took the time to change the channel (switched to channel 26 / doesn’t overlap any Wi-Fi channel) and re-pair my devices (very simple, by the way, didn’t even need to rename) and…
I’m thrilled and I highly approve the simplicity of integration/use (15 devices). Everything works perfectly and even some devices that I couldn’t pair on channel 11 are now integrated. The mesh is amazing for improving range; I can even reach my building located 20 m away (device at 25 m). I’m thinking of installing an outlet at its entrance to improve quality, but I’ll be able to do without my 2nd Zigbee stick!!
@Terdious what would be great is to be able to modify this value from Gladys in the zigbee2mqtt integration afterwards, if that’s even possible, you did it from the zigbee2mqtt interface, I suppose?
hello, it would be nice if you could make a short tutorial to explain how and with what to carry out this channel change?
Indeed, being able to avoid multiple interfaces and control everything from Gladys would be really cool 
You already know @pierre-gilles’s answer: Feature request 
You need to go through the Zigbee interface « IP gladys:8123 »
 using two additional LidlBox units (currently on sale for €9.90) to my existing Zigbee network. The LidlBoxes are connected to the IP network using powerline adapters. To tie it all together, a Zigbee2MQTT container for each LidlBox and a single MQTT container to which the information is forwarded. It’s super convenient, since there’s a good distance between the buildings, but in the end everything appears unified in Gladys
Have a nice evening,
Jean
Hello @jean_bruder,
I’m interested in your setup, I have a chicken coop that I would like to control with Glad
Hello @Einstein8854,
The LidlBox is not supported by Gladys, as indicated in plenty of documents: Gladys natively relies on a USB dongle. I had tried to hack it that way to use the LidlBox by directly modifying the Z2M configuration files under Gladys, but… it’s not great 
A very handy feature was introduced as a result (thanks to @pierre-gilles and the developers): the ability to use an external MQTT module, which is what I do:
That’s it for Gladys.
Aside from that, I have an MQTT container declared under Gladys (mqtt://mqtt:1833), and as many Z2M containers as LidlBoxes deployed and connected to my local network. The configuration is adapted for each one regarding the LidlBox address on the network. Don’t forget to change the Web UI port, default 8080.
Configuration of the MQTT and Z2M containers:
For Mosquitto (MQTT):
For Z2M:
And the configuration specific to this Z2M container (in the data folder):
Regarding the LidlBox, it is modified following the tutorial given above, which just needs to be adapted to the latest firmware version:
- retrieve the « root » password via a terminal connected directly to the LidlBox,
- modify the initialization scripts while still connected directly: the binaries and scripts have changed, so you need to adapt a bit…
- flash the EZP firmware remotely this time via SSH.
That’s the big picture — it’s not too complicated. I hope this can help. If not, feel free to let me know
Thank you very much for sharing @jean_bruder, it’s very interesting and I think it will help people
I shared it on Twitter !