Timo J. Rinne

Same to me. Also random devices emit intermittently the following: ``` [2024-05-07 12:35:49] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "30294". [2024-05-07 12:35:51] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for...

> For network/route errors: a few of these are normal, it's just the network living it's life. You can also get several during z2m start or during a join (again,...

The majority of the messages are for random end device sensors like TS0201 but also router devices like TS011F_plug_1 are there. The odd one for ZBMINIL2 end-device single wire relay...

> @rinne Do you have the complete log file for those ~24h? I'll take a look, see if I can spot something. Indeed I have. [tr-ember.log](https://github.com/Koenkk/zigbee2mqtt/files/15252768/tr-ember.log)

> @rinne Your network relies heavily on Tuya routers, which are know to be subpar in a lot of cases. Maybe try to add a "good" router next time you...

That particular error hasn't reappeared after I flashed 7.3.1 to the Zigbee stick. The only remaining visible issue is weird log entry when enabling/disabling pairing. I don't remember seeing that...

Yeah, I did. Some new issues arose, but overall it seems to be much better. IMO, it's kinda weird to deprecate the driver in the release with the info that...

I get this too. It appeared out-of-the-blue and first I suspected that there were some go runtime update that I didn't notice that broke it. However, there wasn't. I updated...

Stack trace shows github.com/t3rm1n4l/go-mega.blockDecrypt(0x0, 0x0, ... It smells like wrong, since its: func blockDecrypt(blk cipher.Block, dst, src []byte)

And here is the root() implementation to the same bunch because it's so trivial. I didn't test it too well, but it seems to be ok. ``` // Naive truncating...