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

14 results

Tank Fill Percentage from Depth Sensor

Calculate Delta from Pulse Counter

Calculate Delta from Tank Level Sensor

Pump Status from Relay, Flow and Pressure

Utilization / Progress Percentage

Sync GPS Position from Tracker to Vehicle or Container

Daily Energy Consumption Total

Active Device Count Per Site

Manufacturing Plant Output Per 8-Hour Shift

GPS Tracker Geofencing — Entry, Exit, Presence

Calculate Power from Voltage and Current

Hourly Temperature KPIs (Min, Max, Average)

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.

Contribute a Calculated Field Read the contribution guide

Frequently Asked Questions

What are calculated fields?

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.

Are they compatible with all ThingsBoard editions?

Available in CE, PE, and Cloud since v4.0. Data reprocessing (historical recalculation) is PE-only. Each library entry displays edition badges and minimum version requirements.

How do I import a calculated field?

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.

Can I customize calculated fields after importing?

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.

What types of calculated fields are supported?

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).

Difference between Simple and Script?

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.

Can calculated fields be chained?

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

How do use-case tags work?

Each calculated field is tagged with shared IoT use cases, so browsing by a use case surfaces matching fields, devices, dashboards, 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.

How do I contribute?

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

Are they free to use?

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