← ClaudeAtlas

ha-bluetooth-augmentlisted

Augments an existing Home Assistant Custom Integration with Bluetooth support, conforming to spec/ha/bluetooth. Sets the manifest bluetooth matcher list plus the bluetooth_adapters dependency, subscribes to advertisements via bluetooth.async_register_callback with an explicit scanning mode bound through entry.async_on_unload, picks the right Bluetooth coordinator family (passive/active processor or DataUpdate variants), and wires device/service-info lookups over the shared scanner. Keeps passive (connectable=False) as the default. Part of the Gold discovery family, sibling of ha-discovery-augment. Activate on "add bluetooth discovery/support", "listen for BLE advertisements", or equivalent German requests. Do not activate for DHCP/SSDP/USB/HomeKit/Zeroconf discovery (ha-discovery-augment), the config-flow discovery step (ha-config-flow-augment), the generic polling coordinator (ha/coordinator-patterns), greenfield scaffolding (ha-integration-scaffold), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68
Install: claude install-skill nolte/claude-home-assistant
# HA Bluetooth Augment Spec: `spec/claude/ha-bluetooth-augment/en.md` (EN canonical) / `spec/claude/ha-bluetooth-augment/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes how the device advertises and reads back the manifest matcher, the callback registration, the coordinator family, and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (`ha-discovery-augment`, `ha-config-flow-augment`, `ha-coordinator-add`). - **Mid-flow interactivity** — the passive-vs-connectable decision, the coordinator-family choice, and the network-discovery redirect are per-run dialogues the user approves before generation. - **Bounded, inline generation** — the manifest matcher plus the callback registration and the coordinator wiring fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the connectable decision and the trade-off advice belong in the user's working context; skill wins. ## When this skill activates Use this skill to add Bluetooth support — central BLE discovery plus advertisement-driven data fetching — to an existing integration, typically for a device that delivers its data over BLE advertisements (the passive default) or needs an occasional active connection. ## When NOT to activate - DHCP/SSDP/USB/HomeKit/Zeroconf network or bus discovery → `ha-discovery-augment` / `ha/disc