Scenes, scripts and automations that still turn off a Hue light effect with effect: "None" will break in Home Assistant 2026.11. Change #188867 by Martin Hjelmare, merged into the development branch on 27 October 2026 and marked as a breaking change, removes the compatibility mapping that kept that value working.

A deprecation that ran a year late

The story starts with Home Assistant 2025.4. That release stopped accepting None as an effect for Hue lights and replaced it with Home Assistant's standard value off. For commands sent by hand that was fine, but nobody had noticed that existing scenes used the old value.

A fix merged on 2 April 2025, change #142073, turned the break into a deprecation. Home Assistant translated None to off, wrote a warning to the log and raised a repair issue. The planned end date in the code was Home Assistant 2025.10, while the description of that change mentioned 2025.12. Neither date was kept, and the mapping stayed in place for another year.

What the change removes

The change touches the code for bridges that use the Hue v2 API:

  • the translation of None to off when a light is turned on;
  • the log warning "Detected deprecated effect 'None' ... use 'off' instead";
  • the repair issue "Light turned on with deprecated effect" and its texts;
  • the test that covered the old behaviour.

After the update Home Assistant no longer converts None to off. The Hue code treats the value like the name of any other effect, so the call can no longer be counted on to stop an effect that is running.

What to do

Search your configuration for effect: "None" or effect: None in Hue light actions, scenes and scripts, and replace it with effect: "off". The breaking change note in the change asks for exactly that.

The value off behaves sensibly. The Hue code uses it only to stop an effect that is running. If no effect is active, it is ignored, so it is safe to leave in scenes that set a plain colour.

If the repair issue "Light turned on with deprecated effect" has ever appeared under Settings > System > Repairs, at least one of your lights was turned on this way. Fix those calls while you are still on 2026.10, because the repair issue disappears together with the mapping.