Does Nodlyn support HTTP / REST?

Compatibility answer

Yes — at the protocol level. Nodlyn can discover HTTP / REST endpoints and register them for visual workflows.

HTTP discovery can probe a subnet for open web servers; many devices also work with a manual base URL.

What HTTP / REST support means in Nodlyn

HTTP/REST covers local device APIs (Shelly, Hue bridge) and any SaaS webhook. Discovery can probe open web ports on a subnet, or you paste a base URL into an HTTP Request node and parse JSON.

If a device only documents a REST API and no Modbus/MQTT, this is usually the right compatibility path. Pair with WebSocket when the vendor pushes a live stream instead of poll/response.

This page is a compatibility check (supported or not, how you connect). Step-by-step tutorials live on the blog when linked below — so Google (and readers) get one clear “how-to” URL.

Example automations with HTTP / REST

• Shelly switch → webhook chain
• Hue local API → scene
• SaaS webhook → ticket

Quick start for HTTP / REST

1. Use Discovery → Online services, or drop an HTTP Request node.
2. Enter URL / subnet and method.
3. Parse JSON with Transform or field paths.
4. Great for Shelly, Hue local API, and any SaaS webhook.

Brands people ask about for HTTP / REST

Curated examples — not an exhaustive SKU database. Same protocol family usually wires the same way. Missing model? Request confirmation on /protocols.

• Shelly
• Philips Hue Bridge
• Home Assistant REST

Can Nodlyn auto-discover HTTP / REST devices?

Yes. HTTP discovery can probe a subnet for open web servers; many devices also work with a manual base URL. You can also add endpoints manually if discovery is empty.

In-depth HTTP / REST guide (blog)

For configuration details, examples, and troubleshooting, use the long-form guide — that URL is the primary “how to” page: Industrial Protocols Hub: Modbus to OPC UA.

Related protocols