Zigbee2MQTT restarting (NCP ASH counters)

My Zigbee2MQTT is continuously restarting. I recently had to change the adapter from ezsp to ember because of an update. I have a Sonoff stick E and updated to the latest firmware. This resulted in the following errors:

[2025-02-22 20:55:26] error:    zh:ember:uart:ash: Received frame with CRC error
[2025-02-22 20:55:26] error:    zh:ember:uart:ash: Received ERROR from adapter while connecting, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.

So I read somewhere to add this to my config. yaml:

ota:
  image_block_response_delay: 200
  default_maximum_data_size: 15

That helped for a little while, but after a few days I had the same errors again. People advised to change the WiFi channel because it could be interference. So I did that and it worked, Zigbee2MQTT doesn’t fail anymore and I don’t get errors anymore, so far. But is it normal that Zigbee2MQTT restarts every hour or so?

[2025-02-26 11:43:00] info: 	zh:ember: [NCP COUNTERS] 2661,478,173,132,20,0,0,0,58,73,0,0,62,7,0,4,0,0,0,0,0,11,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[2025-02-26 11:43:00] info: 	zh:ember: [ASH COUNTERS] 2265,404,108,295,0,0,0,0,5587,295,294,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[2025-02-26 11:43:00] info: 	zh:ember: [ASH COUNTERS] 2265,404,108,295,0,0,0,0,5587,295,294,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[11:49:33] INFO: Preparing to start...
[11:49:34] INFO: Socat not enabled
[11:49:35] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-02-26 11:49:53] info: 	z2m: Logging to console, file (filename: log.log)
[2025-02-26 11:49:53] info: 	z2m: Starting Zigbee2MQTT version 2.1.1 (commit #unknown)
[2025-02-26 11:49:53] info: 	z2m: Starting zigbee-herdsman (3.2.5)
[2025-02-26 11:49:54] info: 	zh:ember: Using default stack config.
[2025-02-26 11:49:54] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-02-26 11:49:54] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-02-26 11:49:54] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-02-26 11:49:54] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-02-26 11:49:54] info: 	zh:ember:uart:ash: Serial port opened
[2025-02-26 11:49:54] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2025-02-26 11:49:55] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2025-02-26 11:49:55] info: 	zh:ember:uart:ash: ======== ASH started ========
[2025-02-26 11:49:55] info: 	zh:ember:ezsp: ======== EZSP started ========
[2025-02-26 11:49:55] info: 	zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2025-02-26 11:49:55] info: 	zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.4 [GA]","build":0,"major":7,"minor":4,"patch":4,"special":0,"type":170}
[2025-02-26 11:49:55] info: 	zh:ember: [STACK STATUS] Network up.
[2025-02-26 11:49:55] info: 	zh:ember: [INIT TC] Adapter network matches config.
[2025-02-26 11:49:55] info: 	zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2025-02-26 11:49:55] info: 	z2m: zigbee-herdsman started (resumed)
[2025-02-26 11:49:55] info: 	z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":4,"revision":"7.4.4 [GA]","special":0,"type":170},"type":"EmberZNet"}'

My config file looks like this now:

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://core-mosquitto:1883
  user: ***
  password: ***
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240124210837-if00
  adapter: ember
advanced:
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false
ota:
  image_block_response_delay: 200
  default_maximum_data_size: 15

Are you using an extension code cord between the computer and the dongle? If not, try one.

I have the Sonoff dongle in a Rpi 3. What is an extension code? Do I need to add more code to my zigbee config file?

He meant a cable, not code.

1 Like

Duh yeah sorry :woozy_face:

Ah okay!! Haha! I was wondering what does he mean by that? I will look for one and try that, thanks!

So you guys think it is still interference?

I don’t know specifically what those “ASH COUNTERS” messages mean, I can’t find anything about them on the z2m issue tracker on Github, although I did find some other possible causes, like the dongle firmware (some people reported issues that were solved when they updated to 8.0.2) and Linux kernel version (6.7 seems to cause problems on RPi3, downgrading to an older kernel solved those).

Ok, I will look into that, thanks. But first I’m going to try the extension cord.