@DDoug23 I am experiencing the same issue as your original post, I have Smart Things compatible (SmartThings Aeotec Zigbee) motion sensors triggering Philips Hue lights to turn on when motion detected, and there is a 1 - 6 minute delay (this started somethimg in past week). I’ve rebooted by ST hub and Phillips Hue hub and the issue perists. I’m in the UK.
I did some basic troubleshootimg by walking in the relevant rooms and looking at the Motion Sensor History in the ST iOS App and it looks lo me like the Motion Sensors themselves are either not firing the Motion Detected signal immediately (seems unlikely), or they are firing the signal, and the data isn’t getting back to ST until minutes later. I can walk into a room at 12:26pm (for example) and the motion detection doesn’t show up in the log until 12:30pm.
The History screen on the sensor seems to show the laggy timestamp and not the actual time I walked into the room. I have no idea what to try next to fix the lag on theses sensors.
I have the same brand of sensor in multiple rooms and they are all behaving the same way.
Yup, removed and re-added one of the sensors and it makes no difference. The motion detection is taking minutes to show up in the app. I have several of these sensors and they have all started doing this in the past week (whilst I was away on holiday). These have been working for years without an issue. This doesn’t look like a hardware issue on the sensor to me. They all detect motion, it just takes minutes to show up in the app or trigger any smart lighting routines.
It seems a bit coincidental that the original poster has exatly the same issue as me. This must be down to a bad software update somewhere to affect all my sensors at the same time.
That user mentioned restarting the hub by unplugging it helped. So, it’s good to see it was the solution for you as well.
Just as a reference, other users who have had this issue mentioned their power cable was failing, and the hub wasn’t receiving the proper energy to work.
To verify where the delay is, we would need to analyze driver and Hub logs in case it happens in the future.