The actual automations can’t execute slowly, I’ve never experienced such thing.
The delay is mainly caused by connection issues, like interference and/or devices flooding your zigbee mesh, and/or (a) crappy device(s).
For instance one zigbee device which sends shitloads of updates, can choke the complete mesh network.
You can view your zigbee and zigbee device details at https://tools.developer.homey.app/tools/zigbee
I don’t think wifi speed is related in this case. But, to discover at what speeds Homey can send/receive network packets, give the Fast.com Speedtest app a go.
Too close can be an issue, when “next to each other” means within 1 cm to 2 metres. Increase the distance between router and Homey to see if it makes a difference.
You can discover if the delay is caused by the trigger device, or by the commanded device, by connecting notification cards, like timeline-, push- or simple log app cards to the trigger and to the action cards;
When notification arrives at the same time of the device sending a trigger > the delay is an issue with the commanded device;
When notification arrives at the same time of the responded commanded device > the delay is an issue with the trigger device.
My guess there’s too many interference caused by your 2.4GHz wifi , or caused by your close neighbour’s 2.4GHz wifi.
Here’s an extended zigbee tuning guide to help you solve it:
https://community.homey.app/t/advanced-zigbee-troubleshooting-on-homey/115930
