This is one disadvantage of the cloud aspect of ST. The motion sensor needs to report that motion is happening to the hub, then the hub has to communicate this to the cloud, which has to then process and this and decide what action to take, then send the command to turn on the light to the hub, which needs to send it the lights. This all happens very fast, but not instantly.
Still, 3-5 seconds seems like a long time. I guess I’d check to see if the motion sensor is seeing motion right away or not. There’s a red LED inside the AEON that will light up when it sees motion. Does this flick on right away? Is it a case of:
Red LED in motion sensor turns on.
3-5 second delay
Light turns on
Or is it a case of:
2-3 second delay
Red LED in motion sensor turns on
1-2 second delay
Light turns on.
If it’s the first example, then I guess I’d contact support and have them help you look through some of the logs to see if they can find a bottleneck and correct it.
But if it’s the second, then we need to look at the motion sensor and see what’s going on there. There is a sensitivity knob in in the sensor… I’d definitely play with that to see if you can get that red light to click on faster. Also angle is important too. The directions in the box give you some information on what the angle of the sensor is in terms of where it can see.