docs: reconcile number-entity count to five (add ramp_half_width) (#1)

The README What's-new callout and the CHANGELOG 2.1.0 entry still said four number entities, while the README table/intro and the runtime-range-controls spec say five (the four range bounds plus ramp_half_width). Update the callout to list all five and add a CHANGELOG entry for the fifth entity; leave the historical 2.1.0 'four' entry intact. Docs only -- code and spec already reflect five. Filed as openspec change fix-number-entity-count-docs.
This commit is contained in:
Casey Romkes 2026-07-08 23:02:22 +02:00 • committed by GitHub
commit f4ec31ecc8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 48 additions and 1 deletions

View file

@ -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.<profile>_min_brightness` — night-floor brightness (1–100 %)
> - `number.<profile>_max_brightness` — peak-day brightness (1–100 %)
> - `number.<profile>_min_color_temp` — warmest tone (1000–10000 K)
> - `number.<profile>_max_color_temp` — coolest tone (1000–10000 K)
> - `number.<profile>_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