Stadicus

Thanks! As written above, falling back on `20221226` solved some of the issues. I will continue to provide feedback regarding the firmware in the linked issue. --- But even with...

Sure thing. I'm not sure how to update to a specific, non-latest version, however. Any hints?

> Home Assistant unfortunately doesn't allow switching to specific version Dang. Let me know if I can do some Docker magic or whatnot. I'm not that bad in figuring stuff...

The network was running fine with v1.30.3 the whole day, with herdsman logging enabled. I got a few hours of logs from Docker (zipped, as it's 90+ MB) and couldn't...

Quick update: early today around 6am my network running with coordinator firmware `20221226` and Z2M version 1.30.3 became unresponsive, with many timeouts (error `SRSP - AF - dataRequest after 6000ms`,...

I tried a Sonoff coordinator before, with shorter and very long USB cables. Due to the placement of Home Assistant in a 19" rack, the position in my home was...

Your instructions seem straight-forward, but I get the following error: ```sh /bin/sh: npm: not found ``` ----- I checked the following: * Entering the Docker container through SSH locally as...

That command worked, but without any obvious improvement for Z2M: * I still get the `0x02: INVALID_PARAM` error (see log [z2m-logs-v1.33.2-20231109.txt](https://github.com/Koenkk/zigbee2mqtt/files/13312736/z2m-logs-v1.33.2-20231109.txt)) * The log now shows `Starting zigbee-herdsman (0.14.103)`, starting...

Certainly. To cover as much ground as possible, I went through the whole update process in controlled steps. 1. Starting point: ✅ working network with z2m 1.30.3 and herdsman 0.21...

Ah, my bad. I just assumed that v1.30.3 already came with herdsman 0.21, but you're right: it's 0.14 and thus the starting point already was z2m v1.30.3 + herdsman 0.14....