Configuring Docker for ethernet coordinator

[Josov]

I have got a Raspberry Pi with Docker installed and would like to run z2m in a container using docker-compose (or eventually docker). The coordinator is a SmartLight Zigbee LAN adapter, the SLZB-05 on port: 6638. How should I configure the docker compose file for the ethernet Zigbee LAN adapter?

[JackTalisker]

This is my zigbee2mqtt docker compose section for a sonoff wifi coordinator with tasmota fw:

zigbee2mqtt:
   container_name: zigbee2mqtt
   image: koenkk/zigbee2mqtt
   volumes:
   - "/home/pi/zigbee2mqtt:/app/data"
   devices:
   - /dev/null:/dev/ttyACM0
   environment:
   - "TZ=Europe/Rome"
   network_mode: host
   restart: always

[rafvhoof]

Trying to setup Z2M docker with a ZigStar LAN gateway. Using the following docker compose file

version: '3.8'
services:
  zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt:latest
    restart: unless-stopped
    volumes:
      - ./data:/app/data
      - /run/udev:/run/udev:ro
    ports:
      - 8080:8080 # Frontend port
    environment:
      - "TZ=Europe/Berlin"
    network_mode: host
    devices:
      - /dev/null:/dev/ttyACM0 # Make sure this matched your adapter location

I get the following error

Zigbee2MQTT:info  2023-02-13 13:54:58: Starting Zigbee2MQTT version 1.30.1 (commit #eb878d3)
Zigbee2MQTT:info  2023-02-13 13:54:58: Starting zigbee-herdsman (0.14.89)
Zigbee2MQTT:error 2023-02-13 13:54:59: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-02-13 13:54:59: Failed to start zigbee
Zigbee2MQTT:error 2023-02-13 13:54:59: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-02-13 13:54:59: Exiting...
Zigbee2MQTT:error 2023-02-13 13:54:59: Error: Error while opening serialport 'Error: Error: Not a tty setting custom baud rate of 115200'
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:76:22)
    at /app/node_modules/@serialport/stream/dist/index.js:112:18

Can anyone help me with the configuration?

[JackTalisker]

what's yor z2m configuration.yaml ?

[rafvhoof]

configuration.yaml

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.1.24
serial:
  port: 'tcp://192.168.1.108:6638'

No problems with connection when trying directly on my Windows system.

[TurboCoder13]

@rafvhoof Same here. Did you manage to sort it out?

This config is right for Z2M configuration.yaml:

homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.1.24
serial:
  port: 'tcp://192.168.1.108:6638'

But for the docker-compose.yaml file, I have no clue what to use for devices:

zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt
    volumes:
      - /opt/zigbee2mqtt/data:/app/data
      - /opt/zigbee2mqtt/udev:/run/udev:ro
    restart: unless-stopped
    network_mode: host
    environment:
      - TZ=Europe/Berlin
    devices:
      - # what to put here?

[junosuarez]

@eitel13 No need to put anything in devices in docker-compose.yaml - since you're connecting over the network instead of a local USB device, the docker devices config doesn't apply. You do need to make sure the container can communicate to the IP address, however. You can check this by running a command from inside the zigbee2mqtt container:

1. make sure your container is running (eq docker container list --filter name=zigbee2mqtt
2. start a shell inside the container: docker exec -it zigbee2mqtt sh. it should show a minimal prompt: /app #
3. try to connect to your network coordinator, using the IP and port, using netcat: nc 192.168.1.108 6638; echo $?

• make sure you use a space between the IP address and the port number
• the ; echo $? at the end will print the exit code, so we can see if there is an error
• if it connects successfully, you might see no message or a blank screen. this is good, it means you were able to open a connection to the coordinator.
• if it exits immediately or after a few seconds, the connection was closed (or never established in the first place), and you should see a 1 for the exit code.

4. ctrl+c will close the running process. run exit to get out of the container and back to your system command prompt.

The network_mode: host means the docker container should be able to reach all the same routes as your host machine. Docker networking can be tricky, though - feel free to share the results and if you got it working or need to debug further.

[TurboCoder13]

Thank you @junosuarez for the detailed reply! 🙂

I had managed to resolve this after posting here, but nevertheless, it's good to know and reference for the future.

Thank you again 🦾

[d3zit]

How can you test if the container sees the device if the error itself is preventing the container from starting?

[Sandermand]

Thank you @junosuarez for the detailed reply! 🙂

I had managed to resolve this after posting here, but nevertheless, it's good to know and reference for the future.

Thank you again 🦾

What did you do to fix it ? I have the same issue :)