[RÉSOLU] Équipement zigbee non détecté

Quentin57520 · Novembre 1, 2023, 5:08

Bonsoir à tous,

Depuis peu je suis propriétaire d’un Raspberry 4 avec HA installé dessus (je débute totalement), il boot sur un SSD et le tout est monté dans un boitier NASPi v2 avec une clé ConBee II connectée en direct.

J’ai installé Mosquitto broken, Zigbee2MQTT ainsi que le terminal.
Sauf que quand je lance une détection pour appairer mes interrupteur de volet Wiser, ces derniers ne sont pas détectés (alors que quand je fonctionnais sans le boitier NASPi et le SSD, c’était bon ! Sauf que je n’ai pas pensé à faire une sauvegarde de l’image de ma MicroSD quand je suis passé sur le SSD, mais uniquement des fichiers présents sur ma SD )

Détail important, le problème ne vient pas des interrupteurs de volets Wiser, mais pas de HA (sans doute la config que je vais détailler ci-dessous) car je possède le passerelle Wiser Gen.2 et que je lance un appairage, ils sont immédiatement détectés !

Donc si quelqu’un à une idée du problème, c’est dommage de bloquer dès le départ.

Configuration Mosquitto broken :

Logins :
- username: mqtt
  password: mqtt

Configuration 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-mosquitto
user: mqtt
password: mqtt


serial :
port: /dev/ttyACM0
adapter: deconz

EDIT: En rajoutant une rallonge de 2 mètres USB pour la clé ConBee II, j’ai pu installer l’intégration ConBee II, mais par contre quand je vais sous Zigbee2MQTT, quand je lance un appairage, le compteur de temps ne s’affiche pas et j’ai un message d’erreur qui s’affiche dans une bull rouge avec le message « APS Timeout »

Nothing · Novembre 1, 2023, 5:32

Bj

ce qui nous intéresse c’est les journaux et la référence de tes boitier Wiser
tes Wiser, a tu verifier si compatible Z2M ???

anon41081891 · Novembre 1, 2023, 5:34

Bonsoir, il faut au préalable les désappairer de ta passerelle avant d’essayer de les appairer à Z2M

Quentin57520 · Novembre 1, 2023, 5:41

@Nothing : Oui ils sont bien compatible Zigbee 3.0. J’avais réussi à les appairer sur mon raspberry quand je tournais sur la SD. Voici le modèle pour information : [S520567W - SCHNEIDER] Commande pour volets roulants Odace Wiser

@anon41081891 : Ils sont tous dissociés, j’avais juste fais un essais pour tenter d’identifier le problème, en l’occurrence, le raspberry…

J’ai édité mon premier message avec quelques informations supplémentaires en bas

Barbotx · Novembre 1, 2023, 5:43

Bonsoir,
Tu ne peux pas installer l’intégration ZHA et Z2M, avec une clé.

Quentin57520 · Novembre 1, 2023, 5:45

D’accord, donc je dois tout simplement la supprimer si je comprends bien ?

Barbotx · Novembre 1, 2023, 5:45

pour commencer , oui.

Nothing · Novembre 1, 2023, 5:46

tu as tous ce qui te faut la

Barbotx · Novembre 1, 2023, 5:46

Après, comme a dit Nothing, il nous faut les logs.

Quentin57520 · Novembre 1, 2023, 5:55

voici le journal de Mosquitto broken :

2023-11-01 17:37:36: Saving in-memory database to /data//mosquitto.db.
2023-11-01 17:38:17: New connection from 172.30.32.2:55602 on port 1883.
2023-11-01 17:38:17: Client <unknown> closed its connection.
2023-11-01 17:40:17: New connection from 172.30.32.2:48184 on port 1883.
2023-11-01 17:40:17: Client <unknown> closed its connection.
2023-11-01 17:42:17: New connection from 172.30.32.2:35240 on port 1883.
2023-11-01 17:42:17: Client <unknown> closed its connection.
2023-11-01 17:44:17: New connection from 172.30.32.2:46250 on port 1883.
2023-11-01 17:44:17: Client <unknown> closed its connection.
2023-11-01 17:46:17: New connection from 172.30.32.2:41174 on port 1883.
2023-11-01 17:46:17: Client <unknown> closed its connection.
2023-11-01 17:48:17: New connection from 172.30.32.2:52322 on port 1883.
2023-11-01 17:48:17: Client <unknown> closed its connection.
2023-11-01 17:50:17: New connection from 172.30.32.2:43240 on port 1883.
2023-11-01 17:50:17: Client <unknown> closed its connection.
2023-11-01 17:52:17: New connection from 172.30.32.2:53568 on port 1883.
2023-11-01 17:52:17: Client <unknown> closed its connection.
2023-11-01 17:54:17: New connection from 172.30.32.2:34056 on port 1883.
2023-11-01 17:54:17: Client <unknown> closed its connection.
2023-11-01 17:56:17: New connection from 172.30.32.2:43600 on port 1883.
2023-11-01 17:56:17: Client <unknown> closed its connection.
2023-11-01 17:58:17: New connection from 172.30.32.2:52988 on port 1883.
2023-11-01 17:58:17: Client <unknown> closed its connection.
2023-11-01 18:00:17: New connection from 172.30.32.2:40172 on port 1883.
2023-11-01 18:00:17: Client <unknown> closed its connection.
2023-11-01 18:02:17: New connection from 172.30.32.2:48568 on port 1883.
2023-11-01 18:02:17: Client <unknown> closed its connection.
2023-11-01 18:04:17: New connection from 172.30.32.2:42602 on port 1883.
2023-11-01 18:04:17: Client <unknown> closed its connection.
2023-11-01 18:06:17: New connection from 172.30.32.2:52792 on port 1883.
2023-11-01 18:06:17: Client <unknown> closed its connection.
2023-11-01 18:07:37: Saving in-memory database to /data//mosquitto.db.
2023-11-01 18:08:17: New connection from 172.30.32.2:46036 on port 1883.
2023-11-01 18:08:17: Client <unknown> closed its connection.
2023-11-01 18:10:17: New connection from 172.30.32.2:47134 on port 1883.
2023-11-01 18:10:17: Client <unknown> closed its connection.
2023-11-01 18:12:17: New connection from 172.30.32.2:36918 on port 1883.
2023-11-01 18:12:17: Client <unknown> closed its connection.
2023-11-01 18:13:47: Client 26mN7bAEpT7GElcZFTMQCt closed its connection.
2023-11-01 18:14:15: New connection from 172.30.32.1:47941 on port 1883.
2023-11-01 18:14:15: New client connected from 172.30.32.1:47941 as 2TvP0gYmDnAhkBaHl2jdgP (p2, c1, k60, u'homeassistant').
2023-11-01 18:14:17: New connection from 172.30.32.2:40410 on port 1883.
2023-11-01 18:14:17: Client <unknown> closed its connection.
2023-11-01 18:16:17: New connection from 172.30.32.2:47892 on port 1883.
2023-11-01 18:16:17: Client <unknown> closed its connection.
2023-11-01 18:18:17: New connection from 172.30.32.2:54384 on port 1883.
2023-11-01 18:18:17: Client <unknown> closed its connection.
2023-11-01 18:20:17: New connection from 172.30.32.2:51332 on port 1883.
2023-11-01 18:20:17: Client <unknown> closed its connection.
2023-11-01 18:22:17: New connection from 172.30.32.2:53732 on port 1883.
2023-11-01 18:22:17: Client <unknown> closed its connection.
2023-11-01 18:22:33: Client 2TvP0gYmDnAhkBaHl2jdgP closed its connection.
2023-11-01 18:22:48: Client mqttjs_1f4e08b7 closed its connection.
2023-11-01 18:23:00: New connection from 172.30.33.1:37224 on port 1883.
2023-11-01 18:23:00: New client connected from 172.30.33.1:37224 as mqttjs_231f74de (p2, c1, k60, u'mqtt').
2023-11-01 18:23:01: New connection from 172.30.32.1:54285 on port 1883.
2023-11-01 18:23:01: New client connected from 172.30.32.1:54285 as 3cMf8J9OKyL5FL9gIm6YXG (p2, c1, k60, u'homeassistant').
2023-11-01 18:24:17: New connection from 172.30.32.2:49448 on port 1883.
2023-11-01 18:24:17: Client <unknown> closed its connection.
2023-11-01 18:26:17: New connection from 172.30.32.2:36076 on port 1883.
2023-11-01 18:26:17: Client <unknown> closed its connection.
2023-11-01 18:28:17: New connection from 172.30.32.2:57290 on port 1883.
2023-11-01 18:28:17: Client <unknown> closed its connection.
2023-11-01 18:30:17: New connection from 172.30.32.2:41070 on port 1883.
2023-11-01 18:30:17: Client <unknown> closed its connection.
2023-11-01 18:31:04: Client 3cMf8J9OKyL5FL9gIm6YXG closed its connection.
2023-11-01 18:31:23: New connection from 172.30.32.1:55563 on port 1883.
2023-11-01 18:31:23: New client connected from 172.30.32.1:55563 as 5K5p4t7uyUaESNqDKOcROd (p2, c1, k60, u'homeassistant').
2023-11-01 18:32:17: New connection from 172.30.32.2:55696 on port 1883.
2023-11-01 18:32:17: Client <unknown> closed its connection.
2023-11-01 18:34:17: New connection from 172.30.32.2:37964 on port 1883.
2023-11-01 18:34:17: Client <unknown> closed its connection.
2023-11-01 18:35:18: Client 5K5p4t7uyUaESNqDKOcROd closed its connection.
2023-11-01 18:35:46: New connection from 172.30.32.1:52139 on port 1883.
2023-11-01 18:35:46: New client connected from 172.30.32.1:52139 as 36uMWSn7PBl6MfoIu2eWoh (p2, c1, k60, u'homeassistant').
2023-11-01 18:36:17: New connection from 172.30.32.2:38076 on port 1883.
2023-11-01 18:36:17: Client <unknown> closed its connection.
2023-11-01 18:37:38: Saving in-memory database to /data//mosquitto.db.
2023-11-01 18:38:17: New connection from 172.30.32.2:57840 on port 1883.
2023-11-01 18:38:17: Client <unknown> closed its connection.
2023-11-01 18:40:17: New connection from 172.30.32.2:60612 on port 1883.
2023-11-01 18:40:17: Client <unknown> closed its connection.
2023-11-01 18:42:17: New connection from 172.30.32.2:44258 on port 1883.
2023-11-01 18:42:17: Client <unknown> closed its connection.
2023-11-01 18:44:17: New connection from 172.30.32.2:52402 on port 1883.
2023-11-01 18:44:17: Client <unknown> closed its connection.
2023-11-01 18:46:17: New connection from 172.30.32.2:46734 on port 1883.
2023-11-01 18:46:17: Client <unknown> closed its connection.
2023-11-01 18:46:33: Client 36uMWSn7PBl6MfoIu2eWoh closed its connection.
2023-11-01 18:47:00: New connection from 172.30.32.1:41327 on port 1883.
2023-11-01 18:47:00: New client connected from 172.30.32.1:41327 as 4HbbJExOBpwGmVjFS5xeRO (p2, c1, k60, u'homeassistant').
2023-11-01 18:48:17: New connection from 172.30.32.2:40490 on port 1883.
2023-11-01 18:48:17: Client <unknown> closed its connection.
2023-11-01 18:50:17: New connection from 172.30.32.2:52592 on port 1883.
2023-11-01 18:50:17: Client <unknown> closed its connection.
2023-11-01 18:50:24: Client 4HbbJExOBpwGmVjFS5xeRO closed its connection.
2023-11-01 18:50:47: New connection from 172.30.32.1:37865 on port 1883.
2023-11-01 18:50:47: New client connected from 172.30.32.1:37865 as 5QFtCGNh4G81Win4Jb06f0 (p2, c1, k60, u'homeassistant').
2023-11-01 18:52:17: New connection from 172.30.32.2:52430 on port 1883.
2023-11-01 18:52:17: Client <unknown> closed its connection.

et voilà celui de Zigbee2MQTT :

[18:22:49] INFO: Preparing to start...
[18:22:50] INFO: Socat not enabled
[18:22:52] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-11-01 18:22:59: Logging to console and directory: '/config/zigbee2mqtt/log/2023-11-01.18-22-59' filename: log.txt
Zigbee2MQTT:info  2023-11-01 18:22:59: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-11-01 18:22:59: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:info  2023-11-01 18:23:00: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-11-01 18:23:00: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:info  2023-11-01 18:23:00: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-11-01 18:23:00: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-11-01 18:23:00: Connecting to MQTT server at mqtt://core-mosquitto
Zigbee2MQTT:info  2023-11-01 18:23:01: Connected to MQTT server
Zigbee2MQTT:info  2023-11-01 18:23:01: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-11-01 18:23:01: Started frontend on port 0.0.0.0:8099
Zigbee2MQTT:info  2023-11-01 18:23:01: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"unknown","coordinator":{"meta":{"maintrel":0,"majorrel":38,"minorrel":114,"product":0,"revision":"0x26720700","transportrev":0},"type":"ConBee2/RaspBee2"},"log_level":"info","network":{"channel":11,"extendedPanID":"0x3b109baad7456ee3","panID":61828},"permit_join":false,"version":"1.33.1"}'
Zigbee2MQTT:info  2023-11-01 18:23:01: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
Zigbee2MQTT:info  2023-11-01 18:23:01: Zigbee2MQTT started!
Zigbee2MQTT:info  2023-11-01 18:33:12: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:33:33: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:33:45: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:34:14: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:34:18: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:34:18: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"b7u0l-1"}'
Zigbee2MQTT:info  2023-11-01 18:34:22: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:34:31: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:34:38: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:34:38: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"b7u0l-2"}'
Zigbee2MQTT:error 2023-11-01 18:34:50: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:34:50: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"b7u0l-3"}'
Zigbee2MQTT:error 2023-11-01 18:35:19: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:35:19: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"jvtqz-1"}'
Zigbee2MQTT:error 2023-11-01 18:35:27: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:35:27: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"jvtqz-2"}'
Zigbee2MQTT:error 2023-11-01 18:35:36: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:35:36: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"jvtqz-3"}'
Zigbee2MQTT:info  2023-11-01 18:36:24: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:37:29: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:37:29: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"5v579-1"}'
Zigbee2MQTT:info  2023-11-01 18:45:46: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:46:51: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:46:51: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"gpbuv-1"}'
Zigbee2MQTT:info  2023-11-01 18:50:09: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:51:14: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:51:14: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"5i1pq-1"}'
Zigbee2MQTT:info  2023-11-01 18:51:19: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:51:35: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2023-11-01 18:51:48: Zigbee: allowing new devices to join.
Zigbee2MQTT:error 2023-11-01 18:52:24: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:52:24: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"xfp4n-1"}'
Zigbee2MQTT:error 2023-11-01 18:52:41: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:52:41: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"xfp4n-2"}'
Zigbee2MQTT:error 2023-11-01 18:52:53: Request 'zigbee2mqtt/bridge/request/permit_join' failed with error: 'APS TIMEOUT'
Zigbee2MQTT:info  2023-11-01 18:52:53: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{},"error":"APS TIMEOUT","status":"error","transaction":"e41j7-1"}'

@Barbotx : J’ai bien ZHA comme suggéré

@Nothing : J’ai déjà suivi ce tuto. Je viens de le suivre à nouveau en supprimant le étapes 1 et 3 comme indiqué par WarC0zes et du coup le module Z2M ne démarre pas du tout, c’est pour ça que j’avais les paramètres que j’avais dans mon premier post et ça fonctionnait avant le SSD

Voici le journal de Z2M avec le tuto que tu m’as donné :

[19:03:47] INFO: Preparing to start...
[19:03:47] INFO: Socat not enabled
[19:03:49] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-11-01 19:03:55: Logging to console and directory: '/config/zigbee2mqtt/log/2023-11-01.19-03-55' filename: log.txt
Zigbee2MQTT:info  2023-11-01 19:03:55: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-11-01 19:03:55: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:error 2023-11-01 19:03:56: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-11-01 19:03:56: Failed to start zigbee
Zigbee2MQTT:error 2023-11-01 19:03:56: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-11-01 19:03:56: Exiting...
Zigbee2MQTT:error 2023-11-01 19:03:56: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2234130-if00'
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
    at /app/node_modules/@serialport/stream/dist/index.js:118:18

Barbotx · Novembre 1, 2023, 6:10

Il faut supprimer ZHA.
il faudrait que tu partage ta config Z2M en utilisant les sigles </>

Quentin57520 · Novembre 1, 2023, 6:12

@Barbotx : C’est fait, je l’ai indiqué dans mon message précédent
Je vais faire ça, j’éditerai ensuite ce post.

EDIT:

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-mosquitto
user: mqtt
password: mqtt

serial:

port: /dev/ttyACM0
adapter: deconz

Nothing · Novembre 1, 2023, 6:19

Quentin57520:

Zigbee2MQTT:error 2023-11-01 19:03:56: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2234130-if00'

Ton souci est ici essai de fixe ta cle

port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2234130-if00
adapter: deconz

au lieu de
port: /dev/ttyACM0

car si as d’autre cle , les ports peuvent s’inversé
ta zigbee est sur 0 , et des reboot va la mettre sur port: /dev/ttyACM1

Quentin57520 · Novembre 1, 2023, 6:25

@Nothing : Je dois fixer ma clé sur la base du tuto que tu m’as donné ?
Si oui, j’ai essayé, ça n’a pas fonctionné, voici le log :

[19:22:22] INFO: Preparing to start...
[19:22:23] INFO: Socat not enabled
[19:22:25] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-11-01 19:22:31: Logging to console and directory: '/config/zigbee2mqtt/log/2023-11-01.19-22-31' filename: log.txt
Zigbee2MQTT:info  2023-11-01 19:22:31: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-11-01 19:22:31: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:error 2023-11-01 19:22:31: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-11-01 19:22:31: Failed to start zigbee
Zigbee2MQTT:error 2023-11-01 19:22:31: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-11-01 19:22:31: Exiting...
Zigbee2MQTT:error 2023-11-01 19:22:32: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2234130-if00'
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
    at /app/node_modules/@serialport/stream/dist/index.js:118:18

Si c’était via la config Z2M que j’ai donné dans mon premier post, je vais essayer de suite, puis j’éditerai ce post !

EDIT: Ca ne fonctionne pas non plus et voici le log avec la config Z2M de mon premier post et en faisant la modification que tu m’as proposée :

[19:27:52] INFO: Preparing to start...
[19:27:53] INFO: Socat not enabled
[19:27:55] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-11-01 19:28:01: Logging to console and directory: '/config/zigbee2mqtt/log/2023-11-01.19-28-01' filename: log.txt
Zigbee2MQTT:info  2023-11-01 19:28:01: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-11-01 19:28:01: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:error 2023-11-01 19:28:01: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-11-01 19:28:01: Failed to start zigbee
Zigbee2MQTT:error 2023-11-01 19:28:01: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-11-01 19:28:01: Exiting...
Zigbee2MQTT:error 2023-11-01 19:28:01: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2234130-if00'
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/deconz/driver/driver.ts:200:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
    at /app/node_modules/@serialport/stream/dist/index.js:118:18

Je précise que je n’ai pas d’autre clé, j’ai uniquement la ConBee II. Le SSD est lui aussi branché en USB via un pont USB mâle/mâle SSD qui était fourni avec le boîtier NASPi V2.

Quentin57520 · Novembre 1, 2023, 6:38

J’ai désinstallé ZHA, puis Mosquitto broken et Z2M et le compte mqtt.

J’ai réinstallé Mosquitto broke avec comme config :

Logins:

- username: mqtt
  password: mqtt

puis réinstallé Z2M avec comme config:

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-mosquitto
user: mqtt
password: mqtt

serial:

port: /dev/ttyACM0
adapter: deconz

puis créé l’utilisateur mqtt et maintenant ça fonctionne… Je ne pense pas avoir modifier quoi que ce soit par rapport avec la config de mon premier post… Étonnant

Nothing · Novembre 1, 2023, 6:43

tu avais zappe de le faire ?

Quentin57520 · Novembre 1, 2023, 6:47

@Nothing : Non c’était bien fait depuis mon premier post.
J’ai débranché la rallonge USB de ma clé ConBee II pour faire un branchement en direct sur l’USB puis fais un essai : échec
J’ai branché la rallonge USB sur la ConBee II puis fais un essai : fonctionnel
Je suppose que le fait de ne pas avoir la rallonge USB fait déconner la clé ?

Nothing · Novembre 1, 2023, 6:49

il es conseiller une rallonge !
Au pire un petit HUB alimenté

peux être que ta rallonge deconne …
et évité USB3 , connecte la clé.

Si pour toi c’est OK , mais ton sujet en résolu

Quentin57520 · Novembre 1, 2023, 6:54

C’est étonnant, car au début sans rallonge ça fonctionnait (sur le raspberry nu sans boîtier et sur la SD par contre !)
Un petit HUB ? C’est à dire ?
Ce n’est pas impossible pour la rallonge, je vais en acheter une autre !
Éviter l’USB3 ? Peux-tu m’expliquer aussi s’il te plaît ?

Oui le problème de base est résolu donc je vais faire ça !

Merci à tous ceux qui ont participé !

Nothing · Novembre 1, 2023, 6:56

comme ceci
c’est les deux que j’ai

https://www.amazon.fr/partager-connexion-plusieurs-périphériques-DUB-H7/dp/B0000B0DL7/ref=sr_1_5?crid=AQKCO8NMJNZ1&keywords=hub+usb+dlink&qid=1698864888&sprefix=hub+usb+d%2Caps%2C75&sr=8-5

ou

https://www.amazon.fr/gp/product/B07DNBQXRZ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1