Yes, I would change that to your mqtt host IP

I tried 2 options today

When I set:

 

1. - more errors

mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.10.103

Starting Zigbee2MQTT without watchdog.
[2025-03-31 14:13:53] info:     z2m: Logging to console, file (filename: log.log)
[2025-03-31 14:13:53] info:     z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06)
[2025-03-31 14:13:53] info:     z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-31 14:13:53] info:     zh:ember: Using default stack config.
[2025-03-31 14:13:53] info:     zh:ember: ======== Ember Adapter Starting ========
[2025-03-31 14:13:53] info:     zh:ember:ezsp: ======== EZSP starting ========
[2025-03-31 14:13:53] info:     zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-31 14:13:53] info:     zh:ember:uart:ash: Socket ready
[2025-03-31 14:13:53] info:     zh:ember:uart:ash: ======== ASH starting ========
[2025-03-31 14:13:55] info:     zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-31 14:13:55] info:     zh:ember:uart:ash: ======== ASH starting ========
[2025-03-31 14:13:55] info:     zh:ember:uart:ash: ======== ASH connected ========
[2025-03-31 14:13:55] info:     zh:ember:uart:ash: ======== ASH started ========
[2025-03-31 14:13:55] info:     zh:ember:ezsp: ======== EZSP started ========
[2025-03-31 14:13:57] warning:  zh:ember:uart:ash: Frame(s) in progress cancelled in [1ac1020b0a527e]
[2025-03-31 14:13:57] error:    zh:ember:uart:ash: Received unexpected reset from adapter, with reason=RESET_SOFTWARE.
[2025-03-31 14:13:57] error:    zh:ember:uart:ash: ASH disconnected: ASH_ERROR_NCP_RESET | Adapter status: ASH_NCP_FATAL_ERROR
[2025-03-31 14:13:57] error:    zh:ember:uart:ash: Error while parsing received frame, status=HOST_FATAL_ERROR.
[2025-03-31 14:13:57] error:    zh:ember: Adapter fatal error: HOST_FATAL_ERROR
[2025-03-31 14:14:10] error:    zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=0:"VERSION" Seq=0 Len=0].
[2025-03-31 14:14:10] error:    z2m: Error while starting zigbee-herdsman
[2025-03-31 14:14:10] error:    z2m: Failed to start zigbee-herdsman
[2025-03-31 14:14:10] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-03-31 14:14:10] error:    z2m: Exiting...
[2025-03-31 14:14:10] error:    z2m: Error: ASH_ERROR_TIMEOUTS
    at Ezsp.ezspVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/ezsp/ezsp.ts:1426:19)
    at EmberAdapter.emberVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1392:63)
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:674:9)
    at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1536:24)
    at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:142:13)
    at start (/app/index.js:161:5)

** Press ANY KEY to close this window ** 

 

2. Only 1 error

mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.10.103:6638

 

Starting Zigbee2MQTT without watchdog.
[2025-03-31 14:17:03] info:     z2m: Logging to console, file (filename: log.log)
[2025-03-31 14:17:03] info:     z2m: Starting Zigbee2MQTT version 2.1.3 (commit #ba337bd329aeb4ca17735c0cf09b31293c8cff06)
[2025-03-31 14:17:03] info:     z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-31 14:17:03] info:     zh:ember: Using default stack config.
[2025-03-31 14:17:03] info:     zh:ember: ======== Ember Adapter Starting ========
[2025-03-31 14:17:03] info:     zh:ember:ezsp: ======== EZSP starting ========
[2025-03-31 14:17:03] info:     zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-03-31 14:17:03] info:     zh:ember:uart:ash: Socket ready
[2025-03-31 14:17:03] info:     zh:ember:uart:ash: ======== ASH starting ========
[2025-03-31 14:17:05] info:     zh:ember:uart:ash: ======== ASH connected ========
[2025-03-31 14:17:05] info:     zh:ember:uart:ash: ======== ASH started ========
[2025-03-31 14:17:05] info:     zh:ember:ezsp: ======== EZSP started ========
[2025-03-31 14:17:05] info:     zh:ember: Adapter EZSP protocol version (14) lower than Host. Switched.
[2025-03-31 14:17:05] 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-03-31 14:17:05] info:     zh:ember: [STACK STATUS] Network up.
[2025-03-31 14:17:05] info:     zh:ember: [INIT TC] Adapter network matches config.
[2025-03-31 14:17:05] info:     zh:ember: [CONCENTRATOR] Started source route discovery. 1246ms until next broadcast.
[2025-03-31 14:17:05] info:     z2m: zigbee-herdsman started (resumed)
[2025-03-31 14:17:05] info:     z2m: Coordinator firmware version: '{"meta":{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2025-03-31 14:17:05] info:     z2m: Currently 0 devices are joined.
[2025-03-31 14:17:05] info:     z2m: Connecting to MQTT server at mqtt://192.168.10.103:6638
[2025-03-31 14:17:07] error:    z2m: MQTT failed to connect, exiting... (read ECONNRESET)
[2025-03-31 14:17:07] info:     z2m: Stopping zigbee-herdsman...
[2025-03-31 14:17:07] info:     zh:controller: Wrote coordinator backup to '/app/data/coordinator_backup.json'
[2025-03-31 14:17:07] info:     zh:ember:uart:ash: ASH COUNTERS since last clear:
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Total frames: RX=47, TX=92
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Cancelled   : RX=0, TX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   DATA frames : RX=46, TX=44
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   DATA bytes  : RX=638, TX=481
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Retry frames: RX=0, TX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   ACK frames  : RX=0, TX=47
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   NAK frames  : RX=0, TX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   nRdy frames : RX=0, TX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   CRC errors      : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Comm errors     : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Length < minimum: RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Length > maximum: RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Bad controls    : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Bad lengths     : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Bad ACK numbers : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Out of buffers  : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Retry dupes     : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   Out of sequence : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash:   ACK timeouts    : RX=0
[2025-03-31 14:17:07] info:     zh:ember:uart:ash: ======== ASH stopped ========
[2025-03-31 14:17:07] info:     zh:ember:ezsp: ======== EZSP stopped ========
[2025-03-31 14:17:07] info:     zh:ember: ======== Ember Adapter Stopped ========
[2025-03-31 14:17:07] info:     z2m: Stopped zigbee-herdsman

** Press ANY KEY to close this window ** 

 

configuration.yaml

version: 4
homeassistant:
  enabled: false
frontend:
  enabled: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.10.103:6638
serial:
# Location of SLZB-06Mg24
  port: tcp://192.168.10.103:6638
  baudrate: 115200
  adapter: ember
# Disable green led?
  disable_led: false
# Set output power to max 20  
advanced:
  transmit_power: 20
  network_key:
    - 119
    - 193
    - 155
    - 54
    - 113
    - 239
    - 241
    - 185
    - 191
    - 133
    - 219
    - 138
    - 118
    - 114
    - 49
    - 29
  pan_id: 44735
  ext_pan_id:
    - 0
    - 105
    - 120
    - 49
    - 88
    - 159
    - 172
    - 36

 

Ahh got it working, there needs to be the MQTT server which gets the data, i thought it should be the Zigbee Adapter

Then also user / pass had to be added.

 

version: 4
homeassistant:
  enabled: false
frontend:
  enabled: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.10.102:1883
  user: XXX
  password: XXX
serial:
# Location of SLZB-06Mg24
  port: tcp://192.168.10.103:6638
  baudrate: 115200
  adapter: ember
# Disable green led?
  disable_led: false
# Set output power to max 20  
advanced:
  transmit_power: 20
  network_key:
    - 119
    - 193
    - 155
    - 54
    - 113
    - 239
    - 241
    - 185
    - 191
    - 133
    - 219
    - 138
    - 118
    - 114
    - 49
    - 29
  pan_id: 44735
  ext_pan_id:
    - 0
    - 105
    - 120
    - 49
    - 88
    - 159
    - 172
    - 36

 

Glad you got it.  And do make sure your MQTT server is setup to allow for a proper retains database too.  

Today I wanted to fire up my tasmoadmin docker and noticed that it does not work anymore.

Unraid 7.1.4

Docker Protocol

s6-rc: info: service nginx: starting

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service nginx successfully started

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service init-nginx: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service init-nginx successfully started

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-tasmoadmin: starting

s6-rc: info: service init-tasmoadmin successfully started

s6-rc: info: service php-fpm: starting

s6-rc: info: service php-fpm successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

Symlinking /etc/nginx.conf from persistent storage location...

Symlinking /data/tasmoadmin directory to persistent storage location...

Docker env does not exist, doing that now...

WebUI Error message is a white page with : "File not found".

Deleting the container and re-downloading it, or giving it a new port did not work either.

Any idea?

I don't really know where to post this, so I'm casting a wide net on a couple of different sites if you see it again.

I'm trying to get mosquitto & Z2M up and running so I can get HA fully functional with a zigbee network. I bought an SLZB-06M as my coordinator. I've attached what I assume is sufficient log files (all that really populates after attempting to launch Z2M). The big error I guess I'm seeing is an ETIMEDOUT error to the coordinator. I can access it via IP on both my laptop and PC, no issue. It's plugged directly into my switch as are my PC and Unraid server. Can post my mosquitto/Z2M config files if anyone thinks that would be helpful.

Would appreciate any/all advice.

z2m log.pdf

Edited September 26, 2025Sep 26 by rxryanm

On 9/25/2025 at 6:43 PM, rxryanm said:

I don't really know where to post this, so I'm casting a wide net on a couple of different sites if you see it again.

I'm trying to get mosquitto & Z2M up and running so I can get HA fully functional with a zigbee network. I bought an SLZB-06M as my coordinator. I've attached what I assume is sufficient log files (all that really populates after attempting to launch Z2M). The big error I guess I'm seeing is an ETIMEDOUT error to the coordinator. I can access it via IP on both my laptop and PC, no issue. It's plugged directly into my switch as are my PC and Unraid server. Can post my mosquitto/Z2M config files if anyone thinks that would be helpful.

Would appreciate any/all advice.

z2m log.pdf

Try the latest firmware on your EFR chipset model? of both Zigbee coordinator and core?

On 9/28/2025 at 2:28 PM, digiblur said:

Try the latest firmware on your EFR chipset model? of both Zigbee coordinator and core?

Core and coordinator are both now latest firmware, log looks the same as last time when I try to launch unfortunately. Same ETIMEDOUT issue when launching Z2M.

Just did an update on the zwaveJSUI docker and zwaveJSUI won't start anymore. Anyone seen this before?

node:internal/modules/esm/resolve:283

throw new ERR_MODULE_NOT_FOUND(

^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/usr/src/app/server/lib/jsonStore' imported from /usr/src/app/server/bin/www.js

at finalizeResolution (node:internal/modules/esm/resolve:283:11)

at moduleResolve (node:internal/modules/esm/resolve:952:10)

at defaultResolve (node:internal/modules/esm/resolve:1188:11)

at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)

at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)

at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)

at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)

at ModuleJob._link (node:internal/modules/esm/module_job:130:49) {

code: 'ERR_MODULE_NOT_FOUND',

url: 'file:///usr/src/app/server/lib/jsonStore'

}

Node.js v20.19.0

Press ANY KEY to close this window

Edited October 6, 2025Oct 6 by PhAzE

1 hour ago, PhAzE said:

Just did an update on the zwaveJSUI docker and zwaveJSUI won't start anymore. Anyone seen this before?

node:internal/modules/esm/resolve:283

throw new ERR_MODULE_NOT_FOUND(

^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/usr/src/app/server/lib/jsonStore' imported from /usr/src/app/server/bin/www.js

at finalizeResolution (node:internal/modules/esm/resolve:283:11)

at moduleResolve (node:internal/modules/esm/resolve:952:10)

at defaultResolve (node:internal/modules/esm/resolve:1188:11)

at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)

at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)

at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)

at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)

at ModuleJob._link (node:internal/modules/esm/module_job:130:49) {

code: 'ERR_MODULE_NOT_FOUND',

url: 'file:///usr/src/app/server/lib/jsonStore'

}

Node.js v20.19.0

Press ANY KEY to close this window

Came here to post the same issue

3 hours ago, shawnm said:

Came here to post the same issue

Try rolling the container back to last stable release?

I'm not sure what is happening, but I'm getting the same ERR Module not found. I restored the past 4 backups without success. I'm not sure what happened that backups don't work.

3 hours ago, digiblur said:

I tried going back 4 backups without luck. Not sure what happened to make this happen accros backups.

Try rolling the container back to last stable release?

If you are having issues with updating to the latest zwave docker, do this to fix it. Edit the container and use this as the repository: zwavejs/zwave-js-ui:11.3.1. It will pull the last version. The devs have identified the issue and are working on a fix.

Edited October 7, 2025Oct 7 by Mlatx

This is a good reminder to always take note of the current version being used BEFORE updating. And to make sure to turn off auto-updating if you have a plugin installed that does this.

Version 11.4.1 fixes the issue and you can include that in the repository line.

If you want to "fix" the issue and leave your docker config correctly set up for next time, you'll need to delete problem image first, as if you try to pull "latest" it'll just re-use teh cached version.

I just did it the quick and dirty way, by opening a terminal window and then:

docker images to see all images

and

docker rmi imageID to remove the one tagged "latest"

Then you can edit and deploy the container without ":version_string" and it'll download the current latest version - 11.4.1 today

Edited October 7, 2025Oct 7 by Espressomatic

Just got a forum email and was going to come in to post about the fix, but I see that many beat me to it...

20 minutes ago, Espressomatic said:

I just did it the quick and dirty way

Thanks for that! Just did that and worked perfectly here. As a note, I also removed the 11.3.1 build that I'd pulled by adding the tag. Figure there's no reason to have that sitting around for the next decade...

Chiming in to share I had the same issue as above, ERROR MODULE NOT FOUND. Reverting to 11.3.1 build with the added tag to the repository line worked for me. I did try to go to 11.4.0 and that did not work either.

Has anyone else seen this particular container cause the disappearance of an Unraid custom network (br0)?

I was passing a USB device by ID and seemingly that ID changed today after plugging in another USB device (unrelated). That doesn't seem right, but when I edited the container and put in an updated USB ID it started working.

But the network type was set to NONE and my (default) custom network br0 was gone. Turning OFF and then ON the docker service brought it back, but then I also had to re-edit the container to set it back to custom as well as its static IP.

This container has given me more trouble in the past few months than I've had from all other containers on 4 systems combined over 5 years.

I'll be deleting it this week and going to change over to docker-compose within an LXC. That way I don't rely on anyone else to maintain a container either.

Anyone else having problems with the latest Z2M?

2.6.3 cant start herdsman and gives an unspecified error (just says "cannot set"), and works fine after downgrading to 2.6.2.

On 11/29/2025 at 5:32 AM, NetLeiwand said:

Anyone else having problems with the latest Z2M?

2.6.3 cant start herdsman and gives an unspecified error (just says "cannot set"), and works fine after downgrading to 2.6.2.

I had problems after upgrading mine to 2.7.0, which was giving me the following error:

[2025-12-02 00:17:16] error:    z2m: Error while starting zigbee-herdsman
[2025-12-02 00:17:16] error:    z2m: Failed to start zigbee-herdsman
[2025-12-02 00:17:16] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-12-02 00:17:16] error:    z2m: Exiting...
[2025-12-02 00:17:17] error:    z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:115:27)
    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)
    at start (/app/index.js:149:5)

I tried a ton of things, including downgrading to releases 2.6.3, 2.6.2, and 2.6.1 - deleting the container and image and rebuilding it - none of this helped though, no luck.

I eventually got it back up and running, not sure if this is what did it, but the last things I did were reorder some of the configuration.yaml entries, used a different TCP port, and lastly, re-flashed my SLZB-MR3 zigbee-coordinator radio with the same firmware version, and restarted zigbee on it.

My linter indicated nothing wrong with the configuration.yaml file and I hadn't changed it... so I don't think that was it, I think it was just gremlins in my SLZB-MR3?

On 7/30/2025 at 3:08 AM, jluerken said:

Today I wanted to fire up my tasmoadmin docker and noticed that it does not work anymore.

Unraid 7.1.4

Docker Protocol

s6-rc: info: service nginx: starting

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service nginx successfully started

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service init-nginx: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service init-nginx successfully started

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-tasmoadmin: starting

s6-rc: info: service init-tasmoadmin successfully started

s6-rc: info: service php-fpm: starting

s6-rc: info: service php-fpm successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

Symlinking /etc/nginx.conf from persistent storage location...

Symlinking /data/tasmoadmin directory to persistent storage location...

Docker env does not exist, doing that now...

WebUI Error message is a white page with : "File not found".

Deleting the container and re-downloading it, or giving it a new port did not work either.

Any idea?

Delete the nginx folder located in your tasmoadmin appdata share.

I can't make openwakeword working, container is started but seems like model is not downloaded, don't see any signs of this, can you please advise?

On 7/30/2025 at 4:08 AM, jluerken said:

Today I wanted to fire up my tasmoadmin docker and noticed that it does not work anymore.

Unraid 7.1.4

Docker Protocol

s6-rc: info: service nginx: starting

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service nginx successfully started

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service init-nginx: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service init-nginx successfully started

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init-tasmoadmin: starting

s6-rc: info: service init-tasmoadmin successfully started

s6-rc: info: service php-fpm: starting

s6-rc: info: service php-fpm successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

Symlinking /etc/nginx.conf from persistent storage location...

Symlinking /data/tasmoadmin directory to persistent storage location...

Docker env does not exist, doing that now...

WebUI Error message is a white page with : "File not found".

Deleting the container and re-downloading it, or giving it a new port did not work either.

Any idea?

I am having the same issue. Did you ever figure this out?