Error while starting zigbee-herdsman

Since I replaced my old coordinator with an CC2652 from https://www.tindie.com/products/slaesh/cc2652-zigbee-coordinator-or-openthread-router I often have issues like this: Error while starting zigbee-herdsman Zigbee2MQTT:error 2021-01-05 18:36:14: Failed to start zigbee Zigbee2MQTT:error 2021-01-05 18:36:14: Exiting... Zigbee2MQTT:error 2021-01-05 18:36:14: Error: Coordinator failed to start, probably the panID is already in use, try a different panID or channel at /zigbee2mqtt-1.17.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/startZnp.js:172:23 at Generator.throw (<anonymous>) at rejected (/zigbee2mqtt-1.17.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/startZnp.js:25:65) npm ERR! code ELIFECYCLE

Only if I change the PANID I got again access to the coordinator but after that the whole zigbee network is lost. Is there another solution for this?

[slaesh]

@JvD12 could you please check this script? https://github.com/slaesh/cc2652-stick/tree/master/coordinator-test

the HW is tested two times:

• automated HW test
• manually by doing a “range test”

we changed the manufacturer multiple times, I will check you EUID to see where it was manufactured. Could you text me on telegram? https://t.me/slaesh We can send you another device, to check if it’s an HW related problem.

Another thing, we could check this debug-fw: https://slae.sh/projects/cc2652/#from-me

the LED’s will let us know the current state of the MCU. maybe another process is interrupting us…

[parkwart]

ran into this issue after I added network_key to my configuration (just got my slaesh stick yesterday and noticed after reading the docs that I was using the default key for zigbee2mqtt).

after hours of flashing, docker-compose up and downs I somehow fixed it by:

1. docker-compose down
2. deleted the entire data volume
3. flashed the stick using JelmerT cc2538-bsl, used fw CC2652RB_coordinator_20210708.zip on raspberry pi
4. physically cut off power from my raspberry pi
5. removed all light bulbs from power source (aka zigbee routers)
6. factory reset all motion sensors (aka zigbee end-devices)
7. made a coffee and drank it
8. plugged in raspberry again
9. docker compose up

finally zigbee2mqtt started and it works again 🥳. i was able to set a new network_key and was not forced to switch to another pan_id or something like that.

after that I repaired all devices. first the routers (bulbs), then the end-devices (motion sensors). I paired the end-devices at their designated location to ensure that they are connected to the next best router.