v0.29.0

Added

• Scene actions can now target by entity, device, area, floor, or label (like
  Home Assistant automations). The target resolves live at apply time and is
  constrained to the scene's scope, with a live count in the editor showing how
  many entities the target will act on. A directly-named entity is forwarded
  unchanged — it is the author's deliberate choice and is never scope-clipped.
  The device/area/floor/label picker needs Home Assistant 2026.1 or newer; on
  older versions the action editor falls back to entity-only targeting.
• The safe cover actions — Open cover, Close cover, Set cover position, and Set
  cover tilt — are now seeded as default actions on new installs, so covers work
  in scenes out of the box.
• The Actions settings page now shows a dismissible recommendation to install
  the Fado Light Fader integration (smooth light fading with automatic
  brightness restoration) when it isn't already installed.
• The Lux condition now has an "is / is not" choice, so a scene can match when
  your light sensors are not in a chosen range — for example, blocking a scene
  until the room is no longer bright.

Changed

• The action editor no longer prevents two actions in the same scene from
  targeting the same entity (Home Assistant's native target picker cannot hide
  individual entities); contradictory actions apply in order, last-write-wins.
  The config-health overlap warning still flags entities controlled by more than
  one scope/category group. A new target_empty Repairs warning flags an action
  whose target resolves to no entities in its scope.
• In the Lux and Occupancy conditions, the "Any of / All of" selector now sits
  above the sensor list (and only appears when more than one sensor is chosen),
  and their summaries read more naturally — e.g. "Any of (Lounge, Hall) is
  bright", "All of (Lounge, Hall) are detected", "Lounge is unavailable".
• The Advanced settings tab now has a clearer visual hierarchy. Section titles
  stand out from their fields, the two setting groups are more obviously
  separated, and the voice-assistant toggles are presented as a nested
  sub-section of the scope-level pause switch (their switches still line up with
  the fields above).

Removed

• The admin-only ambience.apply_scene action — for calling Ambience from your
  own automations and scripts — has been removed. Automatic scene application
  (as conditions change) and the panel's Run / apply controls are unaffected;
  only the standalone service is gone.

Fixed

• When overriding a built-in time-of-day period (e.g. "Dawn") or lux range, the
  name field now defaults to the range's current name instead of starting blank
  with only the "e.g. Wind down" placeholder. You can still rename it or clear
  it.

Full Changelog: v0.28.0...v0.29.0