Interface web erreur 502 bad gateway

Bonjour, je me prends la tête depuis 2 jours. Je viens de reinstaller un HomeAssistant vierge en natif (pas d’autre Os). J’ai installé mosquito et zigbee2mqtt, mais ne parviens pas à le faire fonctionner. J’ai une erreur Zigbee2MQTT:error 2024-02-08 19:22:25 : Erreur lors du démarrage de zigbee-herdsman.
mais je n’y arrive pas.
Je copie le fichier configuration.yaml de zigbee2mqtt et les captures d’écran de configuration dans le module zigbee2mqtt, la position de mon zigbee (conbee III).
si quelqu’un peut m’aider et m’expliquer ce qui ne va pas…

Configuration.yaml :

homeassistant: true
advanced:
  network_key:
    - 83
    - 58
    - 32
    - 74
    - 183
    - 138
    - 78
    - 194
    - 100
    - 255
    - 13
    - 69
    - 99
    - 84
    - 186
    - 65
  pan_id: 64775
  ext_pan_id:
    - 169
    - 164
    - 126
    - 216
    - 158
    - 77
    - 79
    - 110
mqtt:
  server: mqtt://core-mosquito:1883
  user: mqtt_user
  password: Sertsi13800
serial:
  port: /dev/ttyUSB0
  adapter: deconz
  baudrate: 115200
frontend:
port: 8099

Configuration du module zigbee2mqtt:

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:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquito:1883
  user: mqtt_user
  password: Sertsi13800
serial:
  port: /dev/ttyUSB0
  adapter: deconz
  baudrate: 115200

journal d’erreur de zigbee2mqtt:
[13:33:50] INFO: Preparing to start…
[13:33:50] INFO: Socat not enabled
[13:33:51] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2024-02-09 13:33:53: Logging to console and directory: ‹ /config/zigbee2mqtt/log/2024-02-09.13-33-53 › filename: log.txt
Zigbee2MQTT:info 2024-02-09 13:33:53: Starting Zigbee2MQTT version 1.35.3 (commit #unknown)
Zigbee2MQTT:info 2024-02-09 13:33:53: Starting zigbee-herdsman (0.33.8)
Zigbee2MQTT:error 2024-02-09 13:34:03: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-09 13:34:03: Failed to start zigbee
Zigbee2MQTT:error 2024-02-09 13:34:03: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
Zigbee2MQTT:error 2024-02-09 13:34:03: Exiting…
Zigbee2MQTT:error 2024-02-09 13:34:03: undefined

Information de la cle conbeeIII et de son port :
Sous-système:tty

Chemin d’accès au périphérique:/dev/ttyUSB0

ID:`/dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0`

Attributs:

DEVLINKS: >- /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0 /dev/serial/by-path/pci-0000:00:14.0-usb-0:2:1.0-port0 DEVNAME: /dev/ttyUSB0 DEVPATH: /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/ttyUSB0/tty/ttyUSB0 
ID_BUS: usb ID_MODEL: ConBee_III 
ID_MODEL_ENC: ConBee\x20III 
ID_MODEL_ID: '6015' ID_PATH: pci-0000:00:14.0-usb-0:2:1.0 
ID_PATH_TAG: pci-0000_00_14_0-usb-0_2_1_0 
ID_REVISION: '1000' ID_SERIAL: dresden_elektronik_ConBee_III_DE03188471 
ID_SERIAL_SHORT: DE03188471 
ID_TYPE: generic 
ID_USB_DRIVER: ftdi_sio 
ID_USB_INTERFACES: ':ffffff:' 
ID_USB_INTERFACE_NUM: '00' 
ID_USB_MODEL: ConBee_III 
ID_USB_MODEL_ENC: ConBee\x20III 
ID_USB_MODEL_ID: '6015' 
ID_USB_REVISION: '1000'
ID_USB_SERIAL: dresden_elektronik_ConBee_III_DE03188471
ID_USB_SERIAL_SHORT: DE03188471 
ID_USB_TYPE: generic ID_USB_VENDOR: dresden_elektronik 
ID_USB_VENDOR_ENC: dresden\x20elektronik 
ID_USB_VENDOR_ID: '0403'
ID_VENDOR: dresden_elektronik 
ID_VENDOR_ENC: dresden\x20elektronik 
ID_VENDOR_ID: '0403' 
MAJOR: '188' 
MINOR: '0' 
SUBSYSTEM: tty 
TAGS: ':systemd:' 
USEC_INITIALIZED: '3091845856'

Bonjour,

Peux-tu éditer ton post pour mettre en bloc de code tes fichiers de configuration, sinon c’est illisible. Tu peux sélectrionner le texte et utiliser le bouton:
image

Merci

Bonjour Cloom,
Désolé, je suis nouveau sur le forum et un presque débutant en domotique.
j’y songerai la prochaine fois.
merci de ton commentaire.

1 « J'aime »

Merci, bien plus facile à lire :slight_smile:

Essaye:

  1. Remplacer /dev/ttyUSB0 par
    /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0
  2. Activer le debug pour herdsman dans l’onglet configuration du module complémentaire Z2M, on aura plus de détails :slight_smile: :

Bonjour Cloom,
merci pour ta réponse, mais cela ne fonctionne pas.
Voici les logs (avec debug herdsman) du zigbee2mqtt:

[08:36:12] INFO: Preparing to start...
[08:36:13] INFO: Socat not enabled
[08:36:13] INFO: Zigbee Herdsman debug logging enabled
[08:36:13] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:debug 2024-02-10 08:36:15: Can't load state from file /config/zigbee2mqtt/state.json (doesn't exist)
Zigbee2MQTT:info  2024-02-10 08:36:15: Logging to console and directory: '/config/zigbee2mqtt/log/2024-02-10.08-36-15' filename: log.txt
Zigbee2MQTT:info  2024-02-10 08:36:15: Starting Zigbee2MQTT version 1.35.3 (commit #unknown)
Zigbee2MQTT:info  2024-02-10 08:36:15: Starting zigbee-herdsman (0.33.8)
Zigbee2MQTT:debug 2024-02-10 08:36:15: 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":[169,164,126,216,158,77,79,110],"networkKey":"HIDDEN","panID":64775},"serialPort":{"path":"/dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0"}}'
2024-02-10T07:36:15.304Z zigbee-herdsman:adapter Failed to validate path: 'Error: spawn udevadm ENOENT'
2024-02-10T07:36:15.306Z zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[83,58,32,74,183,138,78,194,100,255,13,69,99,84,186,65],"panID":64775,"extendedPanID":[169,164,126,216,158,77,79,110],"channelList":[11]},"serialPort":{"path":"/dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0"},"databasePath":"/config/zigbee2mqtt/database.db","databaseBackupPath":"/config/zigbee2mqtt/database.db.backup","backupPath":"/config/zigbee2mqtt/coordinator_backup.json","adapter":{"disableLED":false,"concurrent":null,"delay":null}}'
2024-02-10T07:36:15.306Z zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with {"path":"/dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-02-10T07:36:15.311Z zigbee-herdsman:adapter:zStack:znp:log Serialport opened
2024-02-10T07:36:15.312Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-02-10T07:36:15.313Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-02-10T07:36:15.323Z zigbee-herdsman:adapter:zStack:unpi:parser <-- [0,192]
2024-02-10T07:36:15.324Z zigbee-herdsman:adapter:zStack:unpi:parser --- parseNext [0,192]
2024-02-10T07:36:15.566Z zigbee-herdsman:adapter:zStack:znp:log Writing CC2530/CC2531 skip bootloader payload
2024-02-10T07:36:15.566Z zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239]
2024-02-10T07:36:16.569Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-02-10T07:36:16.571Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-02-10T07:36:16.823Z zigbee-herdsman:adapter:zStack:znp:log Skip bootloader for CC2652/CC1352
2024-02-10T07:36:17.282Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-02-10T07:36:17.283Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-02-10T07:36:23.285Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-02-10T07:36:23.287Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
2024-02-10T07:36:29.295Z zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1}
2024-02-10T07:36:29.296Z zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32]
Zigbee2MQTT:error 2024-02-10 08:36:35: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-10 08:36:35: Failed to start zigbee
Zigbee2MQTT:error 2024-02-10 08:36:35: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-02-10 08:36:35: Exiting...
Zigbee2MQTT:error 2024-02-10 08:36:35: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
    at Zigbee.start (/app/lib/zigbee.ts:60:27)
    at Controller.start (/app/lib/controller.ts:109:27)
    at start (/app/index.js:107:5)

POur moi l’erreur est le pb de demarrage de zigbee-herdsman :

Zigbee2MQTT:error 2024-02-10 08:36:35: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-10 08:36:35: Failed to start zigbee

mais je ne comprends pas ce qui provoque cette erreur?
merci de ton aide

Je complète. depuis ce matin, mon broker mosquito ne se lance plus non plus.
voici les logs de mosquito broker :

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[08:30:49] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[08:30:49] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[08:30:50] INFO: Starting mosquitto MQTT broker...
2024-02-10 08:30:50: Warning: Mosquitto should not be run as root/administrator.
2024-02-10 08:30:50: mosquitto version 2.0.18 starting
2024-02-10 08:30:50: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-02-10 08:30:50: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-02-10 08:30:50:  ├── Username/password checking enabled.
2024-02-10 08:30:50:  ├── TLS-PSK checking enabled.
2024-02-10 08:30:50:  └── Extended authentication not enabled.
2024-02-10 08:30:50: Opening ipv4 listen socket on port 1883.
2024-02-10 08:30:50: Opening ipv6 listen socket on port 1883.
2024-02-10 08:30:50: Opening websockets listen socket on port 1884.
2024-02-10 08:30:50: mosquitto version 2.0.18 running
2024-02-10 08:30:50: New connection from 127.0.0.1:60120 on port 1883.
2024-02-10 08:30:50: Client <unknown> disconnected due to protocol error.
[08:30:50] INFO: Successfully send discovery information to Home Assistant.
[08:30:50] INFO: Successfully send service information to the Supervisor.
2024-02-10 08:32:53: New connection from 172.30.32.1:35805 on port 1883.
2024-02-10 08:32:53: New client connected from 172.30.32.1:35805 as 3ujE8Y2RvnmXnbDslJM3dK (p2, c1, k60, u'mqtt_adm').
2024-02-10 08:43:38: Client 3ujE8Y2RvnmXnbDslJM3dK closed its connection.
2024-02-10 08:43:52: New connection from 172.30.32.1:48519 on port 1883.
2024-02-10 08:43:52: New client connected from 172.30.32.1:48519 as 6MwWIqdwKkzIt6EKcKkLD3 (p2, c1, k60, u'mqtt_adm').
2024-02-10 08:58:47: New connection from 172.30.32.1:34619 on port 1883.
2024-02-10 08:58:47: New client connected from 172.30.32.1:34619 as 3VFZTXhZdrA3XlS83E4rzu (p2, c1, k60, u'mqtt_user').
2024-02-10 08:58:47: Client 3VFZTXhZdrA3XlS83E4rzu disconnected.
2024-02-10 08:58:50: New connection from 172.30.32.1:45081 on port 1883.
2024-02-10 08:58:50: New client connected from 172.30.32.1:45081 as 2ybGqyUh6d7Me7QUeTwIEY (p2, c1, k60, u'mqtt_user').
2024-02-10 09:00:25: Client 6MwWIqdwKkzIt6EKcKkLD3 has exceeded timeout, disconnecting.
2024-02-10 09:00:50: Saving in-memory database to /data//mosquitto.db.
2024-02-10 09:03:47: New connection from 172.30.32.1:53115 on port 1883.
2024-02-10 09:03:47: New client connected from 172.30.32.1:53115 as 3gVcCDf29nwmqajxK5Yzhn (p2, c1, k60, u'mqtt_user').
2024-02-10 09:03:47: Client 3gVcCDf29nwmqajxK5Yzhn disconnected.

la j’avoue j’ai beau essayer de comprendre, …
on dirait que ca se alnce bien, après il fait de nouvelles connexions (a quoi?) et enfin il deconnecte le client (pourquoi?)

Bonsoir,
Gràce à …moi-même je viens de toruver tout seul comme un grand.
Finalement ma config zigbee2mqtt est la suivante :

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:
  server: mqtt://192.168.1.180:1883
  user: mqtt_user
  password: Sertsi13800
serial:
  port: /dev/serial/by-id/usb-dresden_elektronik_ConBee_III_DE03188471-if00-port0
  adapter: deconz
  baudrate: 115200
zigbee_herdsman_debug: true

L’avantage, c’est que je vais retenir la manip.
Merci tout de même à Cloom pour son aide

Donc qu’est-ce qui a enlevé ton erreur? De mettre le port avec le lien by-id?

Et pour ton MQTT tu as mis l’adresse IP au lieu de mqtt://core-mosquito:1883 car tu n’utilises pas l’addon MQTT dans HAOS?

Désolé jai oublie de donner ma solution.
Javais deja essayé avec la ligne du port de la cle conbee, mais ca n’avait pas marché.je l ai quand même laissée.et jai mis l’adresse ip de mon home assistant et c’est ca, pour moi, qui a résolu le pb.