Prerequisites: A device already talking MQTT (ESPHome firmware or Zigbee2MQTT), a local broker, Nodlyn Desktop Studio. No new hardware SKU required — use what you already flash/pair.
Goal: an ESP or Zigbee sensor appears in a Nodlyn workflow within 15 minutes — not as a vendor cloud clone, but as MQTT events you can Dry-Run, alert, and later combine with Modbus or documents.
Path A — ESPHome (Wi‑Fi MQTT)
- Flash ESPHome so the device publishes to your broker (state topics under your prefix).
- In Studio, load template #132 or #262; set the MQTT topic to your ESPHome state topic (or a wildcard like
esphome/#). - Dry-Run → tweak Slack/email → Activate.
Path B — Zigbee2MQTT
- Pair the device in Zigbee2MQTT; confirm messages on
zigbee2mqtt/<friendly_name>. - Point Nodlyn’s MQTT trigger at
zigbee2mqtt/#(or a single device topic). - Optional: use Studio Discovery for network health; device addresses can also be typed in the Inspector.
Path C — Already on Home Assistant
- Keep HA as-is. Share the broker and follow the HA MQTT → Slack bridge (#262).
What “done” looks like
- A message on the Live strip / Slack after a sensor change.
- You understand Nodlyn is the edge workflow layer — industrial protocols and document pipelines sit on the same canvas when you need them.