Complex zigbee2mqtt network with three coordinators and a lot of issues

Configuration Zigbee
1

With community assistance, I have achieved to install zigbee2mqtt in two raspberries pi, each one with its own coordinator cc2531. Reasons and procedure here.

On top of these two raspberries, I’m running a thin client x64 with HAOS and the MQTT in it, its coordinator is a sonoff cc2652p.

Each coordinator is running in different channel, 11, 15, 20 respectively. My zigbee network is like this picture

ZIGBEE NETWORK
ZIGBEE NETWORK960×556 10.5 KB

while I was doing trials, I had achieved to have all of them in operation after channel adjustment, deletion of json files etc (readings from this forum).

As started to move raspberries to their operational position, deleting devices from the base unit, pairing to new coordinators, I had a lot of crashes. So far I have no achieved to have all of them (zigbee2mqtt) in flawless operation.

Im diving in panID an ext panID issue and I have no idea how to solve it. From time to time I have achieved to start up one by one the zigbee2mqtt and changing the panid’s but its not something stable. In a few minutes, my setup is collapsing and remaining only one in run.
Last night, it was down the main one and one raspberry, today are off both raspberries.

I have no idea how to come out of this rabbit hole and how to have a stable system.
As I have no idea what other info I should post here before seeking assistance, please have a look in this weird case and propose something.

My zigbee devices are magnet sensors, light sensor, flood sensors, removable wall sockets, motion detectors, switches and temp sensors. Mainly xiaomi -aqara and sonoff.

Thanks!

2

A great starting point would be to move away from that coordinator to something that’s not junk. Something CC2652 based.

The CC253x coordinators are known to lock up, crash, and otherwise just misbehave.

1 Like
3

In long term, yes I’ll change all of the coordinators! Even for sonoff cc2652p I’m not reading good comments…but consider the case as an experiment with stuff that was available in my drawers.

4

The problem is, you can’t tell whether your issues are because of those, or because of other things (like not having them on USB extension cables, WiFi interference, etc).

Sure, it’s convenient to use them, but they’re known to cause problems, and you’re just hurting yourself.

2 Likes
5

Tried “npm start” after deleting the existing network key and the and this is what I got on the screen.

root@DietPi0:/opt/zigbee2mqtt# npm start

> [email protected] start /opt/zigbee2mqtt
> node index.js

(node:5021) UnhandledPromiseRejectionWarning: YAMLException: bad indentation of a mapping entry (16:13)

 13 |   port: /dev/ttyACM0
 14 | advanced:
 15 |   network_key:GENERATE
 16 |   log_syslog:
------------------^
 17 |     app_name: Zigbee2MQTT
 18 |     eol: /n
    at generateError (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:183:10)
    at throwError (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:187:9)
    at readBlockMapping (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:1182:7)
    at composeNode (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:1441:12)
    at readDocument (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:1625:3)
    at loadDocuments (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:1688:5)
    at Object.load (/opt/zigbee2mqtt/node_modules/js-yaml/lib/loader.js:1714:19)
    at Object.read (/opt/zigbee2mqtt/lib/util/yaml.ts:7:21)
    at read (/opt/zigbee2mqtt/lib/util/settings.ts:328:20)
    at getInternalSettings (/opt/zigbee2mqtt/lib/util/settings.ts:433:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5021) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5021) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
6

Looks like you have a YAML formatting error

7

Im trying this

After a good house keeping in yaml file, I did this sudo systemctl stop zigbee2mqtt and now I’m watching the output. It seems that is effective. I’m watching it and reverting