# Docker Zigbee2MQTT error

**URL:** <https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475>\
**Category:** Configuration\
**Created:** [August 11, 2021, 10:18am UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475 "2021-08-11T10:18:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hizo](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/h/51bf81/32.png) [@Hizo](https://community.gladysassistant.com/u/Hizo)\
**Post date:** [August 11, 2021, 10:18am UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475/1 "2021-08-11T10:18:43Z")

</div>

Hello,

I am having an error with Zigbee2MQTT.

```bash
docker logs gladys-z2m-zigbee2mqtt
Using '/app/data' as data directory
Zigbee2MQTT:info 2021-08-11 10:14:29: Logging to console and directory: '/app/data/log/2021-08-11.10-14-27' filename: log.txt
Zigbee2MQTT:info 2021-08-11 10:14:29: Starting Zigbee2MQTT version 1.19.1 (commit #9bd4693)
Zigbee2MQTT:info 2021-08-11 10:14:29: Starting zigbee-herdsman (0.13.111)
Zigbee2MQTT:info 2021-08-11 10:14:32: zigbee-herdsman started
Zigbee2MQTT:info 2021-08-11 10:14:32: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210120,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info 2021-08-11 10:14:32: Currently 9 devices are joined:
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d0003d43a15 (0x00158d0003d43a15): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d0002a65e93 (0x00158d0002a65e93): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d00044f23e9 (0x00158d00044f23e9): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d0002a6e6e6 (0x00158d0002a6e6e6): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d00044f24a8 (0x00158d00044f24a8): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d000247747b (0x00158d000247747b): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d00024773c2 (0x00158d00024773c2): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d0006d5736c (0x00158d0006d5736c): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: 0x00158d0006e4902e (0x00158d0006e4902e): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
Zigbee2MQTT:info 2021-08-11 10:14:32: Zigbee: disabling joining new devices.
Zigbee2MQTT:info 2021-08-11 10:14:32: Started frontend on port 0.0.0.0:8080
events.js:353
      throw er; // Unhandled 'error' event
      ^
Error: listen EADDRINUSE: address already in use 0.0.0.0:8080
    at Server.setupListenHandle [as _listen2] (net.js:1318:16)
    at listenInCluster (net.js:1366:12)
    at doListen (net.js:1503:7)
    at processTicksAndRejections (internal/process/task_queues.js:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1345:8)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '0.0.0.0',
  port: 8080
}

```

It seems to be blocking related elements, I no longer receive new values.

My key is a zzh!.

Any ideas?

Thanks 🙂

---

<div class="post-metadata">

**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:** [August 11, 2021, 6:37pm UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475/2 "2021-08-11T18:37:57Z")

</div>

Hello, the error `Error: listen EADDRINUSE: address already in use 0.0.0.0:8080` indicates that a process is already using port 8080. Indeed, the container **gladys-z2m-zigbee2mqtt** exposes a debug interface.

Two solutions are available:

- identify the process (external to Gladys) and change its port
- modify the `configuration.yaml` file in `/var/lib/gladysassistant/zigbee2mqtt/z2m` and restart the container

```yaml
frontend:
  port: 8080

```

---

<div class="post-metadata">

**Author:** ![Hizo](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/h/51bf81/32.png) [@Hizo](https://community.gladysassistant.com/u/Hizo)\
**Post date:** [August 11, 2021, 9:25pm UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475/3 "2021-08-11T21:25:51Z")

</div>

Thanks a lot, indeed, by changing the port in the configuration file, everything works again 🙂

In my opinion, the one already using port 8080 is the watcher for the update.

---

<div class="post-metadata">

**Author:** ![Jean34](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jean34/32/3349_2.png) [@Jean34](https://community.gladysassistant.com/u/Jean34)\
**Post date:** [August 12, 2021, 11:38am UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475/4 "2021-08-12T11:38:41Z")

</div>

> [@Hizo](#):
>
> In my opinion, the one already using port 8080 is the watcher for the update.

Hi, no because in the official gladys image there are all these containers and it doesn’t prevent the zigbee service from working 😉

---

<div class="post-metadata">

**Author:** ![Hizo](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/h/51bf81/32.png) [@Hizo](https://community.gladysassistant.com/u/Hizo)\
**Post date:** [August 12, 2021, 3:41pm UTC](https://community.gladysassistant.com/t/erreur-docker-zigbee2mqtt/6475/5 "2021-08-12T15:41:13Z")

</div>

It’s strange, because it’s the only recent thing I’ve done that clearly uses port 8080.

In any case, manually changing the port worked very well 🙂

And for the record, since I changed the port, the Gladys update went smoothly whereas nothing was happening before…