Home Assistant / MQTT integration (spec §16.2) #12

Open
opened 2026-07-07 16:52:05 +00:00 by claude-bot · 0 comments
Contributor

Goal

Publish active scheme + event metadata to MQTT on each push so Home Assistant (or any subscriber) can react, with an optional inbound override command.

Design (from spec §16.2)

  • Use the aiomqtt async library.
  • Topics:
    • iris/state — current scheme JSON (retained, so HA gets current state on reconnect)
    • iris/event — current event metadata
    • iris/command — inbound manual-override commands
  • Broker dependency (Mosquitto or similar), env-gated and disabled by default.

Why it was deferred

Adds a broker dependency and bidirectional message handling. The v1 outbound webhook system already covers the most common HA use case (triggering automations on push events).

Acceptance criteria

  • Scheme push publishes retained iris/state + iris/event
  • Inbound iris/command override handled safely
  • Feature env-gated, off by default
  • Tests with a mock broker

Deferred v2 item carried over from the spec.

## Goal Publish active scheme + event metadata to MQTT on each push so Home Assistant (or any subscriber) can react, with an optional inbound override command. ## Design (from spec §16.2) - Use the `aiomqtt` async library. - Topics: - `iris/state` — current scheme JSON (**retained**, so HA gets current state on reconnect) - `iris/event` — current event metadata - `iris/command` — inbound manual-override commands - Broker dependency (Mosquitto or similar), env-gated and disabled by default. ## Why it was deferred Adds a broker dependency and bidirectional message handling. The v1 outbound webhook system already covers the most common HA use case (triggering automations on push events). ## Acceptance criteria - [ ] Scheme push publishes retained `iris/state` + `iris/event` - [ ] Inbound `iris/command` override handled safely - [ ] Feature env-gated, off by default - [ ] Tests with a mock broker Deferred v2 item carried over from the spec.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rbrooks/Iris-WLED#12
No description provided.