Installation HA + zigbee2mqtt avec dongle POE SLZB-06

Bonjour.
My home automation system is currently configured as follows:

  • Synology DS220+ NAS,
  • MQTT broker (eclipse mosquitto) containerized under Docker,
  • Domoticz containerized under Docker with zigbeefordomoticz and Sonoff E dongle (USB).
    For different reasons and before a possible “big jump”, I would like to test the following configuration on my NAS:
  • Containerized HA,
  • containerized zigbee2mqtt + SLZB-06 POE dongle,
  • use of the existing MQTT container.

I might as well point out straight away that my knowledge of Linux and other Docker is limited to everything I have read (especially understand…) of the documentation and tutorials available on the internet… hence, no doubt , the difficulties I am currently encountering…

Here is

  • the docker compose that I use to create the HA and zigbee2mqtt containers:

version: ‘3.8’
services:
#Conteneur Home Assistant
homeassistant:
container_name: homeassistant
image: homeassistant/home-assistant:latest
restart: always
#On définit un “bind mount” pour conserver la configuration de Home-Assistant
volumes:
- /volume1/docker/homeassistant:/config
ports:
#Le port sur lequel sera accessible l’interface web PORT_EXPORTE:PORT_CONTENEUR
- 8123:8123
environment:
- TZ=Europe/Paris

#Conteneur ZigBee2MQTT
zigbee2mqtt:
    container_name: zigbee2mqtt
    image: koenkk/zigbee2mqtt
    restart: unless-stopped
    volumes:
        - /volume1/docker/zigbee2mqtt/data:/app/data
        - /volume1/docker/zigbee2mqtt/data/configuration.yaml:/app/data/configuration.yaml
        - /run/udev:/run/udev:ro         
    ports:
        #Port Zigbee2MQTT
        - 8085:8085
    environment:
        - TZ=Europe/Paris`Preformatted text`
  • the “configuration.yaml” file used for zigbee2mqtt:

homeassistant: true
permit_join: true
frontend:
port: 8085
mqtt:
base_topic: zigbee2mqtt
server: mqtt://192.168.1.100:1883
user: xxx
password: xxx
serial:

Location of SLZB-06

port: tcp://192.168.1.43:6638
baudrate: 115200
adapter: zstack

Disable green led?

disable_led: false

Set output power to max 20

advanced:
transmit_power: 20
network_key:
- 128
- 237
- 95
- 194
- 127
- 152
- 184
- 173
- 202
- 217
- 251
- 26
- 135
- 119
- 15
- 223
pan_id: 14155
ext_pan_id:
- 119
- 197
- 208
- 13
- 245
- 95
- 208
- 141

  • the “mosquitto.conf” configuration file of the mqtt container which currently works (well) on the NAS:

persistence true
persistence_location /mosquitto/data/
log_dest file /mosquitto/log/mosquitto.log
log_type all
listener 1883
allow_anonymous true
socket_domain ipv4

When I run docker compose,

  • the HA container is installed and launched correctly; his diary does not reveal any anomaly;
  • the zigbee2mqtt container installs then launches and stops indefinitely; its log shows the following messages on each reboot:

2024/08/16 17:44:25 stderr at start (/app/index.js:130:14)
2024/08/16 17:44:25 stderr at Object.reRead (/app/lib/util/settings.ts:749:5)
2024/08/16 17:44:25 stderr at getInternalSettings (/app/lib/util/settings.ts:466:21)
2024/08/16 17:44:25 stderr at read (/app/lib/util/settings.ts:380:27)
2024/08/16 17:44:25 stderr at interpretValue (/app/lib/util/settings.ts:369:25)
2024/08/16 17:44:25 stderr at Object.read (/app/lib/util/yaml.ts:7:37)
2024/08/16 17:44:25 stderr at Object.readFileSync (node:fs:464:35)
2024/08/16 17:44:25 stderr at Object.openSync (node:fs:596:3)
2024/08/16 17:44:25 stderr Error: ENOENT: no such file or directory, open ‘/app/data/… 3.yaml’
2024/08/16 17:44:24 stdout Starting Zigbee2MQTT without watchdog.
2024/08/16 17:44:24 stdout Using ‘/app/data’ as data directory

It seems to me that everything happens as if the zigbee2mqtt container could not find the “configuration.yaml” file. I reread the Docker documentation on volumes, but obviously I must not be making the correct volume declaration in Docker compose.

For the record, my Docker configuration is such that each container works on its directory created in the “/volume1/docker” directory of the NAS.

If some of you can give me some indications, or even identify my errors, that would be of service to me.
Thanks in advance …

1 Like

I’ve ran into a similar issue and because I use Terramaster I could easy check the path of the file.

I know that Synology has a similar docker manager style application where you can visually go through your folder structure to select the path after the container has (failed to) run.

After running your docker-compose command and the container has been set up. Go into the Synology docker manager (or similar) application and check if your volume path is correct according to that application. If not, change it. If it is, I am none the wiser too and I hope you find a solution!