11-09-2025 05:30 AM - edited 11-28-2025 01:04 PM
https://drive.google.com/file/d/10vTFsqtvRj4lkKIw79ucMg7US0xeBjw_/view?usp=drivesdk I'm deep in the Google ecosystem and have a ton of devices. For the last few weeks, my motion lighting automations have gone haywire with a bizarre, time-based bug.
The Gist:
Between 8 AM and around 9 PM, everything works perfectly—motion triggers lights on, no problem. But, after 9 PM, the motion sensors (both Hue and Aqara) simply stop detecting motion for the purpose of triggering lights through Google Home.
What I Know:
The actual lights are fine. I can turn them on and off instantly in the Hue app, so it's not a connectivity or power issue for the lights.
The sensors might be fine, but the automation tied to them is failing specifically after 9 PM.
What I've Tried (No Fix):
Deleting and recreating all automations.
Joining and leaving the Google Home Public Preview.
Full network reset (new SSID and everything).
Has anyone seen a weird issue like this? It's like Google Home flips an internal switch at night that disables my motion triggers. Any suggestions for things I haven't tried yet?
Still the same I've added a video link above to show what's happening.
#Google please someone must have a fix