Flashed 20250321 firmwre on ZBdongle-P ->z2m dead

[woodrook]

Hi everybody, this morning I flashed the 20250321 firmware on my Sono Zbdongle-P using Docker.

Everything ok but zigbee2mqtt doesn't start anymore

Trying to flash back 20230507 firmware, flashing process went fine but zigbee2mqtt still dead

I've been going crazy for hours, trying to change channel, reflash firmware, plug unplug, reboot, shutdown the whole house and (obviously) looked for an answer on the web
Now i need help

My Configuration:
Home Assistant Core 2025.09 on Docker on Synology
mosquito latest stable on docker on synology
zigbee2mqtt latest stable on docker on synology - device:zstack channel:26
Coordinator: Sono ZBDongle-P with a 150 cm usb cable

Here is the container LOG
zigbee2mqtt
2025/09/10 13:58:22 stdout [2025-09-10 13:58:22] �[31merror�[39m: z2m: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
2025/09/10 13:58:22 stdout [2025-09-10 13:58:22] �[31merror�[39m: z2m: Not connected to MQTT server!
2025/09/10 13:58:14 stdout Starting Zigbee2MQTT without watchdog.
2025/09/10 13:58:14 stderr To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2025/09/10 13:58:14 stderr Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2025/09/10 13:58:14 stderr [WARN tini (7)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2025/09/10 13:58:14 stdout Using '/app/data' as data directory
2025/09/10 13:58:06 stdout at start (/app/index.js:149:5)
2025/09/10 13:58:06 stdout at Controller.start (/app/lib/controller.ts:101:13)
2025/09/10 13:58:06 stdout at Zigbee.start (/app/lib/zigbee.ts:67:27)
2025/09/10 13:58:06 stdout at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
2025/09/10 13:58:06 stdout at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:151:28)
2025/09/10 13:58:06 stdout at Znp.request (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:249:27)
2025/09/10 13:58:06 stdout at Queue.execute (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
2025/09/10 13:58:06 stdout at /app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:256:45
2025/09/10 13:58:06 stdout at Object.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/waitress.ts:68:23)
2025/09/10 13:58:06 stdout [2025-09-10 13:58:06] �[31merror�[39m: z2m: Error: SRSP - SYS - stackTune after 6000ms
2025/09/10 13:58:06 stdout [2025-09-10 13:58:06] �[31merror�[39m: z2m: Exiting...
2025/09/10 13:58:06 stdout [2025-09-10 13:58:06] �[31merror�[39m: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
2025/09/10 13:58:06 stdout [2025-09-10 13:58:06] �[31merror�[39m: z2m: Failed to start zigbee-herdsman
2025/09/10 13:58:06 stdout [2025-09-10 13:58:06] �[31merror�[39m: z2m: Error while starting zigbee-herdsman
2025/09/10 13:57:58 stdout Starting Zigbee2MQTT without watchdog.
2025/09/10 13:57:58 stderr To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2025/09/10 13:57:58 stderr Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2025/09/10 13:57:58 stderr [WARN tini (6)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2025/09/10 13:57:58 stdout Using '/app/data' as data directory

Here the z2m configuration file:
configuration.yaml

Thanks!

UPDATE: started a brand new HAOS installation on a virtual machine. Sonof coordinator is definetelly recognized and configured (throug ZHA)
I don't really know what's appened to my zigbee2mqtt

[woodrook]

Solved. Set zigbee channel to 11 in configuration.yaml, rebootees the nas and re-plugged the usb stick.

Everything seems to work (let's see how long)

Thanks, Gianluca