Tutorial · updated 2026-05-28 · 1 min read
Work around missing custom scenes in Hue automations
When a Hue automation cannot select a custom scene, build a stable fallback scene path instead of stacking fragile workarounds.
If a Hue automation suddenly cannot use a custom scene, first assume a product limitation or app bug rather than a room-design problem. The goal is to preserve the intended lighting state with the least fragile path.
Build the fallback
- Save the look as a standard Hue scene if the app distinguishes between custom, dynamic, and automation-safe scenes.
- Test the scene from the Hue room before attaching it to an automation.
- If only brightness and color temperature matter, recreate those values directly in the automation.
- Keep one manual recovery scene for the room so a failed automation does not leave lights in an odd state.
Let Rhythm own the normal state
Use Hue automations for Hue-specific effects, and let Rhythm define the room’s ordinary Day and Sleep behavior. That way a missing custom-scene option affects only a special routine, not the baseline lighting state of the room.