|
2 | 2 |
|
3 | 3 | All notable changes to this project will be documented in this file. |
4 | 4 |
|
5 | | -The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), |
6 | | -and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). |
| 5 | +The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and |
| 6 | +this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). |
| 7 | + |
| 8 | +## [0.2.2] - 2026-02-14 |
| 9 | + |
| 10 | +### Fixed |
| 11 | + |
| 12 | +- Handle non-string entity IDs in entity expansion |
| 13 | +- Config flow typing and lint issues |
| 14 | +- Typing and lint issues for light controller services |
| 15 | + |
| 16 | +### Changed |
| 17 | + |
| 18 | +- Updated documentation for v0.2.1 release |
| 19 | +- Updated contributor documentation with current tooling and versions |
| 20 | +- Updated core instruction files to reflect current environment |
| 21 | + |
| 22 | +### Added |
| 23 | + |
| 24 | +- Skills for Home Assistant integration development |
| 25 | +- Link verification tooling and report |
| 26 | +- uv.lock file for package management |
7 | 27 |
|
8 | 28 | ## [0.2.1] - 2026-02-07 |
9 | 29 |
|
10 | 30 | ### Added |
| 31 | + |
11 | 32 | - Per-entity state and transition support in presets |
12 | 33 | - Mixed on/off states in single preset (e.g., turn some lights on, others off) |
13 | 34 | - Per-entity transition times with fallback to global preset transition |
14 | 35 | - `_send_commands_per_target()` method for handling mixed-state presets |
15 | 36 |
|
16 | 37 | ### Changed |
| 38 | + |
17 | 39 | - Updated Python requirement to 3.14.2 (Home Assistant 2025.2.0+) |
18 | 40 | - Updated minimum Home Assistant version to 2025.2.0 |
19 | 41 | - Improved documentation clarity and removed early beta disclaimer |
20 | 42 | - Preset creation now derives preset-level state/transition from per-entity configs |
21 | 43 |
|
22 | 44 | ### Fixed |
23 | | -- Preset configuration gaps where UI-collected per-entity settings were not used by backend |
| 45 | + |
| 46 | +- Preset configuration gaps where UI-collected per-entity settings were not used by |
| 47 | + backend |
24 | 48 | - Hardcoded `state="on"` and `transition=0.0` in preset creation |
25 | 49 | - Minor bug fixes and stability improvements |
26 | 50 |
|
27 | 51 | ## [0.2.0] - 2026-01-31 |
28 | 52 |
|
29 | 53 | ### Removed |
| 54 | + |
30 | 55 | - Notification feature (`notify_on_failure` parameter) |
31 | | -- Blueprint automation templates (adaptive_lighting, button_scene_controller, motion_activated_scene, scene_scheduler) |
| 56 | +- Blueprint automation templates (adaptive_lighting, button_scene_controller, |
| 57 | + motion_activated_scene, scene_scheduler) |
32 | 58 |
|
33 | 59 | ### Changed |
| 60 | + |
34 | 61 | - Simplified scope to focus on core light control and preset management |
35 | 62 | - Updated documentation to reflect current feature set |
36 | 63 |
|
37 | 64 | ### Notes |
38 | | -This release removes features that were not essential to the core functionality. |
39 | | -Users requiring notifications can implement them via automations triggered by |
40 | | -service responses. The core ensure_state service and preset management remain |
41 | | -fully functional. |
| 65 | + |
| 66 | +This release removes features that were not essential to the core functionality. Users |
| 67 | +requiring notifications can implement them via automations triggered by service |
| 68 | +responses. The core ensure_state service and preset management remain fully functional. |
42 | 69 |
|
43 | 70 | ## [0.1.3] - 2026-01-31 |
| 71 | + |
44 | 72 | - Previous release (see git history) |
0 commit comments