Prerequisites: Mosquitto (or another broker) shared with Home Assistant and/or Zigbee2MQTT; Slack incoming webhook; Nodlyn Desktop Studio on the same LAN.
Home Assistant for the home. Nodlyn for edge workflows. This bridge keeps your HA MQTT topics and adds visual alerts, Dry-Run, and (later) industrial or document steps on the same canvas.
What this template does
- HA / Z2M MQTT — subscribes to
zigbee2mqtt/#by default (typical HA + Zigbee2MQTT stack). Switch tohomeassistant/#for HA MQTT Statestream/discovery. - Notify Slack — posts topic + payload to
#ha-bridge(placeholders{{topic}}/{{payload}}are resolved at run time).
Step 1 — Share one broker
- Confirm HA (or Zigbee2MQTT) publishes to the same broker Nodlyn will use (often
localhost:1883on a Pi or NAS). - If the broker requires auth, note username/password for Studio.
Step 2 — Load template #262
- Open Studio → Templates (or empty-canvas recipe When HA / Zigbee publishes…).
- Search
Home Assistant MQTTand load template #262.
Step 3 — Topic filter
- Default topic
zigbee2mqtt/#— narrow to a device (e.g.zigbee2mqtt/living_room) once traffic looks right. For HA Statestream usehomeassistant/#. - Set broker host/credentials on the MQTT trigger node.
Step 4 — Slack + Dry-Run
- Paste a Slack incoming webhook URL; adjust channel/message.
- Use 🧪 Dry-Run first, then Activate on-prem. Watch the Live strip and Activity tab.
Why not “replace HA”?
Nodlyn is the workflow layer next to HA: approvals, PLC/Modbus, invoices, and exportable runtime agents. Keep HA for Lovelace and home entities; bridge the events you care about into Nodlyn.