ha-esphome-binding-addlisted

Wires one Home-Assistant-driven value or command into an ESPHome device per spec/ha/esphome-ha-driven-content — choosing the mechanism by the spec's rule (continuously mirrored value → state subscription, one-shot instruction → callable action, person-set value → writable template entity, something HA must learn → event or action back), then emitting the verified configuration for it, always defining what the device does before the first value arrives and while the API connection is down, and routing anything visible through the display's single redraw script. Activate on "show a Home Assistant value on my device", "let an automation tell the device to do X", or equivalent German requests. Do not activate for rendering (ha-esphome-display-author), the voice pipeline (ha-esphome-voice-satellite-add), a local sensor (ha-esphome-config-augment), or HA-side automations (ha-automation-solution).
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA ESPHome Binding Add Spec: `spec/claude/ha-esphome-binding-add/en.md` (EN canonical) / `spec/claude/ha-esphome-binding-add/de.md` (DE translation). Grounding spec: `spec/ha/esphome-ha-driven-content/en.md`; rendering of the resulting values is owned by `spec/ha/esp32-s3-box-display/en.md`. Adds exactly one Home-Assistant-driven binding per invocation, and the mechanism choice is the substance of the run — not the YAML that follows from it. ## Why this is a skill, not an agent - **Mid-flow approval is the contract (decisive):** the mechanism decision (subscription vs. action vs. writable entity vs. return channel) is made *with* the operator against the spec's rule; picking wrong produces a device that polls what it should have been told, or an automation firing into a device with no receiver — and neither fails loudly. - **Quick, targeted change in the current context:** one block in one device file or package, iterated in conversation. - **Counter-dimension considered:** the six documentation pages this spans make the schema lookup self-contained (agent bias), but the boot-state and offline-behaviour decisions belong in the operator's context, not in a report; skill wins. ## When this skill activates The user wants Home Assistant to drive what an ESPHome device shows or does — "der ESPHome-Node soll den Strompreis anzeigen", "HA should be able to tell the box to show a message", "the button press should reach Home Assistant". ## When NOT to activate - how the val