Fix OverkizCommandParam STANDARD/HISTORICAL/ERROR/UNHEALTHY casing regression

[iMicknl]

Follow-up to #2096.

Problem

Four more OverkizCommandParam members were regressed from their lowercase API state values to capitalized variants in #2085 — the same bug class as ON/OFF/UNKNOWN/BATTERY (fixed in #2096):

Member	Was	Now	Real lowercase source
STANDARD	"Standard"	"standard"	io:MemorizedSimpleVolumeState, io:VentilationConfigurationModeState, modbus:DHWModeState, modbus:YutakiDHWVirtualOperatingModeState
HISTORICAL	"Historical"	"historical"	(Linky pair of STANDARD)
ERROR	"Error"	"error"	core:UpdateStatusState
UNHEALTHY	"Unhealthy"	"unhealthy"	core:AirQualityIndexLevelState

The real Overkiz API returns these state values in lowercase, so every equality comparison against these members silently fails — breaking downstream consumers such as Home Assistant's overkiz integration (e.g. DHW/ventilation state maps keyed on OverkizCommandParam.STANDARD).

Root cause

The capitalized values were harvested from other states that emit the same word in different casing (zigbee:LinkyModeState → "Standard"/"Historical", netatmo:HealthIndexState → "Error"/"Unhealthy"). Both casings are real API values, but they collapse to one SCREAMING_SNAKE enum name. The generator's alphabetical sort (codepoint order, capitals first) let the capitalized catalog value claim the name and drop the lowercase value consumers depend on — exactly the mechanism described in #2096.

Fix

1. Restore the four values to lowercase in pyoverkiz/enums/command.py. The generator's existing "preserve established value on a name collision" guard now pins them on regeneration.
2. Extend the OverkizCommandParam.ON/OFF/UNKNOWN regressed to capitalized values in #2085 (API returns lowercase) #2093 regression test (TestOverkizCommandParamApiValues) to pin all four.

Notes / follow-up

• FAIR/POOR were intentionally left as "Fair"/"Poor" — those casings are the only values netatmo:HealthIndexState emits; no lowercase variant exists in the API.
• The capitalized variants (zigbee:LinkyModeState "Standard"/"Historical", netatmo:HealthIndexState "Error"/"Unhealthy") are dropped for now. They're real state values the single-name enum structurally can't represent alongside the lowercase ones. Keeping both would require an explicit alias map in the generator (e.g. STANDARD_LINKY = "Standard") plus a hard failure on unhandled collisions — tracked as a separate change.

Verification

• uv run utils/generate_enums.py is idempotent — all four values stay lowercase after regeneration (+0 new params).
• uv run pytest tests/test_enums.py — 10 passed.

[Copilot]

Pull request overview

This PR is a follow-up to #2096, fixing four additional OverkizCommandParam enum members (STANDARD, HISTORICAL, ERROR, UNHEALTHY) whose values were regressed from lowercase to capitalized in #2085. The real Overkiz API returns these state values in lowercase, so the capitalized values broke equality comparisons for downstream consumers like Home Assistant's overkiz integration.

Changes:

• Restored four OverkizCommandParam values to their correct lowercase form in pyoverkiz/enums/command.py.
• Extended the existing regression test class (TestOverkizCommandParamApiValues) to pin all four new values.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
pyoverkiz/enums/command.py	Changes ERROR, HISTORICAL, STANDARD, and UNHEALTHY enum values from capitalized to lowercase to match real API responses.
tests/test_enums.py	Adds four assertions to the existing regression test to pin the corrected lowercase values.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.