Entity Type Filter

Use this node to limit processing to specific entity types. For example, you can place it before a node that only works with devices to ensure asset and customer messages take a different path, or combine it with a False output to explicitly handle messages from unexpected entity types.

Configuration

Field	Required	Description
Entity types	Yes	One or more entity types to match against the message originator. At least one must be selected.

Valid entity types include: DEVICE, ASSET, ENTITY_VIEW, CUSTOMER, TENANT, USER, DASHBOARD, RULE_CHAIN, RULE_NODE, EDGE, AI_MODEL, and others.

Message processing algorithm

Check whether the incoming message’s originator entity type is in the configured set.
If it matches, route the message via True.
If it does not match, route the message via False.

Output connections

Connection	Condition
`True`	The originator entity type matches one of the configured types.
`False`	The originator entity type does not match any configured type.
`Failure`	An unexpected error occurred during processing.

Examples

Example 1 — Entity type matches → `True`

Originator entity type: ASSET

{
  "originatorTypes": ["ASSET", "DEVICE"]
}

Result: True — ASSET is in the configured set.

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

Originator entity type: TENANT

{
  "originatorTypes": ["ASSET", "DEVICE"]
}

Result: False — TENANT is not in the configured set.

JSON schema

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