(solved) Sonoff Dongle-E is not working with HA

Hi,
I got a Sonoff ZBDongle E and connected it to my Raspberry with HA. He started working, but during connecting the first device he stopped working and I don´t get it working again…

Server: Raspberry 5
OS: HA
HA: 2025.11.3
Zigbee2MQTT: 2.7.1-1
Dongle-Version: 8.0.2
I tried to connect it directly to Raspberry and via cable, all 4 USB ports, no difference.
The power supply should be ok, I have no other issues and there are no rlated entries in the log
I did the firmware update with Sonoff HA Add-On, so the dongle seems to work and the concnetion should be also fine, Only Zigbee2MQTT doesn´t work with it.

In the log I see this:

[15:12:24] INFO: Preparing to start...
[15:12:24] INFO: Socat not enabled
[15:12:25] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-12-07 15:13:08] info: 	z2m: Logging to console, file (filename: log.log)
[2025-12-07 15:13:08] info: 	z2m: Starting Zigbee2MQTT version 2.7.1 (commit #unknown)
[2025-12-07 15:13:08] info: 	z2m: Starting zigbee-herdsman (7.0.4)
[2025-12-07 15:13:08] info: 	zh:adapter:discovery: Matched adapter: {"path":"/dev/ttyUSB0","manufacturer":"Itead","serialNumber":"404fb23782c2ef119a23c6138148b910","pnpId":"usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_404fb23782c2ef119a23c6138148b910-if00-port0","vendorId":"10c4","productId":"ea60"} => ember: 4
[2025-12-07 15:13:08] info: 	zh:ember: Using default stack config.
[2025-12-07 15:13:08] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-12-07 15:13:08] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-12-07 15:13:08] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-12-07 15:13:08] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-12-07 15:13:08] info: 	zh:ember:uart:ash: Serial port opened
[2025-12-07 15:13:08] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-12-07 15:13:10] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-12-07 15:13:10] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-12-07 15:13:10] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-12-07 15:13:10] info: 	zh:ember: Adapter EZSP protocol version (14) lower than Host. Switched.
[2025-12-07 15:13:10] info: 	zh:ember: Adapter version info: {"ezsp":14,"revision":"8.0.2 [GA]","build":397,"major":8,"minor":0,"patch":2,"special":0,"type":170}
[2025-12-07 15:13:10] error: 	zh:ember:uart:ash: Received frame with CRC error
[2025-12-07 15:13:10] error: 	zh:ember:uart:ash: Received frame with CRC error
[2025-12-07 15:13:10] error: 	zh:ember:uart:ash: Received frame with CRC error
[2025-12-07 15:13:11] error: 	zh:ember:uart:ash: Received frame with CRC error
[2025-12-07 15:13:13] error: 	zh:ember:uart:ash: Received frame with CRC error
[2025-12-07 15:13:16] error: 	zh:ember:uart:ash: Received ERROR from adapter, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2025-12-07 15:13:16] error: 	zh:ember:uart:ash: ASH disconnected | Adapter status: ASH_NCP_FATAL_ERROR
[2025-12-07 15:13:16] error: 	zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2025-12-07 15:13:16] error: 	zh:ember: Adapter fatal error: HOST_FATAL_ERROR
[2025-12-07 15:13:20] error: 	z2m: Error while starting zigbee-herdsman
[2025-12-07 15:13:20] error: 	z2m: Failed to start zigbee-herdsman
[2025-12-07 15:13:20] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-12-07 15:13:20] error: 	z2m: Exiting...
[2025-12-07 15:13:20] error: 	z2m: Error: [INIT TC] Network init timed out after 10000ms
    at Object.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:285:23)
    at EmberOneWaitress.startWaitingForEvent (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/oneWaitress.ts:310:63)
    at EmberAdapter.initTrustCenter (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:870:36)
    at runNextTicks (node:internal/process/task_queues:65:5)
    at processImmediate (node:internal/timers:453:9)
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:708:18)
    at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1539:24)
    at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:143:29)
    at Zigbee.start (/app/lib/zigbee.ts:70:27)
    at Controller.start (/app/lib/controller.ts:101:13)

configuration.yaml:

version: 4
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://core-mosquitto:1883
  user: xxx
  password: xxx
serial:
  port: /dev/ttyUSB0
  adapter: ember
  baudrate: 115200
  rtscts: false
advanced:
  log_level: info
  channel: 11
  network_key:
    - 205
    - 116
    - 83
    - 239
    - 133
    - 213
    - 148
    - 43
    - 49
    - 98
    - 62
    - 141
    - 64
    - 114
    - 25
    - 102
  pan_id: 34501
  ext_pan_id:
    - 158
    - 77
    - 25
    - 95
    - 126
    - 84
    - 132
    - 235
frontend:
  enabled: true
  port: 8099
homeassistant:
  enabled: true
onboarding: true

ZHA ist not installed at this point.

I alsso tried it with ZHA instead Z2M but it is also not working. It seems something is blocking the dongle for all other operations except flashing it… And yes, the flashing Add-On is stopped.

I tried to solve it with ChatGPT, but no success. Has anyone an idea how to solve?

Br, Michael

I solved it: I had to restart the whole server (not HA only)

You may have run into this, and the reboot swapped the ports again due to a race condition and it worked OK this time…
The TTY ports can sometimes change internally, so it is suggested to use the /serial/by-id/ URL that always talks to your dongle by serial so it is always right.
You can find out what that is by using:

and looking for it under all hardware, something like this:

Once you have the long URL use that instead of the ttyxxx one.

If you are using a Container installation, this is how to see the /serial/by-id/ URL:
ls -l /dev/serial/by-id