Message Type Filter

The simplest way to split rule chain processing by message type. Place it right after the chain’s input node to route telemetry, attribute updates, RPC requests, and other message types to separate processing branches — without writing any script.

See Message Types for the complete list of built-in types.

Configuration

Field	Required	Description
Select message types	Yes	A set of message types to check against; at least one must be specified. The message is routed `True` if its type is in this set.

Message processing algorithm

Determine the incoming message type.
Check whether the type is in the configured set.
- If it is, route the message to downstream nodes via True.
- If it is not, route the message to downstream nodes via False.

Output connections

Connection	Condition
`True`	Incoming message type matches any of the configured types
`False`	Incoming message type does not match any of the configured types
`Failure`	Unexpected error during processing

Examples

Example 1 — Message type matches → `True`

Incoming message: type is POST_TELEMETRY_REQUEST.

Node configuration:

{
  "messageTypes": [
    "POST_TELEMETRY_REQUEST",
    "POST_ATTRIBUTES_REQUEST"
  ]
}

Result: routed via True — the message type is in the configured set.

Example 2 — Message type does not match → `False`

Incoming message: type is POST_TELEMETRY_REQUEST.

Node configuration:

{
  "messageTypes": [
    "POST_ATTRIBUTES_REQUEST",
    "TO_SERVER_RPC_REQUEST"
  ]
}

Result: routed via False — the message type is not in the configured set.

JSON schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TbMsgTypeFilterNodeConfiguration",
  "type": "object",
  "required": ["messageTypes"],
  "additionalProperties": false,
  "properties": {
    "messageTypes": {
      "description": "Non-empty set of message types to check against.",
      "type": "array",
      "items": { "type": "string" },
      "uniqueItems": true,
      "minItems": 1
    }
  }
}

Was this helpful?