Skip to content

0.7.0

Choose a tag to compare

@jl0906 jl0906 released this 25 Jul 15:31
ee2282b

Changelog 0.7.0

Advanced YAML light-automation import for nested actions, paired timer workflows, adaptive profiles, and sequential master/slave motion rules.

Added

  • New advanced automation analyzer with a JSON-safe intermediate representation.
  • Recursive discovery of supported service actions inside nested if, then, else, and choose branches.
  • Pairing of a motion-driven timer.start automation with the single timer.finished automation that switches off the same lights.
  • New Advanced YAML bundles cards and a dedicated review/import popup.
  • Transactional import of multiple source automations into one SmartHomeAssistant room configuration.
  • Trigger-specific motion-to-illuminance mappings.
  • Structured sun-elevation lux profiles with automatic toggle and manual helper fallback.
  • Structured illuminance-to-brightness profiles with automatic toggle and manual helper fallback.
  • Conversion of source ownership-marker helpers into SmartHomeAssistant's internal managed-light ownership.
  • Support for one-sided daily time conditions such as after: 05:00:00.
  • Recognition of supported wait_for_trigger sequences as a standalone managed automation rule.
  • One-use temporary grants where the first motion sensor authorizes a second motion sensor for a fixed window.
  • Separate switch-on and switch-off transition values.
  • Separate inactivity switch-off delay and maximum on-time.
  • single-style sequence protection and restartable timer-room behavior.
  • New administrator-only WebSocket imports for advanced bundles and sequences.
  • Additive automation_rules storage and advanced room-profile fields.
  • Import records with multiple source IDs, entities, names, enabled states, and raw backup configurations.
  • Undo that removes the generated rule, restores the previous room, and re-enables every source disabled by the import.
  • Regression tests based on the hallway adaptive-light pair and bedroom-to-hallway night-light sequence.

Safety

  • Source YAML files are never edited, rewritten, or deleted.
  • Templates are never executed; only recognized entities, helpers, numeric branches, and fixed durations are extracted.
  • Advanced imports require stable automation IDs, valid entities, a valid target area, and an unambiguous structural match.
  • Timer bundles require exactly one matching off automation and identical on/off light targets.
  • Keep originals stores the replacement disabled to prevent duplicate control.
  • Disable originals is applied only after the imported configuration validates and is stored successfully.
  • Failed multi-source operations roll back the room/rule and re-enable sources changed during the transaction.
  • Temporary sequence grants and timers are discarded after restart.
  • The master sensor in a sequence never switches the light directly; only the target presence sensor can consume its grant.

Changed

  • Sidebar frontend component advanced to release-specific v070.
  • Config entry minor version increased to 7.
  • Room runtime now supports trigger-based lux selection, adaptive structured profiles, distinct transitions, maximum on-time, and timer-expiry switch-off.
  • The Automations page suppresses misleading generic import suggestions when an advanced bundle or sequence has been recognized.
  • Learning moved to 0.8.0 and vacation simulation moved to 0.9.0.