Why do Hue wake and sleep effects stop working through Google Home over Matter?

Why do Hue wake and sleep effects stop working through Google Home over Matter?

Because those wake and sleep effects are Hue behaviors, not generic Matter lighting commands. If the room is coming into Google Home through a Matter bridge path, basic light control can still work while vendor-specific effects disappear. For Rhythm, the clean answer is to keep the Hue Bridge as the stable device path and let LightHub own the room behavior above it.

Short answer

If you want predictable wake and wind-down lighting, do not depend on a bridged voice path to reproduce every Hue-specific effect. Use Hue for bridge health and device access, then import the Hue room into LightHub so Rhythm can run the room's daily curve directly.

Best path for Rhythm

The best path is Supported through Hue. Keep the Hue Bridge online, import the room into LightHub, and treat Google Home as an optional voice layer instead of the source of truth for the lighting state.

Before you pair

• Confirm the Hue Bridge is online and can still control the affected room from the Hue app.
• Check that the bulbs respond normally for on, off, dimming, and white-light changes inside Hue.
• Leave the Hue side responsible for firmware and bridge-level maintenance.
• Know which room name you want to preserve when you bring it into Rhythm.

Reset and pairing mode

No device reset is usually needed here. The issue is usually the control path, not a bulb that forgot how to pair. If the bridge itself is healthy, keep the hardware where it is and change the room-control path instead.

Pair with Rhythm

1. Open LightHub and choose Add device -> Hue Bridge.
2. Press the bridge button when LightHub asks for authorization.
3. Import the Hue room that needs stable wake and evening behavior.
4. Set the room's Day and Sleep behavior in Rhythm instead of expecting Google Home to reproduce Hue-only effects through Matter.
5. Test one morning and one evening transition directly from the Hue-plus-LightHub path.

If pairing fails

1. Stop and confirm the bridge still works in the Hue app.
2. Make sure LightHub and the bridge are on the same local network.
3. Remove duplicate room automations from Google Home before retesting.
4. If the bridge is unstable in Hue itself, fix that first before touching Rhythm.

Feature support

• Reliable path: basic room control through the Hue Bridge in LightHub.
• Good fit for Rhythm: daily brightness and white-light behavior at the room level.
• Do not assume bridged Matter control will preserve every Hue-branded effect verb for verb.

Known gotchas from real users

• Basic light control can succeed even when wake or sleep effects do not.
• A bridged path can look healthy enough to hide the real limitation.
• Voice assistants are better treated as triggers than as the room's primary lighting brain.

After it works

Once the bridge path is boring again, move the everyday room behavior into Rhythm and keep Google Home for simple voice requests. Related tutorial: How do you fix Hue lights that work in Hue but not Alexa?

The goal is not to manage another device. The goal is to get the light into Rhythm once, then let the room run.