Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.
© 2026 The ThingsBoard Authors
180 Try for free Menu

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

North America Data stored in North America Europe Data stored in the European Union

Rather run it yourself? Install on your own servers

Push Edge Data to Cloud

ThingsBoard Edge stores telemetry and attributes locally and synchronizes them to the ThingsBoard Server through Push to cloud rule nodes in the Edge rule chain. This recipe covers the default behavior and how to forward only part of the data.

Default behavior

Section titled “Default behavior”

The built-in Edge root rule chain already forwards device data to the server through Push to cloud nodes. Unless you have modified the root rule chain:

  • Post telemetry messages go through Save Timeseries to Push to cloud.
  • Post attributes messages (client-side attributes published by devices) go through Save Client Attributes to Push to cloud. The server saves them as server attributes, because the node’s Attributes scope is Server attributes.
  • Attributes Updated and Attributes Deleted messages go straight to Push to cloud.

To change the attribute scope that Push to cloud sends, see Attribute synchronization. To push attribute changes from the server to the Edge, see Attributes.

Push only a subset of data

Section titled “Push only a subset of data”

To forward only specific message types or device groups to the server:

  1. Add a filter node, for example script or device profile switch, before the Push to cloud node.
  2. Route only matching messages to Push to cloud; let everything else pass through without forwarding.
  3. Click Apply changes.

For the full configuration reference and available node settings, see Telemetry synchronization.