related Device attributes
Node finds Related Device of the Message Originator entity using configured query and adds Attributes (client\shared\server scope) and Latest Telemetry value into Message Metadata.
Attributes are added into metadata with scope prefix:
shared attribute ->
shared_client attribute ->
cs_server attribute ->
ss_telemetry -> no prefix used
For example, shared attribute ‘version’ will be added into Metadata with the name ‘shared_version’. Client attributes will use ‘cs_’ prefix. Server attributes use ‘ss_’ prefix. Latest telemetry value added into Message Metadata as is, without prefix.
In ‘Device relations query’ configuration Administrator can select required Direction and relation depth level. Also Relation type can be configured with required set of Device types.
If multiple Related Entities were found, only the first Entity is used for attributes enrichment, other entities will be discarded.
Failure chain is used if no Related Entity was found, otherwise - Success chain.
If attribute or telemetry was not found, it is not added into Message Metadata and still routed via Success chain.
Outbound Message Metadata will contain configured attributes only if they exist.
To access fetched attributes in other nodes you can use this template ‘metadata.temperature’
Note: the rule node has the ability to enable/disable reporting Failure if at least one selected key doesn’t exist in the outbound message.
Last updated
