# Zigbee2mqtt: Docker test image based on Gladys v4 **URL:** \ **Category:** Développement\ **Created:** [November 15, 2020, 10:41am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746 "2020-11-15T10:41:16Z")\ **Posts on this page:** 20\ **Page:** 9
**Author:** ![damalgos](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/d/e274bd/32.png) [@damalgos](https://community.gladysassistant.com/u/damalgos)\ **Post date:** [January 31, 2021, 6:01pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/165 "2021-01-31T18:01:25Z")
Hello, Finally, I am going back on what I said 😃 I started from scratch and for now, the temperature sensor + switch are working well 🙂 As for the wireless switch (double), it is seen but not taken into account. I will look into adding the integration of this one. ```auto 2021-01-31T19:01:07+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x00158d0002d7b79e, feature action not found. 2021-01-31T19:01:07+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x00158d0002d7b79e, feature click not found. 2021-01-31T19:01:07+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x00158d0002d7b79e, feature linkquality not found. 2021-01-31T19:01:07+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x00158d0002d7b79e, feature voltage not found. ``` For my devices (all from Xiaomi) 🙂 ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [January 31, 2021, 7:14pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/166 "2021-01-31T19:14:29Z")
> [@VonOx](#): > > I already have a container named zigbee2mqtt. I’ve modified the container names to make them unique: [fix(zigbee2mqtt): Containers' names · cicoub13/Gladys@6d916a4 · GitHub](https://github.com/cicoub13/Gladys/commit/6d916a44fe7a8970bdcd0b239c93b80664947e12) I’ll let you know when I push a new image 🐋 > [@VonOx](#): > > Another thing to add to the to-do list: the ability to specify an MQTT server if you don’t want Gladys to handle that part. I’ve added it to the list of things to do above 👌 > [@damalgos](#): > > Regarding the wireless switch (double), it is seen but not taken into account. I will look into adding the integration of this one. Yes, the device list is here: [https://github.com/cicoub13/Gladys/tree/zigbee2mqtt-service/server/services/zigbee2mqtt/model](https://github.com/cicoub13/Gladys/tree/zigbee2mqtt-service/server/services/zigbee2mqtt/model) You can contribute (I’ve added you to the repository) ---
**Author:** ![damalgos](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/d/e274bd/32.png) [@damalgos](https://community.gladysassistant.com/u/damalgos)\ **Post date:** [January 31, 2021, 7:20pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/167 "2021-01-31T19:20:15Z")
> [@cicoub13](#): > > You can contribute (I added you to the repository) Oh great thanks I will add that ---
**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:** [February 1, 2021, 1:02pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/168 "2021-02-01T13:02:40Z")
5 messages have been merged into an existing topic: [Zigbee2mqtt - Debug](https://community.gladysassistant.com/t/zigbee2mqtt-debug/6080/3) ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 2, 2021, 7:46am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/169 "2021-02-02T07:46:05Z")
> [@VonOx](#): > > I already have a container named zigbee2mqtt. I pushed a new image with container names clean for Gladys. Could you try again? I still think you’ll have an issue with port 1884 already in use on your machine ☹ ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 2, 2021, 8:57am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/170 "2021-02-02T08:57:33Z")
1883 by default so that should work, I’ll test it tonight ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 2, 2021, 9:39am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/171 "2021-02-02T09:39:00Z")
> [@cicoub13](#): > > I pushed a new image with clean container names for Gladys Are you sure? ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/a/a5d672cf2b42e32440df641667e30560417acfc0.png) I have no zigbee2mqtt container that was created ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/f/f367a2801f13c8111a8085dc72165de6aa93969d.png) I stopped my production container ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 2, 2021, 10:17am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/172 "2021-02-02T10:17:25Z")
Yes, the containers are now called: - `gladys-zigbee2mqqt` - `gladys-zigbee2mqqt-mqtt` Be careful to clean up the containers (in the previous command, I suggested creating the container to test with the name `gladys-zigbee2mqqt` and this can conflict with the new containers… I rewrote the command with the name `gladys-dev-zigbee2mqtt`) ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 2, 2021, 10:31am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/173 "2021-02-02T10:31:09Z")
Oh, I just figured it out, it’s the name of the container with your image 😅 of course the name is already taken. ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 2, 2021, 8:27pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/174 "2021-02-02T20:27:05Z")
Display proposal for the Zigbee2MQTT Configuration page On mobile: ![Capture d’écran 2021-02-02 à 21.25.01](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/3/3e49d8c8a7efc697bc35e2c0d7965eb5a7b2cc78.png) On tablet: ![Capture d’écran 2021-02-02 à 21.25.09](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/2/2d47ddbbf124cbbb321f01c108b16679bf83cbb2.png) The computer version remains the same ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 2, 2021, 9:02pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/175 "2021-02-02T21:02:02Z")
I confirm​😁 « dead » 💀 😱 ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 3, 2021, 9:14am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/176 "2021-02-03T09:14:27Z")
@VonOx I fixed your existing Docker issue and pushed an image 🙂 Don’t forget to delete all the old containers (`gladys-zigbee2mqtt-mqtt` and `ga-zigbee2mqtt`) ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 3, 2021, 2:37pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/177 "2021-02-03T14:37:34Z")
Yes it works (the containers are created) I discovered another bug but I think it’s Gladys and not the z2m service * * * I had created the 1 house and a room. To test, I assigned all discovered devices to this same room. To make it cleaner, I deleted this room and created others ( big mistake 😃 ) Impossible to assign what was discovered to a new room 🙂 - In the discover part I cannot edit the room (already created), by the way if they are already created they should not appear on this tab? ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/d/dc688f5e2504e2edb8a58f12979fbfcfb2250457.png) - In devices, well there’s nothing left ^^ ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/7/7ee065213458af42f05e5a4edb025ce41a7c5b96.png) I messed everything up but in my opinion this room story is likely to happen again. There must be a check on Gladys side (do not delete a room if devices are linked) and on the service side I should be able to edit. I also had to recover my database file (zigbee2mqtt) because it was impossible to join the network, I think that’s my dongle. To be continued 🙂 … ---
**Author:** ![Tlse-vins](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/tlse-vins/32/6054_2.png) [@Tlse-vins](https://community.gladysassistant.com/u/Tlse-vins)\ **Post date:** [February 3, 2021, 2:59pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/178 "2021-02-03T14:59:12Z")
> [@VonOx](#): > > I deleted this room I didn’t think that was possible. Indeed, if there are devices in a room, it should be prevented from being deleted. ---
**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:** [February 3, 2021, 6:00pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/179 "2021-02-03T18:00:59Z")
> [@VonOx](#): > > I had created the first house and a room. > To test, I assigned all discovered devices to the same room. > To make it cleaner, I deleted this room and created others (big mistake 😃) Ah! This is indeed related to the current operation of Gladys. When you delete an entity in Gladys 4, all entities that depend on it are deleted. It’s true that in the case of devices/rooms, this doesn’t make much sense. Two options: - Prevent the user from deleting the room as long as there are devices inside - Update all devices that are in the room to be deleted, and remove their association with the room What do you think? ---
**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\ **Post date:** [February 3, 2021, 6:16pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/180 "2021-02-03T18:16:48Z")
Remove ownership, it’s less restrictive for the user PS: I just reread myself and it’s a disaster, sorry to those who read me for the mistakes. ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 3, 2021, 6:31pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/181 "2021-02-03T18:31:17Z")
Remove ownership (with a message before « All devices linked _to_ this room… ») ---
**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\ **Post date:** [February 3, 2021, 6:47pm UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/182 "2021-02-03T18:47:11Z")
I’m also for removing ownership but keeping the equipment! It makes more sense and is less frustrating if there were 10 pieces of equipment in a room 😅 ---
**Author:** ![lmilcent](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/lmilcent/32/7023_2.png) [@lmilcent](https://community.gladysassistant.com/u/lmilcent)\ **Post date:** [February 5, 2021, 9:24am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/183 "2021-02-05T09:24:08Z")
Hello, I think I found a bug. My smart plug is detected by Zigbee2mqtt but not displayed in Gladys. I checked, the model is officially supported by the Zigbee2Mqtt project: [Lonsonho 4000116784070 control via MQTT | Zigbee2MQTT](https://www.zigbee2mqtt.io/devices/4000116784070.html) Zigbee2Mqtt logs: ```bash Zigbee2MQTT:info 2021-02-05 09:18:30: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"99274c7","coordinator":{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20201026,"transportrev":2},"type":"zStack3x0"},"log_level":"info","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.17.1"}' Zigbee2MQTT:info 2021-02-05 09:18:34: MQTT publish: topic 'zigbee2mqtt/0x60a423fffe685063', payload '{"current":0.5,"energy":3.91,"linkquality":111,"power":81,"state":"ON","voltage":211}' Zigbee2MQTT:info 2021-02-05 09:18:38: MQTT publish: topic 'zigbee2mqtt/bridge/config/devices', payload '[{"dateCode":"20201026","friendly_name":"Coordinator","ieeeAddr":"0x00124b0021cc41df","lastSeen":1612516718278,"networkAddress":0,"softwareBuildID":"zStack3x0","type":"Coordinator"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d00044e9780","hardwareVersion":1,"ieeeAddr":"0x00158d00044e9780","lastSeen":1612516457300,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":6910,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20161128","description":"Aqara door & window contact sensor","friendly_name":"0x00158d0003f26e95","hardwareVersion":2,"ieeeAddr":"0x00158d0003f26e95","lastSeen":1612516597980,"manufacturerID":4151,"manufacturerName":"LUMI","model":"MCCGQ11LM","modelID":"lumi.sensor_magnet.aq2","networkAddress":48897,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20161128","description":"Aqara door & window contact sensor","friendly_name":"0x00158d0003173fdd","hardwareVersion":2,"ieeeAddr":"0x00158d0003173fdd","lastSeen":1612515745207,"manufacturerID":4151,"manufacturerName":"LUMI","model":"MCCGQ11LM","modelID":"lumi.sensor_magnet.aq2","networkAddress":28257,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d0004843eb4","hardwareVersion":1,"ieeeAddr":"0x00158d0004843eb4","lastSeen":1612516353652,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":59336,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d000460bf42","hardwareVersion":1,"ieeeAddr":"0x00158d000460bf42","lastSeen":1612516094548,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":45788,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"","description":"10A UK or 16A EU smart plug","friendly_name":"0x60a423fffe685063","hardwareVersion":1,"ieeeAddr":"0x60a423fffe685063","lastSeen":1612516714348,"manufacturerID":4098,"manufacturerName":"_TZ3000_rdtixbnu","model":"TS0121_plug","modelID":"TS0121","networkAddress":42938,"powerSource":"Mains (single phase)","type":"Router","vendor":"TuYa"}]' Zigbee2MQTT:info 2021-02-05 09:18:38: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":[{"dateCode":"20201026","friendly_name":"Coordinator","ieeeAddr":"0x00124b0021cc41df","lastSeen":1612516718287,"networkAddress":0,"softwareBuildID":"zStack3x0","type":"Coordinator"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d00044e9780","hardwareVersion":1,"ieeeAddr":"0x00158d00044e9780","lastSeen":1612516457300,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":6910,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20161128","description":"Aqara door & window contact sensor","friendly_name":"0x00158d0003f26e95","hardwareVersion":2,"ieeeAddr":"0x00158d0003f26e95","lastSeen":1612516597980,"manufacturerID":4151,"manufacturerName":"LUMI","model":"MCCGQ11LM","modelID":"lumi.sensor_magnet.aq2","networkAddress":48897,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20161128","description":"Aqara door & window contact sensor","friendly_name":"0x00158d0003173fdd","hardwareVersion":2,"ieeeAddr":"0x00158d0003173fdd","lastSeen":1612515745207,"manufacturerID":4151,"manufacturerName":"LUMI","model":"MCCGQ11LM","modelID":"lumi.sensor_magnet.aq2","networkAddress":28257,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d0004843eb4","hardwareVersion":1,"ieeeAddr":"0x00158d0004843eb4","lastSeen":1612516353652,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":59336,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"20170627","description":"Aqara human body movement and illuminance sensor","friendly_name":"0x00158d000460bf42","hardwareVersion":1,"ieeeAddr":"0x00158d000460bf42","lastSeen":1612516094548,"manufacturerID":4151,"manufacturerName":"LUMI","model":"RTCGQ11LM","modelID":"lumi.sensor_motion.aq2","networkAddress":45788,"powerSource":"Battery","softwareBuildID":"3000-0001","type":"EndDevice","vendor":"Xiaomi"},{"dateCode":"","description":"10A UK or 16A EU smart plug","friendly_name":"0x60a423fffe685063","hardwareVersion":1,"ieeeAddr":"0x60a423fffe685063","lastSeen":1612516714348,"manufacturerID":4098,"manufacturerName":"_TZ3000_rdtixbnu","model":"TS0121_plug","modelID":"TS0121","networkAddress":42938,"powerSource":"Mains (single phase)","type":"Router","vendor":"TuYa"}],"type":"devices"}' ``` When I manually turn off the plug: ```bash Zigbee2MQTT:info 2021-02-05 09:24:34: MQTT publish: topic 'zigbee2mqtt/0x60a423fffe685063', payload '{"current":0.22,"energy":3.92,"linkquality":114,"power":22,"state":"ON","voltage":212}' Zigbee2MQTT:info 2021-02-05 09:24:36: MQTT publish: topic 'zigbee2mqtt/0x60a423fffe685063', payload '{"current":0.22,"energy":3.92,"linkquality":126,"power":22,"state":"OFF","voltage":212}' Zigbee2MQTT:info 2021-02-05 09:24:44: MQTT publish: topic 'zigbee2mqtt/0x60a423fffe685063', payload '{"current":0.22,"energy":3.92,"linkquality":105,"power":22,"state":"ON","voltage":212}' ``` We can see that the information is sent to Gladys, which does not display it in the interface. Gladys logs: ```bash 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature current not found. 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature energy not found. 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature linkquality not found. 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature power not found. 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature state not found. 2021-02-05T10:27:34+0100 handleMqttMessage.js:87 () Zigbee2mqtt device 0x60a423fffe685063, feature voltage not found. ``` ---
**Author:** ![cicoub13](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/cicoub13/32/4482_2.png) [@cicoub13](https://community.gladysassistant.com/u/cicoub13)\ **Post date:** [February 5, 2021, 10:01am UTC](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746/184 "2021-02-05T10:01:59Z")
> [@lmilcent](#): > > My connected outlet is detected by Zigbee2mqtt but not displayed in Gladys. You need to declare each device and its associated features in the code here [https://github.com/cicoub13/Gladys/tree/zigbee2mqtt-service/server/services/zigbee2mqtt/model](https://github.com/cicoub13/Gladys/tree/zigbee2mqtt-service/server/services/zigbee2mqtt/model). I think your outlet is not listed there. I don’t know if there is another way to work (automatic detection). [Previous page](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746.md?page=8) [Next page](https://community.gladysassistant.com/t/zigbee2mqtt-image-docker-de-test-basee-gladys-v4/5746.md?page=10)