Follow the origin removal and colour light wire changes #127
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/colour-light-no-origin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follows two breaking firmware wire changes (CCS-HA-61). Firmware #116 removed the origin byte and the manual lockout byte, so the codecs, lockout attributes, ORIGIN constants and bench transcription are gone, and
Spec sectioncitations are renumbered (old 9.x shifts down one). Firmware #107 turns the CCT light into a colour light:CMD_COLOUR/STATE_COLOUR, presented asPK_COLOUR. The HA light now drives brightness, colour temperature and HS colour throughCMD_COLOUR, and on/off throughCMD_SWITCH. Asking for a colour temperature sends saturation 0, so the light is white at that temperature.The shared vectors are taken from firmware main, which now includes #107.
Tested: ruff, mypy and the full suite pass locally (1314 passed, 3 skipped).
Offsets in catalogue.py and frame_bench match the kitchen-cct spec. Findings below.
@ -70,0 +123,4 @@"""Asking for a colour temperature also takes the light out of any hue it was in."""changes: dict[str, int] = {}if ATTR_BRIGHTNESS in kwargs:changes["brightness"] = round(kwargs[ATTR_BRIGHTNESS] * 100 / FULL_BRIGHTNESS)Brightness 1 to 2 of 255 rounds to 0 %, so a dim request on a colour light sends brightness 0. Clamp to at least 1 when a brightness was asked for. No test covers the low end.
Stale "9.5" in the docstring. Should be 9.4. Also line 1774 still says "as a remote request", which no longer means anything.
Still cites "spec section 9.5". The sequence counter is 9.4 now.