Before you can automate a device, you need to find it. Nodlyn Discovery scans your network, smart-home mesh, and industrial buses — then presents every compatible device in a unified list you can register and use in workflows.
Quick reference (Inspector-aligned): Device Discovery in the Knowledge Base. This article goes deeper — intent UX, protocol tables, and field stories.
No manual JSON editing. No guessing IP addresses. Pick an intent (smart home, Bluetooth, CAN Bus…), run a scan, accept the devices you want, and start building automations on the canvas.
Discovery is read-only and safe: it observes devices but never sends control commands until you explicitly accept a device and run a workflow.
Why Discovery Matters for Visual Automation
Traditional integration platforms assume you already know endpoint URLs and API keys. IoT and edge projects don't work that way — devices appear on Wi-Fi, Thread, USB serial, MQTT bridges, or CAN interfaces. Nodlyn closes that gap with protocol-native probes and automatic connector mapping.
- Find — scan by protocol or intent
- Identify — friendly names, signal strength, semantic profiles (smart bulb, sensor, PLC…)
- Register — accept into the device registry with one click
- Automate — drag device nodes onto workflows or let Discovery add them for you
Intent-Based Discovery UX
Studio groups protocols into intents so non-experts don't need to memorise acronyms:
| Intent | What it finds | Protocols used |
|---|---|---|
| Smart devices in your home | Lights, sensors, plugs, thermostats, door contacts | Matter, Zigbee, Z-Wave |
| Nearby Bluetooth | BLE sensors, trackers, wearables | Bluetooth LE |
| Online services & APIs | MQTT brokers, HTTP endpoints, CoAP devices, Azure IoT Hub | HTTP, MQTT, CoAP, IoT Hub |
| Printers & document devices | Network and USB printers, scanners | Printer, mDNS, SSDP |
| CAN Bus & automotive | Vehicle ECUs, industrial controllers | CAN Bus (SocketCAN) |
| Advanced / all protocols | Full probe suite including mDNS, Tuya UDP, serial | All registered probes |
Supported Protocols at a Glance
Nodlyn registers dedicated discovery probes for each major transport:
- Matter — IP-based smart home standard (Wi-Fi & Thread)
- Zigbee — via Zigbee2MQTT bridge
- Z-Wave — via Z-Wave JS UI
- CAN Bus — SocketCAN interfaces (
can0,vcan0) - MQTT — Homie, Home Assistant, Tasmota, ESPHome discovery
- mDNS / DNS-SD — Bonjour services on the LAN
- SSDP / UPnP — media devices, gateways, some IoT hubs
- Bluetooth LE — nearby GATT devices
- HTTP — subnet sweep for REST endpoints
- CoAP — constrained IoT sensors
- Tuya UDP — local LAN discovery for Tuya/Smart Life devices
- Serial / USB — COM ports and USB adapters
- Printers — IPP, JetDirect, vendor-specific discovery
Matter Discovery
Matter is the industry-backed standard for interoperable smart home devices. Nodlyn's Matter probe discovers commissionable and operational nodes on your local network using mDNS — the same mechanism Matter uses for device advertisement.
Supported configuration options include:
- mDNS multicast address and port
- Thread discovery (optional) for Thread-border-router setups
- OTBR REST URL for OpenThread Border Router integration
Typical devices: smart plugs, lights, door locks, sensors, and thermostats from Matter-certified brands — one protocol instead of dozens of vendor apps.
Zigbee Discovery
Zigbee devices communicate through a low-power mesh. Nodlyn integrates with Zigbee2MQTT — the most popular open-source bridge — to discover every paired device on your coordinator.
First-time smart-home setup in Nodlyn:
- Ensure Zigbee2MQTT is running (Studio checks MQTT bridge reachability on localhost)
- Select the Smart home intent
- Run discovery — devices appear with model, IEEE address, and link quality metadata
- Accept a device → it maps to the Zigbee connector automatically
From there, build workflows that read sensors, toggle switches, or react to MQTT events. See our Zigbee automation guide for workflow examples.
Z-Wave Discovery
Z-Wave remains the protocol of choice for many installed smart-home systems (locks, sensors, switches). Nodlyn discovers nodes through Z-Wave JS UI, listing every included node with its home ID, security class, and endpoint information.
After acceptance, use the Z-Wave connector in workflows to get values, set configurations, and trigger scenes — all from the same visual canvas as your business automations.
CAN Bus Discovery
Industrial and automotive projects speak CAN. Nodlyn's CAN Bus probe listens passively on Linux SocketCAN interfaces (can0, vcan0) and reports active buses — ideal for factory floors, test benches, and vehicle telemetry prototypes.
Configuration highlights:
- Interface name selection
- Passive listen duration
- Simulation mode for development without hardware
Pair discovered CAN interfaces with the CAN Bus connector to read frames, decode signals, and trigger alerts — or combine with the AI Workflow Assistant to draft monitoring flows in plain English.
Device Types & Automatic Profiles
Discovery doesn't just return addresses — Nodlyn maps devices to semantic profiles when possible:
- Smart bulbs, plugs, and switches
- Temperature, humidity, and motion sensors
- Energy meters and smart plugs with power monitoring
- ESPHome and Tasmota firmware devices
- HomeKit-advertised accessories
- Network printers (HP, Epson, Brother, Zebra…)
- Generic MQTT sensors via topic heuristics
Each accepted device gets a suggested connector ID and optional firmware adapter (e.g. Tasmota MQTT, ESPHome API) so your first workflow node is already compatible.
From Discovery to Workflow
- Open the Discover tab in Nodlyn Studio
- Choose an intent or select protocols manually (Advanced)
- Configure protocol options (MQTT broker, CAN interface, mDNS service types…)
- Click Start scan — results stream in via SignalR in real time
- Click Accept on a device to register it
- Optionally Add to workflow — Discovery drops a device node on the canvas
- Connect triggers, conditions, and actions; validate and deploy
You can also ask the AI Assistant to "Start discovery scan" (on-prem) without leaving the chat panel.
Security & Privacy
- Observational scans only — no writes, pairing, or firmware changes during discovery
- Explicit acceptance — nothing enters your device registry until you confirm
- Local-first — scans run on your Studio machine or edge runtime, not on a shared cloud scanner
- Operator role required — discovery REST endpoints require authenticated sessions
Discovery vs Manual Device Setup
| Discovery | Manual entry | |
|---|---|---|
| Time to first device | Minutes | Per-device configuration |
| Finds unknown IPs | ✓ | — |
| Multi-protocol scan | ✓ | One at a time |
| Profile & connector hints | ✓ | Manual research |
| Best for | IoT, smart home, lab benches | Known API endpoints |
Who Is This For?
- Smart home enthusiasts — unify Matter, Zigbee, and Z-Wave on one automation canvas
- IoT developers — prototype MQTT and CoAP integrations faster
- Industrial teams — bring CAN Bus signals into the same tool as ERP and approval workflows
- MSPs & integrators — document customer devices during site surveys
- Makers & educators — discover ESPHome/Tasmota nodes on a classroom network
Getting Started
- Download Nodlyn Studio (Windows desktop beta)
- For Zigbee: install Zigbee2MQTT and connect your coordinator
- For Z-Wave: run Z-Wave JS UI
- For Matter: ensure devices are on the same LAN (or Thread via OTBR)
- For CAN: configure SocketCAN on Linux (
ip link set can0 up) - Open Discover → pick your intent → scan → accept → automate
What's Next?
Combine Discovery with Nodlyn's 350+ connectors and 246+ templates: discover a temperature sensor, drop it on the canvas, and use the AI Assistant to add Slack alerts and approval gates — all without leaving local-first Studio.
Discovery is included in the Nodlyn free beta. Install Studio, open the Discover tab, and scan your first network in under five minutes.