rhythm.lighting
← All tutorials

Tutorial · updated 2026-07-25 · 2 min read

How do you stop Google Home lights from turning on at night?

Trace unexpected late-night Google Home lighting, remove duplicate schedules, and give each room one predictable daily source of truth.

Why do all the lights come on in the middle of the night?

When every Google Home-connected light turns on after everyone is asleep, the cause is usually an old routine, a second app, a power-recovery setting, or a room command reaching more devices than expected. The fix is to stop treating this as a pile of scenes and make Rhythm the source of truth for the room.

What this solves

  • Several rooms turn on at roughly the same late-night time.
  • Google Home shows no obvious routine that explains the change.
  • Vendor schedules and voice-assistant automations may overlap.
  • You want the lights to return to a predictable bedtime state after a manual command.

Before you start

  • Write down the exact time and affected rooms the next time it happens.
  • Confirm whether each light still responds in its primary vendor app.
  • Check whether there was a brief power or network interruption near the same time.
  • Identify the stable path Rhythm will use for the room: Hue, Home Assistant, or compatible Matter lighting through LightHub.

Do it in Rhythm

  1. Open Rhythm and add the existing lighting hub or compatible Matter lights through the supported path.
  2. Put only the lights that should behave together into the same Rhythm room.
  3. Set a Day profile for normal daytime behavior and a warmer, dimmer Sleep profile for bedtime.
  4. Test one temporary manual override, then confirm the room returns to its normal profile instead of keeping a stale scene.
  5. Leave the room running for two nights before adding more schedules or voice shortcuts.

Avoid double automation

Review Google Home automations, household routines, personal routines, and every bulb or bridge app connected to the affected lights. Disable duplicate bedtime, wake, presence, sunset, and vacation schedules one at a time. Keep Google Home for voice commands, and let Rhythm own the normal daily curve.

When this is actually a device problem

If only one bulb changes state, the event follows a power flicker, or the light also misbehaves in its primary app, inspect that device's power-recovery behavior and network connection first. If several unrelated rooms change together at the same timestamp, keep looking for a shared automation or controller event.

Good Rhythm settings to start with

  • Use one Day profile and one clearly dimmer Sleep profile.
  • Start with a moderate evening fade instead of several scene changes.
  • Keep manual overrides temporary so they cannot become an accidental overnight state.
  • Change one room first, observe it, then copy the pattern.

Once the room is stable, let Rhythm run the daily curve and keep the vendor app for firmware or special effects.

Filed under
google-homeunexpected-lightsautomationnight-lighting