Does Nodlyn support WebSocket?

Compatibility answer

Yes — at the protocol level. Nodlyn ships WebSocket blocks in the connector library; you point them at your host or broker.

Configure the WebSocket client node with your endpoint URL.

What WebSocket support means in Nodlyn

WebSocket nodes connect to live duplex feeds — custom device bridges, push APIs, market-style streams — then branch on message content. There is no LAN “WebSocket discovery”; you configure the URL.

When the vendor offers both REST and a socket feed, use HTTP for commands and WebSocket for push. Setup patterns are in the WebSocket blog guide.

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 WebSocket

• Live feed → branch on payload
• Device bridge push → alert
• Hybrid: WS events + HTTP commands

Quick start for WebSocket

1. Add WebSocket Send / Fetch nodes.
2. Connect to your stream URL.
3. Parse messages and branch on conditions.
4. Combine with timers or webhooks for hybrid flows.

Brands people ask about for WebSocket

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

• Custom WebSocket APIs

Do I need discovery for WebSocket?

No. Configure the WebSocket client node with your endpoint URL. Discovery is optional for protocols that use a known URL, broker, or PLC address.

In-depth WebSocket guide (blog)

For configuration details, examples, and troubleshooting, use the long-form guide — that URL is the primary “how to” page: WebSocket Client Automation.

Related protocols