message type switch

Routes incoming messages based on their message type. The message is forwarded through the output connection whose label exactly matches the message type rule node connection label.

Configuration

Field descriptions

There are no available configuration fields.

JSON Schema

1
2
3
4
5
6
7
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "EmptyNodeConfiguration",
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Message processing algorithm

1. Determines the incoming message’s type and looks up its rule node connection label.
2. Routes the message to downstream nodes using the connection with a label that exactly matches the rule node connection label.

Output connections

• Message type connection label
  • Used for all standard message types; the message is routed via the connection whose label corresponds to the specific message type (e.g., Post telemetry, Post attributes, RPC Request from Device)
• Other:
  • If the message type is custom or does not have a specific connection defined.
• Failure:
  • If an unexpected error occurred during message processing.

Predefined connection labels

Examples

Example 1 — Message type is POST_TELEMETRY_REQUEST → routed via Post telemetry

Incoming message

Type: POST_TELEMETRY_REQUEST.

Node configuration

1
{}

Result

Routed via Post telemetry.

Explanation

For POST_TELEMETRY_REQUEST, the rule node connection label is Post telemetry. The node routes the message via the connection with that exact label.

Example 2 — Custom message type → routed via Other

Incoming message

Type: CUSTOM_MESSAGE_TYPE.

Node configuration

1
{}

Result

Routed via Other.

Explanation

Custom message types that don’t have a predefined rule node connection label are routed via the Other connection.