diff --git a/CHANGELOG.md b/CHANGELOG.md index 26a43af0..26b6db93 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -47,6 +47,13 @@ maintainers who can actually fix them for everyone. (rare; can happen during very early HA startup), the sensor renders as `unknown` for that tick — the other two sensors continue updating normally. +- **Fifth live-tunable `number` entity: `ramp_half_width`** (5–120 min) — + completes the runtime curve-control set alongside the four range bounds + (`min_brightness`, `max_brightness`, `min_color_temp`, `max_color_temp`). + It tunes the tanh ramp half-width around each sun event live and persists + via `RestoreNumber`; unlike the four range fields it is not surfaced in the + options dialog. Shipped earlier without a changelog entry — recorded here + for completeness. ### Changed diff --git a/README.md b/README.md index e6f6213c..bb2ec46f 100644 --- a/README.md +++ b/README.md @@ -67,13 +67,14 @@ > > ## ✨ What's new in 2.1 > -> Each profile now exposes **four live-tunable sliders** as `number` +> Each profile now exposes **five live-tunable sliders** as `number` > entities you can drop on any Lovelace card: > > - `number._min_brightness` — night-floor brightness (1–100 %) > - `number._max_brightness` — peak-day brightness (1–100 %) > - `number._min_color_temp` — warmest tone (1000–10000 K) > - `number._max_color_temp` — coolest tone (1000–10000 K) +> - `number._ramp_half_width` — curve ramp half-width (5–120 min) > > **Slider position is the runtime truth.** Move a slider on the dashboard > and the curve picks it up on the next tick — no integration reload, no @@ -93,6 +94,7 @@ > - number.dining_mvp_max_brightness > - number.dining_mvp_min_color_temp > - number.dining_mvp_max_color_temp +> - number.dining_mvp_ramp_half_width > ``` > > Also in 2.1: **entity friendly names are now readable.** A profile named diff --git a/openspec/changes/fix-number-entity-count-docs/.openspec.yaml b/openspec/changes/fix-number-entity-count-docs/.openspec.yaml new file mode 100644 index 00000000..8cceb8d5 --- /dev/null +++ b/openspec/changes/fix-number-entity-count-docs/.openspec.yaml @@ -0,0 +1,2 @@ +schema: spec-driven +created: 2026-07-08 diff --git a/openspec/changes/fix-number-entity-count-docs/README.md b/openspec/changes/fix-number-entity-count-docs/README.md new file mode 100644 index 00000000..79d20b64 --- /dev/null +++ b/openspec/changes/fix-number-entity-count-docs/README.md @@ -0,0 +1,3 @@ +# fix-number-entity-count-docs + +Reconcile CHANGELOG and README to five number entities (adds ramp_half_width) diff --git a/openspec/changes/fix-number-entity-count-docs/proposal.md b/openspec/changes/fix-number-entity-count-docs/proposal.md new file mode 100644 index 00000000..1d9b556d --- /dev/null +++ b/openspec/changes/fix-number-entity-count-docs/proposal.md @@ -0,0 +1,24 @@ +## Why + +The count of `number` entities per profile is inconsistent across the Adaptive Lighting docs. The integration exposes **five** live-tunable `number` entities per profile — the four range bounds (`min_brightness`, `max_brightness`, `min_color_temp`, `max_color_temp`) plus `ramp_half_width` — as stated in the README reference table ("Number entities (5)") and intro ("five live-tunable sliders"), and as required by the `runtime-range-controls` spec ("exposes five runtime curve entities"). But two doc locations still say four: the README's top callout block ("four live-tunable sliders", listing only the four range entities) and the `CHANGELOG.md` `2.1.0-cdit.1` "Added" entry, which introduced the original four and was never followed by an entry recording the fifth (`ramp_half_width`). A reader gets contradictory counts inside the same README. + +## What Changes + +- **README**: update the top callout block (the "four live-tunable sliders" section) to list all five entities, adding `number._ramp_half_width`, so it matches the reference table and intro further down the same file. +- **CHANGELOG**: add an entry under the appropriate unreleased version documenting the `ramp_half_width` number entity as the fifth live-tunable slider. Leave the historical `2.1.0-cdit.1` "four" entry intact — it accurately records the release that introduced the first four; the gap is the missing later entry, not a wrong historical one. +- No source change: the implementation already creates five entities. +- No spec change: `runtime-range-controls` already specifies five (its "four range entities" wording refers to the range subset, distinct from the ramp control). + +## Capabilities + +### New Capabilities + +None. Documentation-only correction. + +### Modified Capabilities + +None. `runtime-range-controls` already reflects five entities; behavior is unchanged. + +## Impact + +- `Adaptive_lighting/README.md` (top callout block) and `Adaptive_lighting/CHANGELOG.md` (one added entry). No source or spec files change. diff --git a/openspec/changes/fix-number-entity-count-docs/tasks.md b/openspec/changes/fix-number-entity-count-docs/tasks.md new file mode 100644 index 00000000..34d1aa38 --- /dev/null +++ b/openspec/changes/fix-number-entity-count-docs/tasks.md @@ -0,0 +1,9 @@ +# Tasks + +## 1. Reconcile the number-entity count across the docs + +- [x] 1.1 In `README.md`, update the top callout block that says "four live-tunable sliders" to list all five entities, adding `number._ramp_half_width` +- [x] 1.2 In `CHANGELOG.md`, add an entry under the current unreleased version documenting the `ramp_half_width` number entity as the fifth live-tunable slider; leave the historical `2.1.0-cdit.1` "four" entry unchanged +- [x] 1.3 Verify the README intro ("five live-tunable sliders") and the reference table ("Number entities (5)") now agree with the corrected callout +- [x] 1.4 Grep the repo for other stale "four ... number"/"four ... slider" doc references and fix any stragglers +- [x] 1.5 Leave source and the `runtime-range-controls` spec untouched (both already reflect five entities)