Google Home iOS Bug Caused Smart Lights to Turn On Automatically

According to Android Authority, a strange new bug in the Google Home app for iOS was auto-firing an "on" command to smart lights every time users opened the app — a glitch Google confirmed fixed within hours of the story going public.

The trigger that wouldn't die

The misfire, first logged on Reddit by user MST-1229, hit iPhone and iPad owners with a stubborn payload: launch the Google Home app and every connected lighting device — bulbs, dimmers, LED strips — snapped to on. The Android client and the web dashboard were unaffected, and brand didn't matter. Reports spanned Govee, Philips Hue, Tapo, Kasa, and even hub-bridged setups that talk to other ecosystems. Tapping the physical switch or hitting "off" in-app did nothing; the lights re-fired within seconds. Cleanest diagnosis: the iOS build was pushing an unsolicited state-sync command to lighting endpoints on every cold start, and the endpoints dutifully obeyed.

Workarounds and the wall behind them

With no official patch for several hours, users reached for whatever kill switch they could find. Some force-quit the app repeatedly, others nuked their third-party account links from Google Home settings, and a few unplugged their fixtures outright. The one workaround that actually held: don't open the app. Treat the launcher icon as live ordnance until the fix lands.

That's the real lesson buried in this incident. When your lighting logic runs through someone else's cloud, a bad app update, a misfired routine, or a server hiccup turns your fixtures into non-deterministic actors. The Reviewed team recently spent a week with a $24 mechanical timer switch — a dumb in-wall relay that schedules up to 18 daily on/off events with no Wi-Fi, no app, no hub. No firmware push, no Google account, no cloud outage can flip your hallway light at 3 a.m. If your "smart" lighting is also your only lighting, a non-networked fallback is cheap insurance against the next bad push.

What to watch

Google hasn't published a post-mortem yet, only a brief acknowledgment through its official Google Nest Community account that the issue is resolved. The interesting question is where the bad command originated — client-side in the iOS build, or deeper in the Home API shared by both clients. That answer decides whether your own routines and cross-ecosystem bridges sit behind the same shaky gate. Until then, don't trust a single app to be the only control plane for anything you actually need to stay dark at night.