Asset Profile Switch

Use this node to route messages to different downstream paths based on the originator asset’s profile name — for example, applying different alarm thresholds to HVAC assets versus Temperature Sensor assets. The originator must be an ASSET; any other entity type results in Failure.

This node has no configuration options. The connection label used for routing is determined entirely at runtime from the asset profile name.

1. Check that the message originator entity type is ASSET. If not, route via Failure.
2. Fetch the asset’s profile from the database to retrieve its name. If the profile is not found (e.g., the asset was deleted while the message was queued), route via Failure.
3. Route the message via a connection whose label exactly matches the fetched profile name.

State: originator is an asset with profile name Boiler Room.

Result: message routed via Boiler Room.

State: originator entity type is DEVICE.

Result: message routed via Failure — asset profile switch requires an ASSET originator.

State: originator entity type is ASSET, but the asset no longer exists.

Result: message routed via Failure — profile cannot be fetched.

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