I’m running HA on a raspberry pi with the Aeon z-stick. I’ve got an ecolink motion sensor and a LIFX light bulb. There is an automation trigger set up to turn on the light when there’s motion in the room. It works, but with a 10-15 second lag. If I trigger light.turn_on manually through the developer tools it’s nearly instant. Would going with a separate zwave hub or a more powerful machine for running things cut down on the lag time? Or is this a configuration issue?
I’m running on a PI 3 using an ecolink and I get zero lag. Since your light works without lag, I would suspect latency in your ZWave network between the sensor and the PI - have you tried healing it? That sometimes helps. Checking the timestamps on the messages in your log could help you narrow down what is happening when, and what is taking the time.
Thanks, I’ll give that a shot.
In other news, I thought this was a Raspberry Pi 2, but upon actually looking at the board it’s actually a Pi 1 model B. Whoops. It was in my box of random hardware.
just an update, I’ve confirmed that the lag is happening on the initial trigger, at its worst there’s a 3-4 second delay between when I see the motion sensor LED blink and when it shows up on the event bus. Gonna try a faster PI and see if it’s better.
I’ll try some experiments later to get an idea of my actual lag - I said Zero above, but it could be a second or two (just nothing like the 10 - 15 seconds you initially reported)
Yeah I realized a lot of the original lag was due to the fact that the motion detector isn’t very sensitive, I have to actually get up and walk across the room vs just waving my arms.
I just ran a quick test - on my Pi3 it takes maybe a second to go from detection to switching on the light, so not instantaneous, but pretty fast.