Hub is C8Pro running latest 2.3.8.118 platform.
This problem/observation is not new but now happens well to often to become very annoying and of course. brings WAF (otherwise very high) down. Both Zigbee and ZWave devices exhibiting this problem. I am sure near 100%, Zigbee and Zwave meshes are very healthy. Zigbee mesh could be somewhat compromised because I am in a big apartment complex with gazillions of WiFi routers around. Frankly, I am really surprised Zigbee is actually working and stable in this very not Zigbee-friendly environment. But I don't see any potential problems for the ZWave mesh (it does not mean there is none).
The logs in this case are absolutely useless because once trigger event from the device is logged the rest is flying very fast. I did check time stamps for the Device events from the Device page(s) and time stamps for the correspondent rule(s). In this areas everything is perfectly fine.
But occasionally there is a sizable delay from say, when Button is pressed and before rule is executed. There is absolutely no way to log actual PHYSICAL Button Press Event (again, after hub logs an event the rest is very fast). So, what is going on between PHYSICAL button press and before the correspond Event is logged is absolutely invisible (at least for the end users).
And to make things even more exiting - if button was pressed multiple times because it looked like the rule was not started eventually rule will be executed multiple times. To my eyes it means system actually recorded ALL Events from whatever Device but all these Events processed with significant delays.
Near all my Automations are based on RM. But I am sure, this problem is not RM related.
It is somewhere inside Event Processing Engine.
PS. I asked my wife to wait up to 10+ sec before pressing button second time if it looks like nothing is happening. Most of the time this works, i.e. after a significant delay rule finally executed.
And of course, I heard many times why I cannot fix this if I know what is going on.
Well, I cannot fix this from end user side.