Message Type Switch

Use this node to fan out processing based on message type without writing any code. Each standard message type maps to a human-readable connection label (e.g., POST_TELEMETRY_REQUEST → Post telemetry), so you can wire different downstream paths for telemetry, attribute updates, RPC calls, lifecycle events, and more. Custom or unknown types are routed via Other.

See the message types reference for the full list of built-in types.

This node requires no configuration.

1. Determine the incoming message type and look up its rule node connection label.
2. Route the message via the connection whose label exactly matches the rule node connection label.
3. If the message type is custom or has no predefined label, route via Other.

A telemetry message arrives. The node looks up the connection label for POST_TELEMETRY_REQUEST and routes via Post telemetry.

A message with type CUSTOM_MESSAGE_TYPE arrives. No predefined label exists, so the node routes via Other.

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "EmptyNodeConfiguration",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}