Hopefully a simple change, but care is needed to check the logic. I have
tested on the simulator, but then I did also last time and the logic was
wrong.
Clarified user etiquette expectations and addressed public opinions on application complexity.
Signed-off-by: Philip Abbey <philipabbey@users.noreply.github.com>
1. Originally intended bug fix:
<img width="577" height="890" alt="image"
src="https://github.com/user-attachments/assets/f04f720d-01f4-43fb-85ef-2b7e2a11099d"
/>
2. Fixes for the schema regarding numeric `tap_action`.
3. Code fix to initialise numeric pickers when no user defined template
is supplied.
4. Amended version history.
Add schema metadata and stricter validation for numeric tap_action: include title & description, disallow additionalProperties on the tap_action and its picker properties to better define the number picker payload. Update HISTORY.md with a 3.14 entry documenting numeric items now supporting tap_action.data and the PIN/menu behavior change, and credit the contributor.
Numeric menu items currently discard existing `tap_action.data` when
confirming a picker value. This prevents service call options such as
`transition` from being sent with `light.turn_on`.
This change passes `tap_action.data` into numeric menu items and merges
that data with the selected numeric picker value before calling the Home
Assistant service.
Example fixed payload:
```json
{
"entity_id": "light.living_room",
"transition": 2,
"brightness": 128
}
Tested with a Forerunner 965 build and a Home Assistant light brightness numeric picker.
Added proposed documentation section explaining Numeric data object and also updated JSON schema to match changes.
I tested the numeric example with tap_action.data in the documented web editor. The current schema did not appear to reject the field,
likely because numeric tap_action does not currently forbid additional properties at that nested level. I still added data explicitly
to the numeric schema so it is documented, discoverable, and type-checked as an object.
Store the smaller "glance" subsection of the JSON menu in Storage under
a new key (scStorageKeyGlance) and read the glance template from that
cache to prevent out-of-memory errors from large menus. Removed menu
status field from the Glance UI and simplified the status view to a
single API status line when no custom template is present. Documentation
and images updated to reflect changes.
Don't merge yet, I will test on my watch first.
