-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SLZB-06 does not work with version 1.39.1 #23635
Comments
and on version 1.39.0 it starts
|
Bonsoir. |
Bonjour. I'm working with a Synology DS220+ NAS that already has MQTT installed in a container. I want to do some testing by creating 2 containers (HA and zigbee2mqtt) and using the SLZB-06 POE dongle. Here is my docker compose to create the homeassistant and zigbee2mqtt containers: version: '3.8'
Here is the "configuration.yaml" file which is located in the "/volume1/docker/zigbee2mqtt/data" directory: homeassistant: false Location of SLZB-06
Disable green led?
Set output power to max 20Advanced settingsadvanced: In this file, everything related to the SLZB-06 is given to me by the web app associated with the dongle. Whether I start creating the containers with my "configuration.yaml" file or with the example file that you gave me, the result is the same. Here is the log file associated with the zigbee2mqtt container: 2024/08/17 10:24:46 stderr at start (/app/index.js:130:14) My current understanding of Docker and z2m and my searches on the web do not allow me to understand what is happening. Currently I think my volume declarations when creating the zigbee2mqtt container are incorrect and not allowing the system to find the "configuration.yaml" file. Have a nice day ... |
Sorry...I just realized I was responding to a message that wasn't intended for me. |
I changed the config file for the example that you sent, But it didn´t work too 🤔 edit: I created a new volume and a config file was created, and it was exactly as your example, But it keeps stuck :/ log
|
it is my docker file version: '3.8'
services:
zigbee2mqtt:
container_name: zigbee2mqtt
image: koenkk/zigbee2mqtt:1.39.1
restart: unless-stopped
deploy:
resources:
limits:
cpus: '1'
memory: 1G
reservations:
cpus: '0.5'
memory: 500M
volumes:
- my/local/path/data:/app/data #edit here
- /run/udev:/run/udev:ro
labels:
- "traefik.enable=true"
- "traefik.http.routers.z2m.rule=Host(`my.domain.com`)" #edit here
- "traefik.http.routers.z2m.entrypoints=websecure"
- "traefik.http.services.z2m.loadbalancer.server.port=8080"
- "traefik.http.routers.z2m.tls.certresolver=cloudflare"
environment:
- TZ=Your/TimeZone #edit here
devices:
# Make sure this matched your adapter location
- /dev/tty0:/dev/ttyACM0
networks:
- proxy
networks:
proxy:
driver: bridge
external: true I used this example: https://www.zigbee2mqtt.io/guide/installation/02_docker.html#docker-compose |
@eerison You include the following lines in your docker:
I thought I understood that these lines corresponded to a USB device. Would you use your SLZB-06 via USB and not Ethernet? Can you confirm to me that your z2m configuration file "configuration.yaml" is indeed in the "my/local/path/data" directory (by reference to the content of the file you sent me)? Thank you. |
I can't send it now, but there is anything special, I connect like you, via socket on the network. I added this device settings, because the container wasn't starting without this map, then I added this, just to have z2m running. |
What if you execute the following: |
Running 1.39.1 with SLZB-06 and no issues. Running 20230507 |
Hmmmm It is the output
And the process end 🤔 Hmmm maybe it is the reason because it keep restarting, the process end and try to start again.... I'm running in a arm server (rock64) |
Hey @Arn0uDz I guess the error isn't related with slzb-06, for some reason z2m isn't starting using docker 🥲 |
I tested in other server (x86_64) and it started I guess it is related with arm64 architecture 🥲 Output (server running x86_64)
|
Ok good news the problem was related with the docker image, I removed the image and downloaded again, and it started ❤️ now I am facing the issue bellow
|
Ok it worked :) I removed config and coordinator file, and let the z2m generate again, copied mqqt and serial config from my old config and it is working without any issue. thank you @Koenkk for your support Note: as I removed the coordinator fine I lost my devices and I need to put again in z2m 😄 |
What happened?
after update to version 1.39.1 the z2m does not start
What did you expect to happen?
it starts
How to reproduce it (minimal and precise)
update z2m image from 1.39.0 to 1.39.1 and it gonna see the message bellow
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Zigbee2MQTT version
1.39.1
Adapter firmware version
20240527
Adapter
slzb-06
Setup
docker container
Debug log
I just can see this error
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
Using '/app/data' as data directory
even if I set log_level: debug
The text was updated successfully, but these errors were encountered: