fix(fw): bump home-assistant to 2026.5.4 + light color_temp→kelvin #138

Merged
dominik.polakovics merged 1 commit from fix/fw-ha-pin-bump into main 2026-06-08 01:04:42 +02:00

What

Bumps fw's pinned Home Assistant 2025.3.4 → 2026.5.4 and fixes the config breakage the jump surfaces.

Why

HA on fw is pinned via fetchGit independently of the host channel. The stale pin (HA 2025.3.4, Python 3.13) mismatched the 26.05 host-channel customComponents (epex_spot, now Python 3.14), breaking component/auth loading — the command_line LDAP auth provider failed to register (homeassistant.auth.InvalidProvider), so LDAP login returned 500s. Bumping to a current nixpkgs (HA 2026.5.4, Python 3.14) realigns the toolchain.

Changes

  • default.nix: fetchGit rev 18dd725c331800d (HA 2026.5.4).
  • light.nix: 7× color_temp (mireds) → color_temp_kelvin in light.turn_on (HA 2026.3 removed the mireds parameter). 250→4000K, 450→2222K.

Why 2026.5.4 and not the latest (2026.6)

2026.6 removes the legacy template entities, of which we still have 11. Holding at 2026.5.4 (where they only emit deprecation warnings) keeps this PR a fix rather than a migration. The template migration + the 2026.6 bump are tracked in #137.

Verified

  • nix build of HA 2026.5.4 with fw's full extraComponents set: OK.
  • Pre-commit eval of fw: OK.

⚠️ Before merge

Merging auto-deploys (≤5 min) and triggers a one-way HA recorder DB migration (~14 months of schema). Take a fresh HA + hass DB backup first. Do not merge until the backup is confirmed.

Not covered

UI-managed automations in /var/lib/hass/automations.yaml aren't in the repo. After deploy, check Settings → System → Repairs for any residual color_temp / legacy-template issues there.

## What Bumps fw's pinned Home Assistant **2025.3.4 → 2026.5.4** and fixes the config breakage the jump surfaces. ## Why HA on fw is pinned via `fetchGit` independently of the host channel. The stale pin (HA 2025.3.4, **Python 3.13**) mismatched the 26.05 host-channel customComponents (`epex_spot`, now **Python 3.14**), breaking component/auth loading — the `command_line` LDAP auth provider failed to register (`homeassistant.auth.InvalidProvider`), so LDAP login returned 500s. Bumping to a current nixpkgs (HA 2026.5.4, Python 3.14) realigns the toolchain. ## Changes - `default.nix`: `fetchGit` rev `18dd725c` → `331800d` (HA 2026.5.4). - `light.nix`: 7× `color_temp` (mireds) → `color_temp_kelvin` in `light.turn_on` (HA 2026.3 removed the mireds parameter). 250→4000K, 450→2222K. ## Why 2026.5.4 and not the latest (2026.6) 2026.6 removes the legacy template entities, of which we still have 11. Holding at 2026.5.4 (where they only emit deprecation warnings) keeps this PR a fix rather than a migration. The template migration + the 2026.6 bump are tracked in **#137**. ## Verified - `nix build` of HA 2026.5.4 with fw's full `extraComponents` set: **OK**. - Pre-commit eval of `fw`: **OK**. ## ⚠️ Before merge Merging auto-deploys (≤5 min) and triggers a **one-way HA recorder DB migration** (~14 months of schema). Take a fresh HA + `hass` DB backup first. **Do not merge until the backup is confirmed.** ## Not covered UI-managed automations in `/var/lib/hass/automations.yaml` aren't in the repo. After deploy, check **Settings → System → Repairs** for any residual color_temp / legacy-template issues there.
The HA package is pinned via fetchGit independently of the host channel. The stale pin (18dd725c = HA 2025.3.4, Python 3.13) mismatched the 26.05 host-channel customComponents (epex_spot, now Python 3.14), breaking component/auth loading — the command_line LDAP auth provider failed to register (homeassistant.auth.InvalidProvider). Bumping to nixos-unstable 331800d (HA 2026.5.4, Python 3.14) realigns the toolchain.

HA 2026.3 removed the mireds color_temp parameter from light.turn_on, so the seven color_temp values in light.nix are converted to color_temp_kelvin (250->4000K, 450->2222K).

Held at 2026.5.4, just below 2026.6's removal of legacy template entities (still used here); that migration is tracked separately.
Author
Owner

This was generated by AI while landing a PR.

Validation: PASS

  • Signal relied on: pre-commit dry-build eval (:: fw OK) + local nix build of HA 2026.5.4 with fw's full extraComponents set (OK). The repo gate is eval-only and this PR changes the HA fetchGit src; the host-channel epex_spot customComponent builds against the pinned HA only at deploy — a failure there is safe (fw stays on the prior generation, no DB migration).
  • Conventions: Conventional Commits title; no secrets.yaml/system.stateVersion changes; modules imported by explicit path.
  • Diff: rev 18dd725c -> 331800d (HA 2026.5.4) + 7x color_temp mireds -> color_temp_kelvin in light.nix. Held below 2026.6's legacy-template removal; migration tracked in #137.
  • Mergeable: no conflicts.

Merging on explicit free-text go-ahead.

> *This was generated by AI while landing a PR.* **Validation: PASS** - **Signal relied on:** pre-commit dry-build eval (`:: fw OK`) + local `nix build` of HA 2026.5.4 with fw's full `extraComponents` set (OK). The repo gate is eval-only and this PR changes the HA `fetchGit` src; the host-channel `epex_spot` customComponent builds against the pinned HA only at deploy — a failure there is safe (fw stays on the prior generation, no DB migration). - **Conventions:** Conventional Commits title; no `secrets.yaml`/`system.stateVersion` changes; modules imported by explicit path. - **Diff:** rev 18dd725c -> 331800d (HA 2026.5.4) + 7x color_temp mireds -> color_temp_kelvin in light.nix. Held below 2026.6's legacy-template removal; migration tracked in #137. - **Mergeable:** no conflicts. Merging on explicit free-text go-ahead.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Cloonar/nixos!138
No description provided.