Zigbee2MQTT with Docker Compose
Zigbee2MQTT supports various Zigbee adapters and a big bunch of devices. Zigbee2MQTT integrates well with most home automation solutions because it uses MQTT. In the project's words: zigbee2mqtt.io front page checked 2026-09-29
Replaces: Proprietary Zigbee bridges. The project's tagline: "Zigbee to MQTT bridge, get rid of your proprietary Zigbee bridges". Zigbee2MQTT README on GitHub checked 2026-09-29
Runs on: amd64, arm64, arm/v7, 386, arm/v6, riscv64 from each image's registry manifest, checked 2026-09-29; a CPU counts only if every image has a build for it. Image by image
Add Zigbee2MQTT to the builder to use your own domain, get its passwords generated in your browser, and combine it with other apps in one file.
What Zigbee2MQTT needs
Only figures Zigbee2MQTT's own documentation publishes, each linked to the page it is on. Where the project gives no number, this page does not invent one.
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | The project publishes no figure | |
| CPU | The project publishes no figure | |
| Disk | The project publishes no figure | |
Which hardware Zigbee2MQTT has images for
Read from each image's manifest list in its registry (anonymous, read-only) when this page was built. An app counts for a CPU only if every one of its images lists it.
- x86-64 PC or NAS (
linux/amd64): every image has a build. - Raspberry Pi 4/5, 64-bit OS (
linux/arm64): every image has a build. - Raspberry Pi 3 or Zero 2 W, 32-bit OS (
linux/arm/v7): every image has a build.
| Service | Image | Platforms in the manifest | Digest | Registry | Checked |
|---|---|---|---|---|---|
zigbee2mqtt | ghcr.io/koenkk/zigbee2mqtt | arm64, amd64, arm/v6, arm/v7, riscv64, 386 | sha256:fef0de769dcd04c27b3a6d277b61046eb96284bdd4198dcb1687c3a01b3020f3 | ghcr.io | 2026-09-29 |
Your Zigbee adapter
A USB stick is passed into the container and Zigbee2MQTT tries to detect what it is; a network adapter (Ethernet or Wi-Fi) is reached at a tcp:// address instead, with nothing plugged into the server. Pick yours: the files below then set the serial.adapter value Zigbee2MQTT's docs give for that family (one of zstack, ember, deconz, zigate or zboss) and the port, through the documented ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER / ZIGBEE2MQTT_CONFIG_SERIAL_PORT variables, each value quoted from those docs.
docker-compose.yml
USB, auto-detect
This is exactly what the builder writes for Zigbee2MQTT alone on example.org: the official definition with its published ports removed and Caddy added in front. The time zone is Etc/UTC here; the builder uses your browser's. Every ${VARIABLE} is defined in the .env below.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
With a USB zStack (Texas Instruments) adapter
A USB adapter of the zStack (Texas Instruments) family: the same file, with the adapter type set to zstack and the port to the path inside the container, through the environment form of serial.adapter and serial.port. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Source: https://www.zigbee2mqtt.io/guide/adapters/zstack.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zstack" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zstack" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zstack", from the zStack (Texas Instruments) page: Zigbee2MQTT docs: zStack adapters (Texas Instruments) checked 2026-10-09serial: adapter: zstack- On the docs' adapter list, this family is under Recommended: Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
Recommended zStack based (Texas Instruments) EmberZNet based (Silicon Labs) deCONZ based (Dresden Elektronik)
ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the path inside the container that thedevices:line maps your stick to: “The path before the : is the path on the host, the path after it is the path that is mapped to inside the container. You should always use the /dev/serial/by-id/ path on the host.” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - On the host, the by-id path pattern for the
.env,/dev/serial/by-id/XXX: “# USB adapters - use format "port: /dev/serial/by-id/XXX"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 - Zigbee2MQTT's docs give one by-id pattern for every USB family and no per-family name; their one full example is the TI CC2531. ls -l /dev/serial/by-id on your server lists yours. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Coordinator backups (coordinator_backup.json in the data folder) work with this family. “Note that only adapters based on zStack or EmberZNet currently support backing up the coordinator (coordinator_backup.json).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- Further settings its page names for this family: “Other supported settings are: disable_led, adapter_concurrent and transmit_power (docs).” Zigbee2MQTT docs: zStack adapters (Texas Instruments) checked 2026-10-09
- Not detected over USB? “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Firmware: “Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
With a USB EmberZNet (Silicon Labs) adapter
A USB adapter of the EmberZNet (Silicon Labs) family: the same file, with the adapter type set to ember and the port to the path inside the container, through the environment form of serial.adapter and serial.port. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Source: https://www.zigbee2mqtt.io/guide/adapters/emberznet.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "ember" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "ember" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "ember", from the EmberZNet (Silicon Labs) page: Zigbee2MQTT docs: EmberZNet adapters (Silicon Labs) checked 2026-10-09serial: adapter: ember- On the docs' adapter list, this family is under Recommended: Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
Recommended zStack based (Texas Instruments) EmberZNet based (Silicon Labs) deCONZ based (Dresden Elektronik)
ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the path inside the container that thedevices:line maps your stick to: “The path before the : is the path on the host, the path after it is the path that is mapped to inside the container. You should always use the /dev/serial/by-id/ path on the host.” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - On the host, the by-id path pattern for the
.env,/dev/serial/by-id/XXX: “# USB adapters - use format "port: /dev/serial/by-id/XXX"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 - Zigbee2MQTT's docs give one by-id pattern for every USB family and no per-family name; their one full example is the TI CC2531. ls -l /dev/serial/by-id on your server lists yours. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- The older value ezsp is no longer the one to use: “The use of adapter: ezsp is now deprecated.” Zigbee2MQTT docs: EmberZNet adapters (Silicon Labs) checked 2026-10-09
- The firmware versions its page lists as supported: “Currently supported firmware version: 7.4.x, 8.0.x, 8.1.x, 8.2.x, 9.0.x, 9.1.x” Zigbee2MQTT docs: EmberZNet adapters (Silicon Labs) checked 2026-10-09
- Coordinator backups (coordinator_backup.json in the data folder) work with this family. “Note that only adapters based on zStack or EmberZNet currently support backing up the coordinator (coordinator_backup.json).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- Not detected over USB? “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Firmware: “Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
With a USB deCONZ (Dresden Elektronik) adapter
A USB adapter of the deCONZ (Dresden Elektronik) family: the same file, with the adapter type set to deconz and the port to the path inside the container, through the environment form of serial.adapter and serial.port. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Source: https://www.zigbee2mqtt.io/guide/adapters/deconz.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "deconz" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "deconz" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "deconz", from the deCONZ (Dresden Elektronik) page: Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09serial: adapter: deconz- On the docs' adapter list, this family is under Recommended: Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
Recommended zStack based (Texas Instruments) EmberZNet based (Silicon Labs) deCONZ based (Dresden Elektronik)
ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the path inside the container that thedevices:line maps your stick to: “The path before the : is the path on the host, the path after it is the path that is mapped to inside the container. You should always use the /dev/serial/by-id/ path on the host.” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - On the host, the by-id path pattern for the
.env,/dev/serial/by-id/XXX: “# USB adapters - use format "port: /dev/serial/by-id/XXX"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 - Zigbee2MQTT's docs give one by-id pattern for every USB family and no per-family name; their one full example is the TI CC2531. ls -l /dev/serial/by-id on your server lists yours. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Its page warns: “Various features are not supported by this adapter, in case you depend on these features, consider a different adapter.” Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09
- Some sticks also need a baud rate (serial.baudrate, which this file does not set). ConBee II needs none: “For ConBee2: specifying the baudrate is not necessary” Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09
- ConBee and RaspBee II: “For Conbee and RaspBee2 it is 38400” Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09
- ConBee III: “For ConBee3 it is 115200” Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09
- Not detected over USB? “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Firmware: “Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
With a USB ZiGate adapter
A USB adapter of the ZiGate family: the same file, with the adapter type set to zigate and the port to the path inside the container, through the environment form of serial.adapter and serial.port. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Source: https://www.zigbee2mqtt.io/guide/adapters/zigate.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zigate" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zigate" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zigate", from the ZiGate page: Zigbee2MQTT docs: ZiGate adapters checked 2026-10-09serial: adapter: zigate- On the docs' adapter list, this family is under Not maintained: Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
Not maintained ZiGate based
ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the path inside the container that thedevices:line maps your stick to: “The path before the : is the path on the host, the path after it is the path that is mapped to inside the container. You should always use the /dev/serial/by-id/ path on the host.” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - On the host, the by-id path pattern for the
.env,/dev/serial/by-id/XXX: “# USB adapters - use format "port: /dev/serial/by-id/XXX"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 - Zigbee2MQTT's docs give one by-id pattern for every USB family and no per-family name; their one full example is the TI CC2531. ls -l /dev/serial/by-id on your server lists yours. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Its page warns: “The implementation of this adapter is not maintained anymore. Consider buying one of the recommended adapters instead.” Zigbee2MQTT docs: ZiGate adapters checked 2026-10-09
- Not detected over USB? “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Firmware: “Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
With a USB ZBOSS (Nordic Semiconductor) adapter
A USB adapter of the ZBOSS (Nordic Semiconductor) family: the same file, with the adapter type set to zboss and the port to the path inside the container, through the environment form of serial.adapter and serial.port. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Source: https://www.zigbee2mqtt.io/guide/adapters/zboss.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. # Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zboss" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them. # ELEVATED ACCESS (devices: your Zigbee adapter): kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" - "/run/udev:/run/udev:ro" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zboss" devices: - "${ZIGBEE2MQTT_ADAPTER}:/dev/ttyACM0" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zboss", from the ZBOSS (Nordic Semiconductor) page: Zigbee2MQTT docs: ZBOSS adapters checked 2026-10-09serial: adapter: zboss- On the docs' adapter list, this family is under Experimental: Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
Experimental ZBOSS based (Nordic Semiconductor)
ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the path inside the container that thedevices:line maps your stick to: “The path before the : is the path on the host, the path after it is the path that is mapped to inside the container. You should always use the /dev/serial/by-id/ path on the host.” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - On the host, the by-id path pattern for the
.env,/dev/serial/by-id/XXX: “# USB adapters - use format "port: /dev/serial/by-id/XXX"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 - Zigbee2MQTT's docs give one by-id pattern for every USB family and no per-family name; their one full example is the TI CC2531. ls -l /dev/serial/by-id on your server lists yours. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Its page warns: “Support for this adapter is experimental, not yet recommended for production setups” Zigbee2MQTT docs: ZBOSS adapters checked 2026-10-09
- The boards its page says it was tested on: “Currently tested on nRF52840 Dongle, Nice!Nano v2 (nRF52840) and ESP32-C6/H2 devboards.” Zigbee2MQTT docs: ZBOSS adapters checked 2026-10-09
- Not detected over USB? “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Firmware: “Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).” Zigbee2MQTT docs: Supported Adapters checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
With a network adapter
A Zigbee coordinator on your network (Ethernet or Wi-Fi), reached at tcp://<address>:<port>. Nothing is plugged into the server, so the file passes no device into the container and does not mount /run/udev. Everything else is the USB, auto-detect file, as the builder writes it for Zigbee2MQTT alone on example.org.
# docker-compose.yml built at dankhost.com for: Zigbee2MQTT # Each app block is its official compose definition. Only the names were prefixed with # the app slug (services, containers, volumes, bind folders, .env variables) so any set of # apps can share one file; other differences are listed under "Changed:" in each block. # Only Caddy publishes ports. Secrets live in .env next to this file. services: # ---- Caddy: the one reverse proxy, HTTPS certificates from Let's Encrypt ---- # Source: https://caddyserver.com/docs/running (checked 2026-09-23) # Source: https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose (checked 2026-09-23) # Caddyfile goes in ./caddy/Caddyfile. Fixed address 172.30.0.2 so apps can trust it exactly. caddy: image: "caddy:2" container_name: "caddy" restart: "unless-stopped" ports: - "80:80" - "443:443" - "443:443/udp" volumes: - "./caddy:/etc/caddy" - "caddy-data:/data" - "caddy-config:/config" networks: proxy: ipv4_address: "172.30.0.2" # ---- Zigbee2MQTT (zigbee.example.org) ---- # Source: https://www.zigbee2mqtt.io/guide/installation/02_docker.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/getting-started/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/frontend.html (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29) # Source: https://www.zigbee2mqtt.io/guide/configuration/adapter-settings.html (checked 2026-10-09) # Changed: Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network. # The adapter is the network address in ${ZIGBEE2MQTT_ADAPTER} (tcp://<address>:<port>, the docs' example until you change it) and its type is ${ZIGBEE2MQTT_ADAPTER_TYPE}, both in .env, set through ZIGBEE2MQTT_CONFIG_SERIAL_PORT and ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER, the documented environment form of serial.port and serial.adapter. The documented devices: line and the /run/udev mount are removed: nothing is plugged into the server. # Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped. zigbee2mqtt: image: "ghcr.io/koenkk/zigbee2mqtt" container_name: "zigbee2mqtt" restart: "unless-stopped" volumes: - "./zigbee2mqtt/data:/app/data" environment: TZ: "Etc/UTC" ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN: "${ZIGBEE2MQTT_AUTH_TOKEN}" ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "${ZIGBEE2MQTT_ADAPTER}" ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "${ZIGBEE2MQTT_ADAPTER_TYPE}" networks: proxy: {} networks: # Pinned so the trusted-proxy address given to each app (172.30.0.2) is exact. # If "docker compose up" reports "Pool overlaps", change 172.30.0 here, in Caddy's # ipv4_address and in every trusted-proxy value to a free 172.x.0 range. proxy: ipam: config: - subnet: "172.30.0.0/24" ip_range: "172.30.0.128/25" gateway: "172.30.0.1" volumes: caddy-data: caddy-config:
ZIGBEE2MQTT_CONFIG_SERIAL_PORTis thetcp://<address>:<port>form,tcp://192.168.1.12:6638in the docs' example, which the.envbelow starts from: “# Ethernet adapters - use format "port: tcp://192.168.1.12:6638"” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09- Another example from the docs, with a host name: “port: tcp://zbgw_efr32_pro.local:6638” Zigbee2MQTT docs: EmberZNet adapters (Silicon Labs) checked 2026-10-09
- The address: “For network adapters you need to find the IP address of your adapter through router/switch web-interface. Make sure that the adapter has been assigned a static IP address!” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- Zigbee2MQTT's docs give no rule for the port: both of their examples use 6638, and they do not say every network adapter listens there. Your adapter's own settings page shows its port.
ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERis${ZIGBEE2MQTT_ADAPTER_TYPE}from the.env, one of: “# Adapter type, allowed values: `zstack`, `ember`, `deconz`, `zigate` or `zboss`” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09ZIGBEE2MQTT_CONFIG_SERIAL_PORTandZIGBEE2MQTT_CONFIG_SERIAL_ADAPTERareserial.portandserial.adapterby the configuration page's rule: “The name of the environment variable should start with ZIGBEE2MQTT_CONFIG_ followed by the path to the property you want to set in uppercase split by a _.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09- They take the place of the same keys in
configuration.yaml: “It is possible to override the values in configuration.yaml via environment variables.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 - Removed: the
devices:line and the/run/udevmount. The docs give the mount for one purpose, “-v /run/udev:/run/udev:ro: required for auto-detecting the adapter” Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-10-09 - Some adapters do both: “If it's still not connecting, make sure your adapter is in USB mode. Some adapters, eg. the ZigStar run in network mode by default, and won't communicate over USB until put into USB mode.” Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- The docs also describe mdns:// discovery for a few network adapters; this file uses the tcp:// form, and the docs say nothing about mDNS discovery from inside a Docker bridge network. Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09
- The docs do not say whether the onboarding page fills in values set through environment variables; give it the same port and type. “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
Caddyfile save as caddy/Caddyfile
Caddy gets and renews the HTTPS certificate for zigbee.example.org by itself once the DNS record points at your server and ports 80 and 443 reach it.
# Caddyfile built at dankhost.com. Save it as ./caddy/Caddyfile next to docker-compose.yml.
# Caddy gets and renews a Let's Encrypt certificate for each name below by itself,
# once the DNS records point at this server and ports 80 and 443 reach it.
# Zigbee2MQTT
zigbee.example.org {
reverse_proxy zigbee2mqtt:8080
}
.env
The secret is left blank here on purpose: a password printed on a public page is the same for everyone who copies it. The builder fills it with random letters and digits made in your browser.
# .env for Zigbee2MQTT, from dankhost.com/app/zigbee2mqtt/. Fill the blank secret before starting. # Keep this file private (chmod 600). # Zigbee2MQTT # 32 random letters and digits: the builder fills this in your browser ZIGBEE2MQTT_AUTH_TOKEN= # Your Zigbee adapter: the value below is the example from Zigbee2MQTT's docs. Replace it with your adapter's path from: ls -l /dev/serial/by-id/ ZIGBEE2MQTT_ADAPTER=/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED3DDF-if00
With a network adapter
The adapter path is replaced by its tcp:// address, and the adapter type is added. The secret is left blank, as above.
# .env for Zigbee2MQTT, from dankhost.com/app/zigbee2mqtt/. Fill the blank secret before starting. # Keep this file private (chmod 600). # Zigbee2MQTT # 32 random letters and digits: the builder fills this in your browser ZIGBEE2MQTT_AUTH_TOKEN= # Your network Zigbee adapter as tcp://<address>:<port>: the value below is the example from Zigbee2MQTT's docs. Replace it with your adapter's static IP address and port. ZIGBEE2MQTT_ADAPTER=tcp://192.168.1.12:6638 # Your adapter's type, one of the docs' allowed values: zstack, ember, deconz, zigate or zboss. zstack is the docs' example; replace it with your adapter's family. ZIGBEE2MQTT_ADAPTER_TYPE=zstack
What Zigbee2MQTT needs beyond the proxy
Zigbee2MQTT asks for more than an ordinary container. The compose file keeps what the project documents and labels each item with an # ELEVATED ACCESS comment:
- devices: your Zigbee adapter: kept from the documented file: the USB Zigbee adapter is passed into the container as /dev/ttyACM0, and /run/udev is mounted read-only so Zigbee2MQTT can detect it. The container gets that one device, not the others on the host.
With a network adapter, Zigbee2MQTT needs nothing beyond the proxy: the file passes no host device into the container and mounts nothing from /run/udev, so it carries no # ELEVATED ACCESS comment.
Changes from the official file
Besides prefixing every service, container, volume, folder and variable with zigbee2mqtt (so any set of apps can share one file), these are all the differences from what the project documents:
- Removed the documented '8080:8080' frontend port; Caddy reaches zigbee2mqtt:8080 on the proxy network.
- The adapter path is ${ZIGBEE2MQTT_ADAPTER} in .env (the docs' example path until you change it) instead of written into the file; the docs say to use the /dev/serial/by-id/ path.
- Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zstack" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them.
- Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "ember" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them.
- Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "deconz" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them.
- Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zigate" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them.
- Added ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "zboss" and ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyACM0", the documented environment form of serial.adapter and serial.port, so Zigbee2MQTT is told the adapter type and port instead of detecting them.
- The adapter is the network address in ${ZIGBEE2MQTT_ADAPTER} (tcp://<address>:<port>, the docs' example until you change it) and its type is ${ZIGBEE2MQTT_ADAPTER_TYPE}, both in .env, set through ZIGBEE2MQTT_CONFIG_SERIAL_PORT and ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER, the documented environment form of serial.port and serial.adapter. The documented devices: line and the /run/udev mount are removed: nothing is plugged into the server.
- Added ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, the documented environment form of frontend.auth_token, set to a generated token, so the frontend asks for it. TZ is your time zone instead of Europe/Berlin; container_name is dropped.
Notes for Zigbee2MQTT behind the proxy
- Set ZIGBEE2MQTT_ADAPTER in .env to your adapter first: plug it in and run ls -l /dev/serial/by-id/. Docker refuses to start the container while the path does not exist.
- Set ZIGBEE2MQTT_ADAPTER in .env to your adapter's address as tcp://<address>:<port>, and ZIGBEE2MQTT_ADAPTER_TYPE to its family: zstack, ember, deconz, zigate or zboss. Give the adapter a static IP address first.
- On the first start Zigbee2MQTT runs its onboarding page at https://zigbee.example.org, and it is open to whoever gets there first: open it straight away. Give the adapter as /dev/ttyACM0 (the path inside the container) and your MQTT broker; with Mosquitto in the same file that is mqtt://mosquitto:1883 and the user you created for it.
- On the first start Zigbee2MQTT runs its onboarding page at https://zigbee.example.org, and it is open to whoever gets there first: open it straight away. Give the adapter as the same tcp://<address>:<port> and type as in .env and your MQTT broker; with Mosquitto in the same file that is mqtt://mosquitto:1883 and the user you created for it.
- After onboarding the frontend asks for a token: ZIGBEE2MQTT_AUTH_TOKEN from .env. The docs note that the frontend's WebSocket does not work with HTTP basic authentication in Safari and on iOS, which is why the token is used instead.
- The docs' image has no tag, so it is 'latest', which the Docker page describes as the latest release.
How to run it
- At your DNS provider, add an A record named
zigbeeon your domain pointing at the server's public IP address, and forward TCP 80, TCP 443 and UDP 443 to it. - Save the three files in one folder:
docker-compose.ymland.envside by side, the Caddyfile at./caddy/Caddyfile. Replaceexample.orgwith your domain in the Caddyfile, the compose file and the .env, or let the builder do it. - Fill the blank
ZIGBEE2MQTT_AUTH_TOKENin.env. The builder generates it; on the server,tr -dc A-Za-z0-9 </dev/urandom | head -c 32prints 32 random letters and digits. Thenchmod 600 .env. - Start it:
docker compose up -d docker compose logs -f caddy # watch the certificate arrive
- Open the new address (
zigbee.plus your domain) in a browser and follow the notes above.
With Home Assistant, Mosquitto and Zigbee2MQTT in the same file
Tick all three in the builder and they land in one docker-compose.yml, but they do not reach the broker at the same address. Home Assistant keeps network_mode: "host" as its install page documents, so it is on none of the file's networks; Mosquitto and Zigbee2MQTT are both on the proxy network. Every step below is quoted from the project's own docs, with the date the page was fetched.
| App | In the file | Broker address |
|---|---|---|
| Home Assistant | network_mode: "host" | <server LAN IP>, port 1883 |
| Zigbee2MQTT | the proxy network | mqtt://mosquitto:1883 |
| Mosquitto | the proxy network, publishes 1883:1883 | listens on 1883 inside its container |
- Zigbee2MQTT uses the service name. It shares the
proxynetwork with Mosquitto, and Compose gives every service on a network a name the others can look up, somosquittoresolves to the broker's container from inside Zigbee2MQTT's: “Each service registers its name with an internal DNS server, so containers can reach each other using the service name directly.” “The proxy service is isolated from the db service, because they do not share a network in common.” Docker docs: Networking in Compose (service discovery by name, custom networks) checked 2026-10-09 - Home Assistant uses the server's own address. With host networking it is not on the
proxynetwork at all, so the namemosquittomeans nothing to it. It reaches Mosquitto the way the devices on your network do, through the port the file publishes on the server (1883:1883): “If you use the host network mode for a container, that container's network stack isn't isolated from the Docker host (the container shares the host's networking namespace), and the container doesn't get its own IP-address allocated.” Docker docs: Host network driver checked 2026-10-09 “-p 8080:80 Map port 8080 on the Docker host to TCP port 80 in the container.” Docker docs: Port publishing and mapping checked 2026-10-09
1. Create the broker user first
Mosquitto in this file lets no client in without a user from its password file. Create the first one with the command in Mosquitto's notes before you start it. To give Home Assistant and Zigbee2MQTT a user each, add the second the way Mosquitto's docs say, without the create flag: “To add more users to an existing password file, or to change the password for an existing user, leave out the -c argument” Mosquitto docs: Authentication methods (mosquitto_passwd, password_file) checked 2026-10-09
A user added while Mosquitto runs is not read until the broker reloads the file, so restart it afterwards: “If you make changes to the password file you must trigger the broker to reload the file by sending a SIGHUP message” Mosquitto docs: Authentication methods (mosquitto_passwd, password_file) checked 2026-10-09 “Restarts all stopped and running services, or the specified services only.” Docker docs: docker compose restart checked 2026-10-09
docker compose restart mosquitto
2. Home Assistant: add the MQTT integration
- “Go to Settings > Devices & services.”
- “In the bottom right corner, select the Add Integration button.”
- “From the list, select MQTT.” Home Assistant docs: MQTT integration (adding it, broker settings, MQTT protocol version 5) checked 2026-10-09
- As broker give
<server LAN IP>(the address you open Home Assistant on, notmosquitto), as port1883, and the user and password from the first step. “Add the MQTT integration, then provide your broker’s hostname (or IP address) and port and (if required) the username and password that Home Assistant should use.” Home Assistant docs: MQTT integration (adding it, broker settings, MQTT protocol version 5) checked 2026-10-09
3. Zigbee2MQTT: the broker address
Zigbee2MQTT keeps its settings in configuration.yaml in its data directory, which this file mounts from ./zigbee2mqtt/data. The file is written by the onboarding page on the first start: “The file have to be located in the data directory within your installation.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09 “Zigbee2MQTT offers an onboarding process on first run (when no configuration.yaml exists).” Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-10-09
Its mqtt section, with the docs' example address changed to the broker's service name and port, and the user you created for Zigbee2MQTT: “Zigbee2MQTT requires a MQTT-Server connection to operate. # Required: MQTT settings mqtt:” “server: 'mqtt://localhost:1883'” “user: my_user” “password: my_password” Zigbee2MQTT docs: Configuration, MQTT (server, user, password) checked 2026-10-09
mqtt: server: 'mqtt://mosquitto:1883' user: <user> password: <password>
4. Zigbee2MQTT: make its devices appear in Home Assistant
Zigbee2MQTT announces its devices to Home Assistant over MQTT, but only when told to: “The easiest way to integrate Zigbee2MQTT with Home Assistant is by using MQTT discovery. This allows Zigbee2MQTT to automatically add devices to Home Assistant.” Zigbee2MQTT docs: Home Assistant integration (MQTT discovery) checked 2026-10-09 “# Enable the integration (default: false)” Zigbee2MQTT docs: Configuration, Home Assistant integration (homeassistant.enabled) checked 2026-10-09
Add these two lines to the same configuration.yaml: “In your Zigbee2MQTT configuration.yaml set: homeassistant: enabled: true” Zigbee2MQTT docs: Home Assistant integration (MQTT discovery) checked 2026-10-09
homeassistant: enabled: true
Then restart Zigbee2MQTT: “Some options will require a restart before being effective.” Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-10-09
docker compose restart zigbee2mqtt
Its devices then appear in Home Assistant as devices of the MQTT integration from step 2: “When using Home Assistant MQTT discovery, Zigbee2MQTT integrates with the Home Assistant device registry. This allows you to change the Home Assistant entity_id and friendly_name from the Home Assistant web interface without having to restart Home Assistant.” Zigbee2MQTT docs: Home Assistant integration (MQTT discovery) checked 2026-10-09
Back it up
Zigbee2MQTT publishes no backup procedure for Docker. Everything it keeps (configuration.yaml, the device database and the adapter's network backup) is in its data directory, copied below with Docker's generic method.
Below is the BACKUP.md the builder writes next to the compose file above: which of its folders and volumes hold data, what to copy with which container stopped, and a restore check. Pick more apps in the builder and it covers them all in one file.
# BACKUP.md built at dankhost.com for: Zigbee2MQTT
What to copy from the docker-compose.yml built with this file, the database dump each project documents (rewritten for the service names in that file), what to copy with which container stopped, and how to check the result. Run every command in the folder that holds docker-compose.yml.
The folders are owned by the containers' users: put sudo in front of tar if it says "Permission denied". Named volumes live under /var/lib/docker/volumes, not next to the compose file, so they are copied through a throwaway ubuntu container (Docker's documented --volumes-from method). tar makes a full copy each run; for large folders an incremental tool (restic, borg, rsync) saves time and space.
Never run "docker compose down -v" on this file: it deletes the named volumes of every app in it.
## Before you start
BACKUP=/mnt/backup/selfhost # change this: a disk or machine other than this server's system disk
mkdir -p "$BACKUP"
## Every time: the three stack files
tar czf "$BACKUP/stack-files.tar.gz" docker-compose.yml .env caddy
.env holds the database passwords and secret keys the apps were set up with; keep this archive as private as the data.
## Caddy (the reverse proxy)
Caddy's docs: 'The data directory must not be treated as a cache.' It holds the TLS certificates and their private keys; without it Caddy has to ask Let's Encrypt for every certificate again.
- caddy-data (named volume, /data in caddy)
BACK UP: TLS certificates, private keys, OCSP staples.
- caddy-config (named volume, /config in caddy)
SKIP: the last active configuration, kept for 'caddy run --resume', which this setup does not use: it starts from the Caddyfile.
- ./caddy (/etc/caddy in caddy)
IN stack-files.tar.gz: the Caddyfile, copied with the stack files above.
Copy (Caddy keeps serving while you copy):
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu tar cvf /backup/caddy-data.tar /data
Restore check:
tar tf "$BACKUP/caddy-data.tar" > /dev/null && echo OK
docker run --rm --volumes-from caddy -v "$BACKUP":/backup ubuntu bash -c "cd /data && tar xvf /backup/caddy-data.tar --strip 1"
Sources:
- Caddy docs: Conventions, Data directory: https://caddyserver.com/docs/conventions#data-directory (checked 2026-09-24)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-24)
## Zigbee2MQTT
Zigbee2MQTT publishes no backup procedure for Docker. Everything it keeps (configuration.yaml, the device database and the adapter's network backup) is in its data directory, copied below with Docker's generic method.
What this compose mounts:
- ./zigbee2mqtt/data (/app/data in zigbee2mqtt)
BACK UP: configuration.yaml, database.db (your paired devices) and coordinator_backup.json.
1. Stop zigbee2mqtt. Stopping it keeps the device database from changing mid-copy. Zigbee devices keep working locally, but nothing reaches MQTT until it starts again.
docker compose stop zigbee2mqtt
2. Copy while zigbee2mqtt is stopped:
tar czf "$BACKUP/zigbee2mqtt-data.tar.gz" ./zigbee2mqtt/data
3. Start it again:
docker compose start zigbee2mqtt
Restore check:
tar tzf "$BACKUP/zigbee2mqtt-data.tar.gz" > /dev/null && echo OK
Put a copy back (with zigbee2mqtt stopped):
tar xzf "$BACKUP/zigbee2mqtt-data.tar.gz" # recreates ./zigbee2mqtt/data; move the old folder aside first
Stop it, put ./zigbee2mqtt/data back, start it with the same adapter.
Sources:
- Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables): https://www.zigbee2mqtt.io/guide/configuration/ (checked 2026-09-29)
- Docker docs: Volumes, Back up, restore, or migrate data volumes: https://docs.docker.com/engine/storage/volumes/#back-up-restore-or-migrate-data-volumes (checked 2026-09-29)
Update it
What docker compose pull does depends only on how each image line in the compose file above is tagged. For Zigbee2MQTT as this page writes it:
| Service | Image | How it is pinned | What docker compose pull does |
|---|---|---|---|
caddy | caddy:2 | Major version only (tag 2) | Takes the newest image tagged 2: minor and patch releases of 2, never 3. A new major version needs a tag edit. |
zigbee2mqtt | ghcr.io/koenkk/zigbee2mqtt | Not pinned: no tag, which means latest | Moves to the newest image published as latest, which can be a new major version. |
What Zigbee2MQTT's docs say about updating
Zigbee2MQTT's Docker page: docker compose pull for its service, then docker compose up -d for it.
The steps
- Back up first, as in Back it up above. An update can migrate Zigbee2MQTT's data on its first start; the copy is the way back.
- Download the new images. Running containers are not touched yet:
docker compose pull
- Recreate the containers whose image changed. Volumes and bind-mounted folders stay as they are:
docker compose up -d
- Watch Zigbee2MQTT start (Ctrl+C stops following the log, not the app):
docker compose logs -f zigbee2mqtt
- Optional: remove the old images the pull left without a tag. This covers every stack on the machine, not only this one:
docker image prune
Locked out? Reset the admin password
The frontend asks for frontend.auth_token, stored in clear text. This file sets it with ZIGBEE2MQTT_CONFIG_FRONTEND_AUTH_TOKEN, read from ZIGBEE2MQTT_AUTH_TOKEN in .env, which overrides configuration.yaml.
- In .env, read or replace the token: Source: Zigbee2MQTT docs: Frontend (auth_token) read 2026-10-03; Zigbee2MQTT docs: Configuration, Environment variables read 2026-10-03
ZIGBEE2MQTT_AUTH_TOKEN=<new token>
- If you changed it, recreate the container so it reads the new value: Source: Zigbee2MQTT docs: Configuration, Environment variables read 2026-10-03; Docker docs: docker compose up read 2026-10-03
docker compose up -d
Sources
Every page below was fetched on the date shown.
- zigbee2mqtt.io front page checked 2026-09-29 (what it does)
- Zigbee2MQTT README on GitHub checked 2026-09-29 (what it replaces)
- Zigbee2MQTT docs: Docker (docker run, Docker Compose example, tags) checked 2026-09-29 (compose definition and proxy settings, update notes, Your adapter)
- Zigbee2MQTT docs: Getting started (onboarding on first run) checked 2026-09-29 (compose definition and proxy settings, Home Assistant, Mosquitto and Zigbee2MQTT together, Your adapter)
- Zigbee2MQTT docs: Frontend (auth_token, Nginx proxy configuration) checked 2026-09-29 (compose definition and proxy settings)
- Zigbee2MQTT docs: Configuration (the data directory, ZIGBEE2MQTT_CONFIG_ environment variables) checked 2026-09-29 (compose definition and proxy settings, backup plan, Home Assistant, Mosquitto and Zigbee2MQTT together, Your adapter)
- Caddy docs: Keep Caddy running (Docker Compose section) checked 2026-09-23 (Caddy)
- Vaultwarden wiki: Caddy with HTTP challenge (uses the caddy:2 image) checked 2026-09-23 (Caddy)
- Docker docs: Volumes, Back up, restore, or migrate data volumes checked 2026-09-29 (backup plan)
- Caddy docs: Conventions, Data directory checked 2026-09-24 (backup plan)
- Docker docs: docker compose pull checked 2026-09-30 (update steps)
- Docker docs: docker compose up (recreates changed containers, keeps volumes) checked 2026-09-30 (update steps)
- Docker docs: docker image prune checked 2026-09-30 (update steps)
- Home Assistant docs: MQTT integration (adding it, broker settings, MQTT protocol version 5) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Zigbee2MQTT docs: Home Assistant integration (MQTT discovery) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Zigbee2MQTT docs: Configuration, Home Assistant integration (homeassistant.enabled) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Zigbee2MQTT docs: Configuration, MQTT (server, user, password) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Mosquitto docs: Authentication methods (mosquitto_passwd, password_file) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- mosquitto.org front page checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Docker docs: Networking in Compose (service discovery by name, custom networks) checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Docker docs: Host network driver checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Docker docs: Port publishing and mapping checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Docker docs: docker compose restart checked 2026-10-09 (Home Assistant, Mosquitto and Zigbee2MQTT together)
- Zigbee2MQTT docs: Adapter settings (serial.port, serial.adapter, tcp://) checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: Supported Adapters checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: zStack adapters (Texas Instruments) checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: EmberZNet adapters (Silicon Labs) checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: deCONZ (Dresden Elektronik) checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: ZiGate adapters checked 2026-10-09 (Your adapter)
- Zigbee2MQTT docs: ZBOSS adapters checked 2026-10-09 (Your adapter)