Probleme 2MQTT suite a mise a jour ZBDongle-E

[Nurarihyon33]

Bonjour

Suite a la mise a jour de ma clé Sonoff ZBDongle-E, j’ai Zigbee2MQTT qui ne veut plus démarrer.

Voici le journal de démarrage 2MQTT:

[11:51:27] INFO: e[32mPreparing to start...e[0m
[11:51:27] INFO: e[32mSocat not enablede[0m
[11:51:27] INFO: e[32mStarting Zigbee2MQTT...e[0m
Starting Zigbee2MQTT without watchdog.
[2025-11-05 11:51:28] e[32minfoe[39m: 	z2m: Logging to console, file (filename: log.log)
[2025-11-05 11:51:28] e[32minfoe[39m: 	z2m: Starting Zigbee2MQTT version 2.6.3 (commit #unknown)
[2025-11-05 11:51:28] e[32minfoe[39m: 	z2m: Starting zigbee-herdsman (6.3.2)
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember: Using default stack config.
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember: ======== Ember Adapter Starting ========
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember:uart:ash: Serial port opened
[2025-11-05 11:51:28] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:33] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:33] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:38] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:38] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:43] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:43] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:48] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:48] e[32minfoe[39m: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:53] e[31merrore[39m: 	z2m: Error while starting zigbee-herdsman
[2025-11-05 11:51:53] e[31merrore[39m: 	z2m: Failed to start zigbee-herdsman
[2025-11-05 11:51:53] e[31merrore[39m: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-11-05 11:51:53] e[31merrore[39m: 	z2m: Exiting...
[2025-11-05 11:51:53] e[31merrore[39m: 	z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:665:19)
    at EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1547:24)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
    at Zigbee.start (/app/lib/zigbee.ts:67:27)
    at Controller.start (/app/lib/controller.ts:101:13)
    at start (/app/index.js:149:5)

[11:51:27] INFO: e[32mPreparing to start…e[0m
[11:51:27] INFO: e[32mSocat not enablede[0m
[11:51:27] INFO: e[32mStarting Zigbee2MQTT…e[0m
Starting Zigbee2MQTT without watchdog.
[2025-11-05 11:51:28] e[32minfoe[39m: z2m: Logging to console, file (filename: log.log)
[2025-11-05 11:51:28] e[32minfoe[39m: z2m: Starting Zigbee2MQTT version 2.6.3 (commit #unknown)
[2025-11-05 11:51:28] e[32minfoe[39m: z2m: Starting zigbee-herdsman (6.3.2)
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember: Using default stack config.
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember: ======== Ember Adapter Starting ========
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember:ezsp: ======== EZSP starting ========
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember:uart:ash: Serial port opened
[2025-11-05 11:51:28] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:33] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:33] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:38] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:38] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:43] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:43] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:48] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-11-05 11:51:48] e[32minfoe[39m: zh:ember:uart:ash: ======== ASH starting ========
[2025-11-05 11:51:53] e[31merrore[39m: z2m: Error while starting zigbee-herdsman
[2025-11-05 11:51:53] e[31merrore[39m: z2m: Failed to start zigbee-herdsman
[2025-11-05 11:51:53] e[31merrore[39m: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-11-05 11:51:53] e[31merrore[39m: z2m: Exiting…
[2025-11-05 11:51:53] e[31merrore[39m: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:665:19)
at EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1547:24)
at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@6.3.2/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:67:27)
at Controller.start (/app/lib/controller.ts:101:13)
at start (/app/index.js:149:5)

Que faire pour que cela refonctionne ?

Merci et bonne journée

[Idaho947]

Tu as pas ZHA qui est toujours là ? Tu as bien ignoré l’intégration ?
Ton port de clef n’a pas bougé ?

Tu as quoi dans ta config z2m ? Tu es bien en ember ?

[pascal_ha]

Salut,

tu as fait quelle mise à jour pour ta clé ?

Afin que l’on puisse t’aider :

• Peux-tu mettre le contenu complet de ton fichier de configuration.yaml de zigbee2mqtt
  il devrait ressembler à ceci : (pense a masquer tes mots de passe)

homeassistant:
  enabled: true
mqtt:
  server: mqtt://core-mosquitto:1883
  user: addons
  password: ton_mot_de_passe_a_masquer_!
  keepalive: 120
  reject_unauthorized: true
  version: 4
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221101080844-if00
  adapter: ember
frontend:
  enabled: true
  port: 8099
advanced:
...
...
...

• Peux-tu mettre la configuration de ton HA (comme demandé à la création d’un sujet)
  
  

Merci

[Nurarihyon33]

Voici les différentes choses demandées :

homeassistant:
  enabled: true
advanced:
  network_key:
    - 183
    - 34
    - 121
    - 165
    - 238
    - 233
    - 243
    - 137
    - 175
    - 170
    - 143
    - 48
    - 250
    - 222
    - 56
    - 226
  pan_id: 23227
  ext_pan_id:
    - 96
    - 104
    - 196
    - 46
    - 126
    - 6
    - 165
    - 122
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto:1883
  user: xxxx
  password: xxxx
serial:
  port: >-
    /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0
  adapter: ember
  baudrate: 115200
frontend:
  enabled: true
  port: 8099
device_options: {}
devices:
  '0xa4c1380346dfed24':
    friendly_name: Prise Ecran
  '0xa4c1387c7f451a3c':
    friendly_name: Prise PC
  '0x0ceff6fffe675c0a':
    friendly_name: Capteur Bureau
  '0x60b647fffe26f93d':
    friendly_name: Volet Roulant Bureau
  '0xf4b3b1fffed64a3f':
    friendly_name: VMC
  '0x0ceff6fffe675679':
    friendly_name: Capteur Salle de Bain Parents
  '0xa4c138ef727faf55':
    friendly_name: 'Réfrigérateur '
  '0xa4c1384dfc85dc3e':
    friendly_name: Switch Internet
  '0x842712fffe327090':
    friendly_name: Capteur Malaury
  '0x0ceff6fffe67d15d':
    friendly_name: Capteur Kiara
  '0x943469fffea29640':
    friendly_name: Spot Salon
  '0xa4c13855a537ae44':
    friendly_name: 'Congélateur '
  '0xa4c1386b70c78155':
    friendly_name: Prise Tv salon
  '0xa4c13860bfbdd01a':
    friendly_name: Serveur Home Assitant
  '0xa4c138c054b7abba':
    friendly_name: Lampe Kiara
  '0xd44867fffe2e5bc2':
    friendly_name: Capteur Salle a Manger
  '0xd44867fffe4beb67':
    friendly_name: Capteur Celier
  '0xd44867fffe58b3b2':
    friendly_name: Capteur Chambre Parents
version: 4

## System Information

version | core-2025.10.4
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
container_arch | amd64
user | root
virtualenv | false
python_version | 3.13.7
os_name | Linux
os_version | 6.12.51-haos
arch | x86_64
timezone | Europe/Paris
config_dir | /config

<details><summary>Home Assistant Community Store</summary>

GitHub API | ok
-- | --
GitHub Content | ok
GitHub Web | ok
HACS Data | ok
GitHub API Calls Remaining | 5000
Installed Version | 2.0.5
Stage | running
Available Repositories | 2346
Downloaded Repositories | 13

</details>

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 16.3
-- | --
update_channel | stable
supervisor_version | supervisor-2025.11.1
agent_version | 1.7.2
docker_version | 28.3.3
disk_total | 30.8 GB
disk_used | 10.4 GB
nameservers | 9.9.9.10, 9.9.9.9, fd0f:ee:b0::1, 1.0.0.1, 1.1.1.1
healthy | true
supported | true
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | kvm
board | ova
supervisor_api | ok
version_api | ok
installed_addons | File editor (5.8.0), Mosquitto broker (6.5.2), Advanced SSH & Web Terminal (21.0.4), Linky (1.6.1), Zigbee2MQTT (2.6.3-1), Samba share (12.5.4), Let's Encrypt (5.4.9), Node-RED (20.0.0), ESPHome Device Builder (2025.10.4)

</details>

<details><summary>Dashboards</summary>

dashboards | 3
-- | --
resources | 5
views | 7
mode | storage

</details>

<details><summary>Network Configuration</summary>

adapters | lo (disabled), enp0s18 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethe88057c (disabled), vethd148d3d (disabled), vethb389eb1 (disabled), vethfa7418b (disabled), vethbdc2db3 (disabled), vethc95c146 (disabled), vethf4fc969 (disabled), veth84ab1f0 (disabled), veth26ede30 (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), enp0s18 (192.168.1.160/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethe88057c (), vethd148d3d (), vethb389eb1 (), vethfa7418b (), vethbdc2db3 (), vethc95c146 (), vethf4fc969 (), veth84ab1f0 (), veth26ede30 ()
ipv6_addresses | lo (::1/128), enp0s18 (2a01:e0a:bb5:6400:c9dc:4e3d:2656:fb5f/64, fe80::778f:f3a1:f576:1363/64), hassio (fe80::8838:eeff:fe76:dc9/64), docker0 (fe80::cfc:54ff:fe18:86c7/64), vethe88057c (fe80::74a7:8cff:fe57:82ed/64), vethd148d3d (fe80::189a:7cff:fe10:db13/64), vethb389eb1 (fe80::e44c:91ff:fe71:cb76/64), vethfa7418b (fe80::f8b9:3fff:fec5:d277/64), vethbdc2db3 (fe80::1c4d:d8ff:fe3d:f05b/64), vethc95c146 (fe80::44a:9dff:feb7:f143/64), vethf4fc969 (fe80::bc8e:77ff:fe7c:3482/64), veth84ab1f0 (fe80::d0fb:93ff:fe3a:92fc/64), veth26ede30 (fe80::78eb:51ff:fe51:7214/64)
announce_addresses | 192.168.1.160, 2a01:e0a:bb5:6400:c9dc:4e3d:2656:fb5f, fe80::778f:f3a1:f576:1363

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 24 octobre 2025 à 12:50
-- | --
current_recorder_run | 5 novembre 2025 à 11:41
estimated_db_size | 193.62 MiB
database_engine | sqlite
database_version | 3.49.2

</details>

J‘ai flashé la clé sur le site Sonoff pour la mettre a jour en 8.0.2 ( j’étais en 7.4.4) car j’ai des problemes pour mettre a jour mes capteurs via 2MQTT

Merci der votre aide

[ddfdom]

Salut a voir l’adresse de ton dongle ce n’est pas du tout une sonoff type-E

Vérifies l’adresse de ton dongle dans la me u système de HA

[Nurarihyon33]

Voici ce que je trouve depuis la mise a jour, avant ce n’était pas la même adresse

 ttyUSB0 /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 Sous-système: tty Chemin d’accès au périphérique: /dev/ttyUSB0 ID: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 Attributs: DEVLINKS: >-   /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0   /dev/serial/by-path/pci-0000:01:1b.0-usb-0:1:1.0-port0   /dev/serial/by-path/pci-0000:01:1b.0-usbv2-0:1:1.0-port0 DEVNAME: /dev/ttyUSB0 DEVPATH: >-   /devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0 ID_BUS: usb ID_MODEL: CP2102_USB_to_UART_Bridge_Controller ID_MODEL_ENC: CP2102\x20USB\x20to\x20UART\x20Bridge\x20Controller ID_MODEL_ID: ea60 ID_PATH: pci-0000:01:1b.0-usb-0:1:1.0 ID_PATH_TAG: pci-0000_01_1b_0-usb-0_1_1_0 ID_PATH_WITH_USB_REVISION: pci-0000:01:1b.0-usbv2-0:1:1.0 ID_REVISION: '0100' ID_SERIAL: Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001 ID_SERIAL_SHORT: '0001' ID_TYPE: generic ID_USB_DRIVER: cp210x ID_USB_INTERFACES: ':ff0000:' ID_USB_INTERFACE_NUM: '00' ID_USB_MODEL: CP2102_USB_to_UART_Bridge_Controller ID_USB_MODEL_ENC: CP2102\x20USB\x20to\x20UART\x20Bridge\x20Controller ID_USB_MODEL_ID: ea60 ID_USB_REVISION: '0100' ID_USB_SERIAL: Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001 ID_USB_SERIAL_SHORT: '0001' ID_USB_TYPE: generic ID_USB_VENDOR: Silicon_Labs ID_USB_VENDOR_ENC: Silicon\x20Labs ID_USB_VENDOR_ID: 10c4 ID_VENDOR: Silicon_Labs ID_VENDOR_ENC: Silicon\x20Labs ID_VENDOR_ID: 10c4 MAJOR: '188' MINOR: '0' SUBSYSTEM: tty TAGS: ':systemd:' USEC_INITIALIZED: '2572900528'

[ddfdom]

N’aurais pas tu flasher par erreur un mauvais firmware ?

Tente de le refaire sur le site de sonoff directemen

[Nurarihyon33]

Je vais reflasher pour voir

[ddfdom]

Pourtant cela semble ok pour le firmware

Fais une capture de la partie hardware car là c’est difficilement lisible

[Nurarihyon33]

Pas de changement après le flash

J’ai oublier de préciser que je suis sous promox, je ne sais pas si cela change quelque chose

[Idaho947]

Et zha tu l’as bien ignoré ?

[Nurarihyon33]

oui ZHA bien ignoré, ca fais 2 ans que cela tourne sans probleme

[WarC0zes]

Première fois que je vois une telle adresse pour une Sonoff E

en général c’est :
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_XXXXXXXXXXX-if00

[ddfdom]

Ah peut être qu’il y’a eu un micmac au moment du bind dans proxmox

Tu as bien remis le dongle sur exactement le même port ?
Éteins puis redémarre ta VM et vérifie le port

[WarC0zes]

Oui, il y a un problème, ce sont les mêmes adresses sur ttyusbo et ttyusb1.
Un souci de passthrough usb sur ça VM ?

[Nurarihyon33]

Ca marche, j’ai du modifier dans promox le périphérique USB et remettre le bon nom dans la configuration de 2MQTT

Merci a vous pour votre aide

[WarC0zes]

Pense à mettre ton sujet en résolu, en cochant la case solution sur le message qui l’apporte.