feat(ha): first-party Home Assistant add-on (deploy/homeassistant)

[HuggeK]

Rebased onto current master (v1.4.0 / srcfl/ftw structure). The community
add-on (erikarenhill/ha-addon-forty-two-watts) pinned
ghcr.io/frahlg/forty-two-watts:v1.3.0 and stopped tracking releases after the
Sourceful restructure:

• Canonical image is now ghcr.io/srcfl/ftw; the frahlg path survives only as
  a byte-identical mirror (same manifest digest).
• Runtime binary is /app/ftw; the -config/-web/-drivers/-user-drivers
  interface is unchanged, so the wrapper drives it exactly as before.
• The MPC optimizer, which upstream runs as a separate ftw-optimizer sidecar
  container, is bundled into the add-on image rather than dropped (see below) —
  a single-container add-on can't run a sidecar, so it supervises both processes
  instead.

Adds deploy/homeassistant/ (repository.yaml + ftw/ add-on): an all-in-one
image that bundles the srcfl/ftw:v1.4.0 core with the ftw-optimizer:v1.3.1
Python/CVXPY optimizer in one container. run.sh supervises both — core is the
primary process (its exit code propagates to Supervisor for correct
restart-on-crash), and the optimizer is optional: if it dies, core degrades over
FTW_OPTIMIZER_TRANSPORT=auto (bundled Python worker → in-Go DP planner) instead
of crash-looping the add-on. State lives on Supervisor's /data, the
-user-drivers overlay and host networking are restored, ingress is off (the app
isn't X-Ingress-Path aware), and self-update is off (no updater container).
Version 1.4.0 matches the release line (package.json / release / compose), so
the earlier semver-inversion concern does not apply.

docs/ha-addon.md carries the full findings, storage-growth guidance (Parquet
cold history ~a few GB/year, included in HA backups), and the open-items
checklist (live Supervisor smoke test + publishing the subtree to a root-level
add-on repo remain before release). README gains a Home Assistant add-on install
section.

Claude-Session: https://claude.ai/code/session_01HBjLafzpEYX1dptEE7AGsx

[HuggeK]

Vad tycks @erikarenhill ?

@frahlg om nu ftw-web-sidan skriver om ett HA-addon, vad sägs då om att skapa ett srcfl/ftw-ha-addon eller något liknande namn?

[erikarenhill]

Vad tycks @erikarenhill ?

@frahlg om nu ftw-web-sidan skriver om ett HA-addon, vad sägs då om att skapa ett srcfl/ftw-ha-addon eller något liknande namn?

låter rimligt med en officiell addon, den jag satte upp var mest ett snabbhack 😊

[frahlg]

Packaging decision — 2026-07-22

Recommendation: do not merge this subtree into srcfl/ftw. Put the first-party package in a separate official repository, preferably srcfl/home-assistant-addons if that name is approved.

Home Assistant requires repository.yaml at the Git root, so users cannot add deploy/homeassistant/ to Supervisor. Current Home Assistant guidance also prefers pre-built multi-architecture images. This PR has no image: entry in config.yaml, so its current public path would make each Home Assistant host build the image locally.

Proposed boundary:

• The add-on repo owns repository.yaml, the FTW app manifest, wrapper and process supervision, Home Assistant docs and assets, the add-on image, CI, and releases.
• srcfl/ftw owns the FTW runtime and API. It should contain only a short install link and compatibility notes.
• Add-on install, boot, update, mount, and Supervisor faults go to the add-on repo. FTW runtime and device faults go to the right upstream repo.
• Community support remains best effort with no SLA. Commercial support stays a separate Sourceful service.

Minimum new repo:

repository.yaml
LICENSE
README.md
SUPPORT.md
SECURITY.md
CODEOWNERS
ftw/
  config.yaml
  build.yaml
  Dockerfile
  run.sh
  README.md
  DOCS.md
  CHANGELOG.md
  icon.png
  logo.png
.github/workflows/
  check.yml
  release.yml

The add-on should use its own version, pin a tested Core and Optimizer pair, publish a pre-built amd64/aarch64 image to GHCR, pass a live Home Assistant OS/Supervisor smoke test, publish beta first, and promote the tested artifact to stable.

Keep #620 as a draft source until the new repo gets approval. Then move and adapt the package in a new-repo PR, make a small docs-only FTW PR with the install link, and close #620 as moved. Do not merge this PR as-is.

Current checks pass, but most code checks skip these paths. The PR still lacks a live Supervisor build and boot test.

References: Home Assistant repository rules and publishing guidance.

[frahlg]

bra idé! Jag sätter igång en tråd !

…

On 21 Jul 2026, at 20:06, Erik A ***@***.***> wrote: erikarenhill left a comment (srcfl/ftw#620) <#620 (comment)> Vad tycks @erikarenhill <https://github.com/erikarenhill> ? @frahlg <https://github.com/frahlg> om nu ftw-web-sidan skriver om ett HA-addon, vad sägs då om att skapa ett srcfl/ftw-ha-addon eller något liknande namn? låter rimligt med en officiell addon, den jag satte upp var mest ett snabbhack 😊 — Reply to this email directly, view it on GitHub <#620?email_source=notifications&email_token=ABUQT7SXGXDBWP4WBWGJJI35F6WJFA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBTG42DANJWGYZKM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5037405662>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUQT7TNBJUTGQFSKCP6FMD5F6WJFAVCNFSNUABGKJSXA33TNF2G64TZHMYTEMBYGY3TGMRSHE5US43TOVSTWNBZGM4DIOBXG44DDILWAI>. You are receiving this because you were mentioned.

[frahlg]

Moved to the official Home Assistant repository: https://github.com/srcfl/home-assistant-addons

The usable add-on work from this PR now lives in the new repository and was merged through srcfl/home-assistant-addons#1. The new repository also records the source work and attribution in https://github.com/srcfl/home-assistant-addons/blob/main/ATTRIBUTION.md.

Home Assistant requires repository.yaml at the Git root, so the add-on could not stay under deploy/homeassistant in this repository. I am closing this PR as moved. A small FTW docs PR will add the official repository link and current beta status. No add-on beta or stable image has been published yet.