Good evening!
I’m coming home from work after a rough day, and I find a number of home automation features that no longer work at my place… Bad day!
So, after checking, my Zigbee is no longer working properly, and it’s crazy how my home automation looks like nothing without Zigbee It had been working perfectly for several weeks, the problem appeared today… I restarted Gladys, no improvement.
Specifically, the dashboard/integration/device/zigbee2mqtt/setup page on Gladys seems to say everything is fine, but I can’t access the Zigbee page on port 8080. And a quick look in the logs (on my Raspberry Pi in /var/lib/gladysassistant/zigbee2mqtt/z2m/log/) shows this:
info 2023-12-06 21:29:42: Logging to console and directory: '/app/data/log/2023-12-06.21-29-42' filename: log.txt
info 2023-12-06 21:29:42: Starting Zigbee2MQTT version 1.34.0 (commit #aae7312)
info 2023-12-06 21:29:42: Starting zigbee-herdsman (0.25.0)
error 2023-12-06 21:30:03: Error while starting zigbee-herdsman
error 2023-12-06 21:30:03: Failed to start zigbee
error 2023-12-06 21:30:03: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
error 2023-12-06 21:30:03: Exiting...
error 2023-12-06 21:30:04: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:60:27)
at Controller.start (/app/lib/controller.ts:101:27)
at start (/app/index.js:107:5)
Any idea what’s happening to my system? And how to fix it?
you should give more details about your setup… Pi, mini PC, disk type etc
You need to pay attention to one point we often neglect, the increase in space taken up by apps over time… which fills the disk, and when there’s no more space and the system needs to save files and can’t, it sometimes crashes without warning, so check that!
Thanks in any case for these initial details. And to answer you:
@Tlse-vins I hadn’t thought to look for the error text on the forum, so indeed I’m not the first… But there is quite a wide variety of possible reasons!!
@cicoub13 I just tried restarting the container, no improvement. If I have to buy a new dongle, which one would be the most reliable based on your experience?
@cce66 my setup: Raspberry Pi 4B, 120 GB SSD drive used at less than 25%, Zigbee CC2531 dongle
Ah, that might be a lead, I’ll have to look more closely tomorrow (because right now I have to go to bed actually ) : I don’t remember what the wattage of the power supply unit was, it’s in a place that’s not very accessible… but to the touch it’s abnormally hot…
From experience I know that CC2531-based dongles are unreliable; they’re even on the list of things not to recommend in the z2m docs
Maybe it’s a good opportunity to properly diagnose the source of your problem (power supply / other) and to take the plunge to a dongle based on CC2652 or CC1352
Not that DSM 7 doesn’t support USB, but I am indeed on DSM 7: I install the drivers manually, and on restarting the NAS the port (again) changed its name (USB1 vs USB2).
This may be because I added a new USB device.
However, I don’t see how to prevent this problem on Synology…
Well indeed, I had never noticed that. And that may also explain why I’ve felt from the start of my use of Zigbee that the tech wasn’t very reliable (sensor reports that sometimes get lost, commands that don’t always go through, …). Right, Sonoff dongle ordered, it won’t hurt.
And I’ll also look into making the power supply more reliable.
In any case, the new Sonoff dongle lets me access the page [IP]:8080 again, that’s a good sign.
Except that I no longer see any Zigbee devices. That’s logical since it’s not the same dongle, but that means I have to reconnect them all (around thirty or so…)
Unless there’s a way to retrieve the config from the previous dongle and import it into the new one? I’m asking, but I don’t really believe it…
And will it be enough for me to give the Zigbee devices the same names as before on the [IP]:8080 page (I had renamed them there to recognize them better…) so that in Gladys they are reassociated identically? Or will I have to redo all Zigbee device detections in Gladys, and then readjust all the scenes and dashboard widgets that use them?
I’m a bit dreading the answer…
If you have a bit of time to advise me, I might save a lot of time on my end. Thanks in advance
I do have Gladys+. But actually, I didn’t even need it, so I ended up scaring myself.
In fact, all I have to do is go back to a Zigbee device and reset it. It then reconnects to the new dongle, finds the ‹ friendly name › I had given it, and Gladys finds it too and the link is restored without any problem.
Right, now all that’s left is to go around all the devices