Haltian IoT in 10 Minutes

A plain-language introduction to the Haltian IoT platform — what it measures, how your buildings are modelled, and how you get the data out

What is Haltian IoT?

Haltian IoT turns physical spaces into data you can act on. Battery-powered sensors measure what happens in your buildings — whether a room is occupied, how many people pass through a door, how warm or stuffy the air is — and send it to the Haltian IoT cloud. From there you read it in a ready-made application, stream it into your own systems, or export it for analytics.

The sensors detect presence using passive infrared, radar, or laser. There are no cameras, no microphones, and no biometric data — so the data is anonymous by design, which keeps GDPR and works-council conversations simple.

How the pieces fit together

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#F6FAFA', 'primaryTextColor': '#143633', 'primaryBorderColor': '#143633', 'lineColor': '#143633', 'secondaryColor': '#C7FDE6', 'tertiaryColor': '#73F9C1', 'clusterBkg': '#ffffff', 'clusterBorder': '#143633', 'edgeLabelBackground': '#ffffff'}}}%%
flowchart BT
    subgraph North["Your systems and users"]
        Apps["fa:fa-desktop Haltian applications"]
        Yours["fa:fa-building Your apps, BI, Microsoft Places"]
    end

    subgraph Middle["Haltian IoT cloud"]
        Cloud["fa:fa-cloud Data storage and APIs"]
    end

    subgraph South["Your building"]
        Sensors["fa:fa-microchip Sensors"]
        GW["fa:fa-broadcast-tower Gateway"]
    end

    Sensors --> GW --> Cloud
    Cloud --> Apps
    Cloud --> Yours

    style North fill:#ffffff,stroke:#143633,stroke-width:2px,color:#143633
    style Middle fill:#ffffff,stroke:#143633,stroke-width:2px,color:#143633
    style South fill:#ffffff,stroke:#143633,stroke-width:2px,color:#143633
    style Sensors fill:#F6FAFA,stroke:#143633,stroke-width:2px,color:#143633
    style GW fill:#F6FAFA,stroke:#143633,stroke-width:2px,color:#143633
    style Cloud fill:#73F9C1,stroke:#143633,stroke-width:2px,color:#143633
    style Apps fill:#C7FDE6,stroke:#143633,stroke-width:2px,color:#143633
    style Yours fill:#C7FDE6,stroke:#143633,stroke-width:2px,color:#143633

Sensors talk to a gateway over a self-healing wireless mesh, the gateway talks to the cloud, and everything above the cloud is a choice you make: use our applications, use your own, or both.

How your buildings are described

Before the data means anything, the platform needs to know where each sensor sits. It models locations, buildings, and floors as a hierarchy. Zones describe areas on a floor, while devices are assigned to a space, typically a floor:

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#F6FAFA', 'primaryTextColor': '#143633', 'primaryBorderColor': '#143633', 'lineColor': '#143633', 'secondaryColor': '#C7FDE6', 'tertiaryColor': '#73F9C1', 'clusterBkg': '#ffffff', 'clusterBorder': '#143633', 'edgeLabelBackground': '#ffffff'}}}%%
flowchart TB
    Organization --> Location --> Building --> Floor
    Floor -->|area| Zone
    Floor -->|device spaceId| Device
    Device -->|measurement deviceId| Measurement

For example, Oulu Headquarter contains the Yrttipellontie 1 building, which contains the 3rd floor. Meeting Room Taika is a zone on that floor; a sensor is assigned to the floor and produces measurements.

Measurement records identify the device that reported them; they do not repeat the full location hierarchy. To add spatial context to a report, use deviceId to look up the device and its spaceId, then follow the space hierarchy to the building and location. For zone-level reporting, use the available zone assignment or position data: a device’s spaceId identifies its space, not a specific zone.

Zones are areas such as meeting rooms, desk areas, parking slots, or cafeterias. You define them to match how your organization talks about the space.

See Data Model for the full entity reference.

What a measurement actually is

Measurements are reported based on their type. For state measurements such as occupancy, the last state remains valid until it changes. Temperature, CO₂, and battery readings may also be sent when a threshold is crossed or on a configured schedule, so gaps have different meanings for different measurements.

See Event-Based Measurements for details.

Getting the data out

There are several ways to consume the data, and most customers end up using more than one.

You want to…	Use	What it is
Look at it, manage devices, check installations	Haltian applications	Studio, Finder, and Field — ready to use, nothing to build
React to changes as they happen	Stream API	Live MQTT feed of measurements
Query devices, spaces, and metadata	Service API	GraphQL API for everything in the data model
Analyse history, feed BI or AI/ML	Data API	Bulk Parquet export to your data lake
Use the tools you already have	Integrations	Microsoft Places, ThingsBoard, Azure IoT Hub and more

Where do you want to go deeper?

Pick the question closest to what’s on your mind:

If you’re asking…	Start here
“What can you actually measure?”	Device catalog
“How would this map onto our sites and buildings?”	Data model
“Can I just see it working?”	Demo environment
“How do we get the data into our own systems?”	APIs and Integrations
“Does this work with Teams and Outlook?”	Integrations
“Who in our organization can see what?”	Roles and access
“Is it secure and GDPR-safe?”	Security
“How do the sensors reach the network?”	Wirepas mesh
“What does that term mean?”	Glossary

Try it yourself

The fastest way to understand the platform is to open it. The demo environment is a public sandbox with live sensor data from real Haltian sites — log in to Haltian Studio, browse the space hierarchy, and run a few API queries against it before you commit to anything.