homematiclisted

# Homematic Use this skill for Homematic IP Home Control Unit (HCU) state inspection and guarded smart-home control planning. The primary v1 integration target is the official Homematic IP Connect API, which exposes HCU plugin communication over WebSocket. Treat CCU/RaspberryMatic and Homematic IP Access Point cloud support as separate compatibility paths until their protocols are implemented and tested. This v1 targets remote HCU Connect API clients. The HTTPS port `6969` auth helpers implement the remote-client enrollment flow. Installed HCU plugin containers instead receive their token from the HCU container environment and mounted `/TOKEN` file; this helper does not implement container installation. ## Safety Rules 1. Start with `plan`, `summarize-fixture`, `plugin-ready`, `get-state`, or `get-system-state`. 2. For HCU setup, generate gateway `http-request` payloads with the helper. Never ask the operator to paste activation keys or auth tokens into chat. 3. For HCU WebSocket operations, use helper `websocket-message` output as the source of truth for connection headers, message type, path, stakes tier, and approval requirement. 4. For a local operator-owned read-only smoke test, `run-websocket` can open the HCU WebSocket directly using `HOMEMATIC_HCU_AUTH_TOKEN` from the helper environment. Do not pass that token as an argument. Use gateway-managed execution for any amber/red operation. 5. Reads are green but still privacy-sensitive because home