# Zigbee2MQTT, External Broker and configuration **URL:** \ **Category:** Configuration\ **Tags:** zigbee2mqtt\ **Created:** [April 3, 2024, 4:32pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-brocker-externe-et-configuration/8817 "2024-04-03T16:32:13Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [April 4, 2024, 7:13am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-brocker-externe-et-configuration/8817/2 "2024-04-04T07:13:49Z")
> [@McFlyPartages](#): > > The installation of Zigbee2MQTT installs a mosquitto folder with a new mosquitto.conf file and its values including port 1884? Why not connect directly to the existing container? The goal of this integration in its current operation is to make the very existence of Zigbee2mqtt completely forgotten. For the user, it’s just an integration that allows them to connect their Zigbee devices. The « technical » operation must be totally invisible, and the integration must be stable for years, without interruption. By totally separating the « Zigbee » behavior from the MQTT integration, we properly isolate the Zigbee integration, and if the user fiddles with the MQTT integration (adding a new broker, changing the MQTT password, etc…), it doesn’t break the Zigbee integration which runs on its own. I understand that coming from HA this may seem strange to you, but on the Gladys side it’s a totally different philosophy: we start from the user, not from the technology. > [@McFlyPartages](#): > > Impossible to modify Z2MQTT’s `configuration.yaml` without breaking the service. I just want to connect Z2MQTT to the external broker manually. Not possible? Mmm no, not possible, because you would have 2 Zigbee2mqtt… Gladys’s and HA’s, that cannot work. What you want is for Gladys to talk to the Zigbee2mqtt broker of HA, and that is not possible at the moment. > [@McFlyPartages](#): > > There is no function to properly remove the Mosquitto and Zigbee2MQTT integration (and probably others) If you disable the integration in the interface, normally it cleans the containers properly. ![Screenshot 2024-04-04 at 09.00.38](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/0/066b0796eb671423fd21268c5689d833eaf123ed.png) Indeed if you touch the CLI, Gladys thinks the containers have crashed and therefore restarts them at the next startup. > [@McFlyPartages](#): > > Do you have the same issues over there? Even though I know this is more for tinkerers, or maybe I don’t use best practices? I think you are the first in the community to test all these behaviors, because what you’re trying to do is very unique 😃 Nobody does CLI/file tinkering here, Gladys’s ambition is really to offer a product where everything is done in the UI and everything works without having to worry. **To do what you want, I see 3 options:** 1. Launch the Zigbee2mqtt integration in Gladys, and import your entire HA config into Gladys’s Zigbee2mqtt. This would mean completely disconnecting your Z2M from HA, and plugging your dongle into Gladys. 2. Wait for this development to be developed ( [Pouvoir utiliser un Zigbee2mqtt externe dans Gladys](https://community.gladysassistant.com/t/pouvoir-connecter-un-z2mqtt-externe-a-gladys/8790) ), unfortunately I can’t guarantee a date, it’s a feature that ultimately has few requests and I’m personally focused on training at the moment 🙂 3. Test the development from 2) in its current state. As I said in another thread, the development has already been started (Cf [PR Github](https://github.com/GladysAssistant/Gladys/pull/1872)) then paused because the dev had a child and is less available 😃 Nevertheless, I tested the current development and it seems to me that it already worked (the UI is actually a work in progress though, and not everything works completely…) If you’re interested in testing, I restarted this morning a build of this development on the Docker tag: ```auto gladysassistant/gladys:z2m-setup-wizard ``` ⚠⚠⚠ **I guarantee nothing, do not run this development on your prod** ⚠⚠⚠ I know all this may seem frustrating, it’s frustrating for me too to see you struggle because for all the other Gladys users, using Z2M is one click and it works great ^^ --- _[View the full topic](https://community.gladysassistant.com/t/zigbee2mqtt-brocker-externe-et-configuration/8817)._