I think something in the whole system changed so it gets kind of flooded with something that causes the whole System to be busy. Once the system starts to show taht delay its done…and not getting any better. Its a dance between bad and worse sometimes it takes 5 seconds to react and sometimes it takes 30 seconds to handle the commands.
what can we do to get this solved? I think my two comparison videos show the difference quiet well and that the delay above 2.23.02 is far far from useable.
I can do a list of devices in my network to - that way we can check if we got any devices in common
I can do more logs if needed. it would be nice to have a stable version so we can use recently released devices.
After moving half to zigbee2mqtt with my devices and not got this to work stable in the first try (i think if i had more time it could have been not that worse) i reverted everything back to deconz and started my docker again.
i had 60 devices i had to re-pair and the hole network after that process was behaving like a complete mess for almost 2 days. with lights switching randomly, lights i could not control, motionsensors not working and so on - i rebooted several times and also had to re-pair some lights multiple times to get this whole network stable again.
This is why i hate to test in my daily surroundings - on the other side it is nearly impossible for a normal user to build a testsetup because going back to af unctional network is sometimes as difficult as it is to find the failure. there is alway component X in that equation that makes reverting unpredictable
Hope you get this sorted out soon thanks again for the effort with your testing - hope we get this whole issue fixed in near future.