Bonjour,
Je fais appel à la communauté pour une petite aide
Je n’arrive pas à paramétrer l’addon Zigbee2MQTT.
Je rencontre une erreur 502: Bad Gateway.
J’utilise Home Assistant sur un Raspberry PI 4 avec un Dongle Plus Sonoff
La clé semble bien être reconnu :
>
> /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ac1214afda5fec11abb82c5f25bfaa52-if00-port0
> Sous-système:
> tty
> Chemin d’accès au périphérique:
> /dev/ttyUSB0
> ID:
> /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ac1214afda5fec11abb82c5f25bfaa52-if00-port0
> Attributs:
> DEVLINKS: >-
> /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ac1214afda5fec11abb82c5f25bfaa52-if00-port0
> /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3.2:1.0-port0
> DEVNAME: /dev/ttyUSB0
> DEVPATH: >-
> /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3.2/1-1.3.2:1.0/ttyUSB0/tty/ttyUSB0
> ID_BUS: usb
> ID_MODEL: Sonoff_Zigbee_3.0_USB_Dongle_Plus
> ID_MODEL_ENC: Sonoff\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus
> ID_MODEL_ID: ea60
> ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3.2:1.0
> ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_3_2_1_0
> ID_REVISION: '0100'
> ID_SERIAL: ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ac1214afda5fec11abb82c5f25bfaa52
> ID_SERIAL_SHORT: ac1214afda5fec11abb82c5f25bfaa52
> ID_TYPE: generic
> ID_USB_DRIVER: cp210x
> ID_USB_INTERFACES: ':ff0000:'
> ID_USB_INTERFACE_NUM: '00'
> ID_VENDOR: ITead
> ID_VENDOR_ENC: ITead
> ID_VENDOR_ID: 10c4
> MAJOR: '188'
> MINOR: '0'
> SUBSYSTEM: tty
> TAGS: ':systemd:'
> USEC_INITIALIZED: '11731004'
Mon param est le suivant rien de bien compliquer :
> data_path: /config/zigbee2mqtt
> socat:
> enabled: false
> master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
> slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
> options: "-d -d"
> log: false
> mqtt: {}
> serial:
> port: /dev/ttyUSB0
> homeassistant: false
> permit_join: true
> zigbee_herdsman_debug: true
Ci-dessous les logs
[20:43:43] INFO: Preparing to start...
[20:43:43] INFO: Socat not enabled
[20:43:44] INFO: Zigbee Herdsman debug logging enabled
[20:43:46] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2023-04-12 20:43:53: Loaded state from file /config/zigbee2mqtt/state.json
Zigbee2MQTT:info 2023-04-12 20:43:53: Logging to console and directory: '/config/zigbee2mqtt/log/2023-04-12.20-43-53' filename: log.txt
Zigbee2MQTT:debug 2023-04-12 20:43:53: Removing old log directory '/config/zigbee2mqtt/log/2023-04-12.10-21-11'
Zigbee2MQTT:info 2023-04-12 20:43:54: Starting Zigbee2MQTT version 1.30.3 (commit #unknown)
Zigbee2MQTT:info 2023-04-12 20:43:54: Starting zigbee-herdsman (0.14.103)
Zigbee2MQTT:debug 2023-04-12 20:43:54: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null,"disableLED":false},"backupPath":"/config/zigbee2mqtt/coordinator_backup.json","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","databasePath":"/config/zigbee2mqtt/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyUSB0"}}'
2023-04-12T18:43:54.547Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2023-04-12T18:43:54.552Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyUSB0"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2023-04-12T18:43:54.554Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2023-04-12T18:43:54.575Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened
2023-04-12T18:43:54.580Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2023-04-12T18:43:54.584Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2023-04-12T18:43:54.841Z zigbee-herdsman:adapter:zStack:znp:log Writing CC2530/CC2531 skip bootloader payload
2023-04-12T18:43:54.844Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2023-04-12T18:43:55.847Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2023-04-12T18:43:55.849Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2023-04-12T18:43:56.101Z zigbee-herdsman:adapter:zStack:znp:log Skip bootloader for CC2652/CC1352
2023-04-12T18:43:56.617Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2023-04-12T18:43:56.619Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2023-04-12T18:44:02.625Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2023-04-12T18:44:02.626Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2023-04-12T18:44:08.634Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2023-04-12T18:44:08.635Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
Quelqu’un aurait une idée ?
Merci à vous.