Push to Cloud

Use this node on an Edge instance to selectively push data up to the cloud — for example, forwarding critical telemetry values or alarm events while keeping routine sensor readings local, or synchronising attribute updates to the cloud only after local validation.

Configuration

Attributes scope — required. Default attribute scope used for attribute-related messages (SERVER_SCOPE, CLIENT_SCOPE, or SHARED_SCOPE). Can be overridden per message by including a scope key in the message metadata.

Supported message types

Message type	Description
`POST_TELEMETRY_REQUEST`	Time-series data
`TIMESERIES_UPDATED`	Time-series update
`POST_ATTRIBUTES_REQUEST`	Attribute post
`ATTRIBUTES_UPDATED`	Attribute update
`ATTRIBUTES_DELETED`	Attribute deletion

Message processing algorithm

Verify that the message type is supported. If not, route via Failure.
Convert the message into a cloud event based on the message type.
Write the cloud event to persistent storage (local cloud queue).
Route via Success.

Output connections

Connection	Condition
`Success`	Cloud event written to persistent storage. Outgoing message is unchanged.
`Failure`	Unsupported message type or unexpected error.

Examples

Example 1 — Push telemetry to cloud

Originator: DEVICE | Type: POST_TELEMETRY_REQUEST.

{
  "temperature": 22.5,
  "humidity": 65.3
}

{
  "scope": "SERVER_SCOPE"
}

Result: cloud event queued; edge synchronisation service will deliver it to the cloud. Routes via Success.

JSON schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "TbMsgPushToCloudNodeConfiguration",
  "type": "object",
  "required": ["scope"],
  "additionalProperties": false,
  "properties": {
    "scope": {
      "type": "string",
      "enum": ["SERVER_SCOPE", "CLIENT_SCOPE", "SHARED_SCOPE"],
      "description": "Default attribute scope for attribute-related messages."
    }
  }
}