Not Configured Dusun DSGW-210 Sub Model - B13

Technical Support
1

We got a new gateway and default installed with Debian OS. Now we want to up and running zigbee2mqtt whose docker file is already available in it. When we are running it to install then adapter ezsp was giving problem , after explored we got to know that we have to upgrade adapter to “ember” and post updation when we run docker configurationt then we get the below logs

zigbee2mqtt | [2024-06-14 15:10:35] info: z2m: Logging to console, file (filename: log.log)

zigbee2mqtt | [2024-06-14 15:10:35] info: z2m: Starting Zigbee2MQTT version 1.38.0 (commit #fe048e6)

zigbee2mqtt | [2024-06-14 15:10:35] info: z2m: Starting zigbee-herdsman (0.49.2)

zigbee2mqtt | [2024-06-14 15:10:36] info: zh:ember: Using default stack config.

zigbee2mqtt | [2024-06-14 15:10:36] info: zh:ember: ======== Ember Adapter Starting ========

zigbee2mqtt | [2024-06-14 15:10:36] info: zh:ember:ezsp: ======== EZSP starting ========

zigbee2mqtt | [2024-06-14 15:10:36] info: zh:ember:uart:ash: ======== ASH NCP reset ========

zigbee2mqtt | [2024-06-14 15:10:37] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.

zigbee2mqtt | [2024-06-14 15:10:37] info: zh:ember:uart:ash: Serial port opened

zigbee2mqtt | [2024-06-14 15:10:37] info: zh:ember:uart:ash: ======== ASH starting ========

zigbee2mqtt | [2024-06-14 15:10:39] info: zh:ember:uart:ash: ======== ASH NCP reset ========

zigbee2mqtt | [2024-06-14 15:10:39] info: zh:ember:uart:ash: ======== ASH starting ========

zigbee2mqtt | [2024-06-14 15:10:42] info: zh:ember:uart:ash: ======== ASH NCP reset ========

zigbee2mqtt | [2024-06-14 15:10:42] info: zh:ember:uart:ash: ======== ASH starting ========

zigbee2mqtt | [2024-06-14 15:10:44] info: zh:ember:uart:ash: ======== ASH NCP reset ========

zigbee2mqtt | [2024-06-14 15:10:44] info: zh:ember:uart:ash: ======== ASH starting ========

zigbee2mqtt | [2024-06-14 15:10:45] info: zh:ember:uart:ash: ======== ASH connected ========

zigbee2mqtt | [2024-06-14 15:10:45] info: zh:ember:uart:ash: ======== ASH started ========

zigbee2mqtt | [2024-06-14 15:10:45] info: zh:ember:ezsp: ======== EZSP started ========

zigbee2mqtt | [2024-06-14 15:10:45] error: z2m: Error while starting zigbee-herdsman

zigbee2mqtt | [2024-06-14 15:10:45] error: z2m: Failed to start zigbee

zigbee2mqtt | [2024-06-14 15:10:45] error: z2m: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions

zigbee2mqtt | [2024-06-14 15:10:45] error: z2m: Exiting…

zigbee2mqtt | [2024-06-14 15:10:46] error: z2m: Error: NCP EZSP protocol version of 8 does not match Host version 13

zigbee2mqtt | at EmberAdapter.emberVersion (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1674:19)

zigbee2mqtt | at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:854:9)

zigbee2mqtt | at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2683:24)

zigbee2mqtt | at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:127:29)

zigbee2mqtt | at Zigbee.start (/app/lib/zigbee.ts:62:27)

zigbee2mqtt | at Controller.start (/app/lib/controller.ts:109:27)

zigbee2mqtt | at start (/app/index.js:107:5)

Please suggest what we should to make it up and running.

2

Hi!

Unless you had some serious issues with the ezsp adapter I would NOT go through the trouble of updating the adapter.

this is from the the issue on github regarding the deprecated driver:

Note that nothing will change for users that are currently using serial.adapter ezsp , this will stay as is.

How did you go about updating the driver for the zigbee controller?

3

i have connected with dusun support and they suggest me to upgarde the firmware of the gateway and after that ezsp adapter only started working.

latest firmware which suggested was : 1.3.2

4

I see. I am currently looking into doing an update onto ember on it but I am not having any luck yet. You say that after a firmware update the ezsp started working, but I thought you had issues with ember?