I’d like to ask you about your experiences with the speed of automation execution in Homey Pro. I’ve set up several connections via flows where the speed varies significantly (from time to time). Here are a few examples:
Aqara Smart Wall Switch H1 → Homey Pro → Shelly 2PM Gen4 (turning kitchen lights on/off). It usually takes 1 to 4 seconds between pressing the button and the light turning on.
THIRDREALITY Zigbee motion sensor → Homey Pro → Shelly 1PM Gen4 (turning the living room lights on/off) It usually takes 1 to 7 seconds between detection (I see the light on the sensor turn on) and the actual light turning on.
Philips Hue dimmer switch → Homey Pro → Aqara Smart Plug & SwitchBot Blind Tilt (turn on floor lamp and close blinds) Aqara usually 1 to 3 seconds & SwitchBot usually 3 to 15 seconds.
These devices are all located around the Homey Pro, with no long distances between them. Can anyone tell me why there is so much delay and so much variation here? Can this be resolved to make it more stable?
It depends a lot on the environment. How far away is Homey from your router? And how far away is the Shelly from your router? Can you go to https://speedtest.net and show your latency? That can also impact connection speeds. Do you have other Zigbee networks on the same Zigbee channel as Homey? You can check Homey’s Zigbee channel here.
Something important to mension is that the shelly devices are also configured as zigbee devices. In total is have 29 zigbee devices now. No other zigbee master in the house (i think this is what you mean by this question “Do you have other Zigbee networks on the same Zigbee channel as Homey?”)
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.
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.
The automation/flow itself yes. I hope, this is executed within millisec’s. BUT unfortunately i must join with the author of original post. Have also flow(set) which one manages the lights in bathroom. Different times/different lights, auto switching off etc…
Have multiple sensors for presence. The door and IR motion. Usually during active time the system works quite well and have no problems with that. But usually then, when there was no activity during longer periods ( nights, working days) the lights may delay… sometimes even ~10s.
My working hypotesis is, that the Homey goes to sleep and the wake-up may take time. Yeah, it’s not excluded, that there is something in my network, but the devices are in 2 different net ( Z-wave and Matter)
And yeah, have also plans to go into bathroom with opened app - to see, if/when devices (alarms) chenge their statuses, but as The Situations are quite rare, then usually wins need to go and not the “open/take phone app” Also… if Homey (really) goes to sleep, then i think the app-connect wakes him up anyway.
Just my 10 cents. May-be related with initial problem, may-be not.
I think it can be due to Matter-over-wifi sensors.
My first sensors were wifi based, and it often took over 8s to wake up, reconnect to wifi and send an event.
So wifi based battery powered sensors which should respond immediately are the worst choice imho.
Homey having a unmanageble possible standby / sleep mode is unknown to me.
Battery devices are almost continously in sleep mode, I would search for delays with these type of devices.
And if it’s zigbee or Matter-over-Thread sensors, check the zigbee and 2.4GHz wifi channels for least interfering channel numbers.
A frustrated zigbee/Thread mesh network can be very sluggish.
Also check for chatty devices (choking the mesh with tons of events) here: https://tools.developer.homey.app/tools/zigbee
When you use BOTH protocols, try to stick to one, for better performance / less hickups
Also… if Homey (really) goes to sleep, then i think the app-connect wakes him up anyway.