So I am having some issues with heavy slow downs with my Homey Pro (2023) and I don’t know what the issue is. My house mostly consists of Z-Wave devices with a few ZigBee devices thrown in there.
I have a main power switch in my house that turns on/off everything at the same time, this causes huge delays for up to half a minute before things start happening, and sometimes it will not even run all the commands. I’ve experimented with adding a slight delay between triggers to spread out the load which seems to have fixed the issue of commands not being run, it is however still slow.
Another issue is if I use Chronograph Transitions with a short duration and many dim steps per second. Ideally I want lights to slowly dim on over a 2-5 second period, this seems to be very problematic. I’ve figured it’s doable with a max dim step per second of 3 for a single light. Doing a fade in on more than one light at a time I can just forget about.
So what is the problem here? Is it Homey that is too weak, am I overloading the Z-Wave network? Is there a solution to this, or some kind of best practice? At this point I am a bit frustrated, but I don’t know if my mistake was choosing to buy a Homey or to buy Z-Wave devices. Having worked with DALI devices before, this was not an issue as far as I remember.
Homey just can’t command many devices (of the same protocol) at once.
Next, standard flow cards are all fired at once, regardless of the order they’re in.
In advanced flow you can ‘daisy chain’ the flowcards, which makes them fire one by one with a slight delay.
But with group devices of community apps like Device Capabilities (Advanced virtual device, < group > (Blended & United group) or Boolean Toolbox (State device - WIP), there’s a minimal (adjustable) delay in ms between every group member; this way you can command many devices “at once”.
.
Most probably there’s one or more “chatty” devices, choking the mesh communication, making it the main issue most probably.
Known devices for excessively flooding the mesh are Aeotec sensors for example.
Go to https://tools.developer.homey.app/tools/zwave
and check the tx and rx columns for (extremely) deviating numbers.
This probably are the devices causing the sluggishness.
When you’re lucky you can decrease polling intervals, or max updates per time-unit, per device settings.
With Boolean Toolbox , you should be able to force flow using the logic gates. I would think that simple AND formulas would be effective for stopping a flow until it’s synchronized, for example.
Actually…OR would suffice as you can set the gates to not continue until all inputs are set. Using AND, OR, XOR etc should be valuable for flow control and synchronization (haven’t tried specifically for that, but the option to wait for all inputs to be set would have that effect).
