fix(hass): register the Honeywell fan package so its dashboard buttons work #215

Merged

kblack0610 merged 1 commit from fix/honeywell-package-register into master

2026-09-01 19:44:06 +00:00

kblack0610 commented

2026-09-01 19:43:44 +00:00

Owner

Follow-up to #210, which I shipped broken.

config/packages/honeywell_fan.yaml was never added to the explicit configMapGenerator file list, so it never reached the cluster. Nothing catches this: kustomize build succeeds (an unreferenced file is not an error, merely not an input), Flux applies, HA starts healthy. The only symptom is three wall-tablet buttons calling script.honeywell_fan_* that silently do nothing.

Caught by querying live HA for the entities it should have created: 0 honeywell entities while the manifests looked complete. The original commit had this defect from day one in 2026-07-09 - the explicit file list already existed then - which is plausibly why the branch was abandoned unmerged.

Also adds scripts/check-ha-packages.py to the existing checks workflow, matching that workflow`s stated purpose (assert facts that span two files). Negative control run before trusting it:

with fix:       ok: all 17 package files are registered      exit 0
line removed:   FAIL: config/packages/honeywell_fan.yaml ... exit 1
restored:       ok: all 17 ...                              exit 0

Follow-up to #210, which I shipped broken. `config/packages/honeywell_fan.yaml` was never added to the explicit `configMapGenerator` file list, so it never reached the cluster. Nothing catches this: `kustomize build` succeeds (an unreferenced file is not an error, merely not an input), Flux applies, HA starts healthy. The only symptom is three wall-tablet buttons calling `script.honeywell_fan_*` that silently do nothing. Caught by querying live HA for the entities it should have created: **0 honeywell entities** while the manifests looked complete. The original commit had this defect from day one in 2026-07-09 - the explicit file list already existed then - which is plausibly why the branch was abandoned unmerged. Also adds `scripts/check-ha-packages.py` to the existing checks workflow, matching that workflow`s stated purpose (assert facts that span two files). Negative control run before trusting it: ``` with fix: ok: all 17 package files are registered exit 0 line removed: FAIL: config/packages/honeywell_fan.yaml ... exit 1 restored: ok: all 17 ... exit 0 ```

kblack0610 added 1 commit

2026-09-01 19:43:44 +00:00

fix(hass): register the Honeywell fan package so its dashboard buttons work

checks / fleet-roster (pull_request) Successful in 6s

Details

checks / kustomize-builds (pull_request) Successful in 7s

Details

6c1fa38cbe

b41a897 added config/packages/honeywell_fan.yaml, the IR tooling, and three
wall-dashboard buttons, but never added the package to the configMapGenerator
file list in kustomization.yaml. The file therefore never reached the cluster:
kustomize build succeeds (an unreferenced file is not an error, just not an
input), Flux applies, HA starts healthy, and the only symptom is three buttons
on a wall tablet that call script.honeywell_fan_* and do nothing.

It shipped that way in #210 and was caught by querying the live HA API for the
entities it should have created - the cluster reported zero honeywell entities
while the manifests looked complete.

Adds scripts/check-ha-packages.py to the existing checks workflow so the next
one fails in CI instead of on a tablet. Verified it fails on this exact bug
before trusting it: removing the line reports 1 of 17 unregistered, exit 1.