The value of smart hardware appears when it joins an open automation graph. That means bridges: auth, discovery, commands, and realtime state.
Most production pain is idle timeouts and bad entity modeling — not the first power-on command.
Realtime is an ops problem
WebSocket heartbeats prevent proxy 1006 deaths. MQTT remains the right fan-out for device events.
Ship debug dumps and raw event streams for field support.
Entities beat devices
Multi-channel hardware must become multiple entities. Home Assistant users automate switches, not opaque blobs.
Takeaways
- Automations need entities, not vendor screens.
- Heartbeat your control sessions.
- Debug tooling is part of the bridge.