IoT Solutions

Smart Building

Run climate, air quality, access and occupancy on one platform for every building

Talk to us
  • Indoor air quality
  • HVAC energy savings
  • Space utilization
  • Legionella compliance

Applications

What you can build

The projects teams in the sector deliver most often once their devices are connected.

  • Air quality

    Monitor CO2, particulates and ventilation in every room, and act before air quality affects the people inside.

  • Climate control

    Drive HVAC from real occupancy and temperature data instead of fixed schedules, cutting energy waste.

  • Occupancy monitoring

    Count people in meeting rooms, desks and common areas with anonymized sensors that respect privacy.

  • Access control

    Manage doors, zones and schedules centrally, with per-user permissions for staff, tenants and visitors.

  • Energy metering

    Meter electricity and water per floor or tenant, and spot anomalies from live dashboards.

  • Facility alerts

    Get notified about leaks, equipment faults and out-of-range conditions the moment sensors detect them.

Why it matters

Conditioning rooms nobody is using

A timetable heats every floor whether anyone is in or not. Room sensors let the building react to the people actually inside.

Without data

All day

heating half empty floors

  1. 07:00Air handling starts on every floor, as scheduled
  2. 11:00Floor 3 is half empty; it is heated anyway
  3. 16:00Room 2B complains it is stuffy; nobody knows why

With Thinger.io

1 min

from reading to adjustment

  1. 07:00Occupancy sensors put floor 3 at 20%
  2. 07:01Floor 3 drops to its setback temperature
  3. 14:20CO₂ in room 2B passes 1000 ppm; ventilation steps up

In the field

The whole building in one view

HVAC units, occupancy and air quality sensors and the hot water boiler report to one place, so facility teams run every floor from the same screen.

Building instrumentation

What gets connected

What facility teams actually install in real buildings, with the ranges and output signals you already work with.

Instrument catalogue · Smart buildingsSHEET IB-01 · REV A · N.T.S.
AT-201Indoor air quality sensorFIG. 01

Tells you when the air in a room goes stale before the people inside feel it, and lets ventilation run only where it is needed.

Measures
CO2 (NDIR) · temp · RH · TVOC
Range
CO2 400-5,000 ppm · ±(30 ppm + 3%)
Output
LoRaWAN · Modbus RTU variants
Install
Offices, meeting rooms, classrooms
OS-112Occupancy sensorFIG. 02

Shows which rooms and desks are actually used, so cleaning, climate and floor space follow real occupancy instead of the booking calendar.

Measures
Presence · people count · desk use
Range
PIR lens, ~94° field · anonymized
Output
LoRaWAN · battery 5+ years
Install
Meeting rooms, desks, common areas
JT-301Three-phase energy meterFIG. 03

Splits the electricity bill into causes: which floor, which tenant, which machine, and flags loads that keep running out of hours.

Measures
kWh · kW · V · A · PF per phase
Range
Direct 65 A or CT /5 A · Class 1 / MID B
Output
Modbus RTU · M-Bus · pulse
Install
Main boards, floor panels, tenant submeters
TT-405DHW temperature probeFIG. 04

Keeps the anti-Legionella log for you: storage at 60 °C, returns above 50 °C, every reading time-stamped for the auditor.

Measures
DHW tank · return · outlet temp °C
Range
PT1000 Class A · -50 to 200 °C · ±0.15 °C
Output
4-20 mA · Modbus RTU · LoRaWAN
Install
Calorifiers, return loops, sentinel taps
HM-502Thermal energy meterFIG. 05

Measures the heat each circuit or tenant really takes from the plant, the number both fair billing and HVAC tuning depend on.

Measures
Heating / cooling energy · flow · ΔT
Range
qp 0.6-15 m³/h · ΔT 3-178 K · EN 1434 Cl. 2
Output
M-Bus · wireless M-Bus · Modbus · LoRaWAN
Install
Substations, HVAC circuits, tenant billing
LS-610Water leak detectorFIG. 06

Catches the drip under a chiller or a ceiling void early, and can close a motorized valve before water reaches anything expensive.

Measures
Water presence on floor or in tray
Range
Point probe · sensing cable runs
Output
LoRaWAN · relay to motorized valve
Install
Plant rooms, AHU trays, server rooms
GW-01Building LoRaWAN gatewayFIG. 07

The building's radio backbone: one box in a riser hears every battery sensor on this sheet and forwards their data to the platform.

Radio
LoRaWAN EU868 · 8 channels · 1,000+ nodes
Coverage
Several floors per indoor gateway
Backhaul
Ethernet · Wi-Fi · LTE
Install
Risers, plant rooms, rooftops
Field signals acceptedLORAWAN · MODBUS RTU · BACNET/IP · M-BUS · 4-20 MA · PULSE
Integration Every interface on this sheet lands in thinger.io through LoRaWAN servers, Node-RED gateways or native device connections.
IB-01 · REV A · N.T.S.

THE BUILDING, READ IN REAL TIME

Live dashboard

See it in action

A live app built with the dashboard SDK, running on a Thinger.io demo server. It is read-only, so explore it freely.

ConnectingRead-only demo account

Loading the live dashboard…

The platform

How it works

Field devices connect to Thinger.io over standard protocols. There you manage every device, store its data and trigger alarms.

Every protocol under one roof

Building devices arrive speaking LoRaWAN, Modbus or BACnet, and the platform closes the loop across all of them.

  • Native MQTT, HTTP and LoRaWAN ingestion, plus Modbus and BACnet through Node-RED gateways
  • Readings stored in data buckets, ready for dashboards, benchmarks and export
  • Rules react on their own: alerts, webhooks or setpoint and valve commands

Retrofit first, rip out nothing

Most smart building projects start in buildings that are already built and already occupied.

  • Battery LoRaWAN sensors install in minutes, with no cabling or downtime
  • Provisioning a thousand rooms works like provisioning one
  • White label dashboards for facility teams and tenants under your own brand

Success stories

Proven in the field

Good to know

Frequently asked questions

What teams ask before a pilot, answered with the numbers they need.

Still have questions? Talk to us
What CO2 levels should an office maintain, and what is demand-controlled ventilation?

European standard EN 16798-1 grades indoor air quality by CO2 concentration above outdoor air: 550 ppm for Category I, 800 ppm for Category II and 1,350 ppm for Category III. With outdoor air at roughly 420 ppm, the usual office target of Category II works out to about 1,200 ppm absolute, and readings that sit beyond Category III mean the space is underventilated for its occupancy.

Demand-controlled ventilation uses those readings as a control signal. Instead of running fans on fixed schedules sized for a full building, the air handling system modulates fresh air per zone based on measured CO2. Field and simulation studies report HVAC energy reductions of 9 to 33 percent, with fan savings of 25 to 55 percent in spaces with variable occupancy such as meeting rooms and open plan offices. An IoT platform closes the loop by feeding room level CO2 into the ventilation control and alerting when any zone drifts out of its category.

How does continuous temperature monitoring help with Legionella compliance?

Legionella multiplies between 20 and 45 degrees Celsius, so every control scheme comes down to keeping hot water hot and cold water cold. UK guidance HSG274 Part 2 asks for storage calorifiers at 60 degrees or above, hot water reaching outlets at 50 degrees or more within one minute (55 in healthcare), and cold water below 20 degrees, with monthly checks at sentinel taps. In Spain, Real Decreto 487/2022 sets equivalent temperature requirements and a documented prevention and control plan for every affected building.

PT1000 probes on tanks, return loops and sentinel outlets turn that manual routine into continuous telemetry: every reading is logged automatically, a loop that drops below threshold raises an alert the same day instead of waiting for the next monthly round, and the stored series becomes the audit trail an inspector asks for.

Can we monitor an existing building without new cabling?

Yes, and it is the most common starting point. Battery powered LoRaWAN sensors mount on a wall or ceiling in minutes, run 5 to 10 years on their cells and reach a gateway through several floors and walls, so a typical office building is covered with one or two indoor gateways. No conduits, no fire barrier penetrations, no disturbing tenants.

That changes the economics of retrofits: instrumenting a room costs a sensor plus minutes of labour rather than a cabling project, so coverage can grow floor by floor. Wired infrastructure that already exists, such as meters on RS-485 or points on the BMS, joins the same platform through gateways instead of being replaced.

How does the platform integrate with an existing BMS over Modbus or BACnet?

Through gateways, without touching the control logic. A small industrial gateway or edge PC running Node-RED polls the BMS or its field devices, using Modbus TCP/RTU and BACnet/IP nodes to read temperatures, setpoints, meter registers and alarm points, and forwards them to Thinger.io over MQTT. The built-in Node-RED plugin makes this a supported path in both directions: the same flow can write values back, for example adjusting a setpoint from an occupancy rule, while the BMS keeps running its safety interlocks locally.

The result is one layer above the whole building. BACnet air handlers, Modbus energy meters and LoRaWAN retrofit sensors land in the same buckets, dashboards and alert rules, and everything is exposed again through a REST API for FM software or energy reporting tools.

How much does a smart building deployment cost?

It depends on the number of buildings, the points monitored and the integration work, so most projects are quoted individually, but the orders of magnitude are known. Retrofit hardware is modest: a LoRaWAN indoor air quality sensor costs on the order of 100 to 250 euros per room, and a Modbus three phase meter with current transformers stays in a similar range per electrical panel, with installation measured in minutes rather than days.

On the platform side, our Private Cloud plans are published on the pricing page and start at 49 euros per month for a dedicated instance, which is usually enough to run a first building end to end. Larger portfolios and on premise deployments are sized per project.

Can one platform serve a whole portfolio of buildings and tenants?

Yes, that is the model the platform is designed around. Devices, dashboards and users are organized per project, so a facility operator, ESCO or property manager runs every building from one instance while each site keeps its own devices, data and alert rules. Per-user permissions decide exactly what a tenant, a maintenance contractor or a building manager can see and do.

Licenses include white label branding, so the operator serves its customers under its own name and domain: each tenant logs into a portal with the operator's brand and sees only its floor or building, while the operations team keeps a portfolio wide view for benchmarking consumption and dispatching maintenance.

Next step

Ready to build your smart building solution?

Tell us about your devices and your deployment, and we will map them to the platform. Or start on a free account and see it first.