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 and how they find the site, so we can improve it (Google Analytics).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, 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
Try for free

ThingsBoard Cloud

Choose your data region

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

Rather run it yourself? Install on your own servers

IoT Calculated Fields

Install ready-made formulas in one click — turn raw telemetry into the metrics you monitor, like fuel efficiency or power factor, without building the logic by hand.

Contribute
Calculated Fields illustration

27 results

Items per page:

Share Your Calculated Field with the Community

Built a useful data transformation? Export it as a JSON from ThingsBoard and publish it to the IoT Hub. Share it with thousands of ThingsBoard developers worldwide.

Frequently Asked Questions

Calculated fields are server-side data transformations that run automatically when new data arrives. They combine telemetry, attributes, or historical data into derived values, stored as new time series or attributes. Introduced in ThingsBoard 4.0, they simplify logic that previously lived in rule chains.

Click Install on the calculated field’s page and pick the target — a device, asset, or device/asset profile — in the install dialog. The field is created on that target and immediately starts computing from live telemetry, saving the result as a new time series key or attribute. You can also download the JSON and import it manually from the Calculated Fields tab.

Yes. Modify title, arguments, expression/script, output config. For Script types, use the built-in Test Function mode to validate with real data before saving.

Six types: Simple (arithmetic expressions), Script (TBEL logic), Geofencing (zone enter/exit detection), Propagation (forwarding values up or down the entity hierarchy), Related Entities Aggregation (rolling up telemetry across related entities), and Entity Aggregation (aggregating across all entities of a profile, e.g. fleet-wide totals).

Simple uses basic arithmetic and standard math functions. Script uses TBEL for complex logic with conditionals, loops, and multi-value output — ideal for tiered pricing, state machines, or custom aggregation.

Yes. Output of one CF can trigger another, enabling multi-step processing pipelines.

Each calculated field is tagged with shared IoT use cases, so browsing by a use case surfaces matching fields, devices, and widgets together. Popular use cases for calculated fields include Asset Tracking, Environment Monitoring, Fleet Tracking, Industrial Automation, Predictive Maintenance, Smart Building, and Smart City; the full marketplace vocabulary is searchable in the Use Case filter.

Check the IoT Calculated Field Contribution Guide that describes the process of adding calculation fields. You can also contact us or email iothub@thingsboard.io for help.

All community-contributed CFs are currently free. Licensing terms displayed on each page. Commercial listings may come in a future phase.