Migrating from Thingsee IoT on Haltian Developer Documentation

Thingsee MQTT vs Haltian IoT MQTT

Mon, 01 Jan 0001 00:00:00 +0000

This guide provides a detailed comparison between Thingsee MQTT and Haltian IoT MQTT, helping you migrate your MQTT integrations.

Quick Comparison

Aspect	Thingsee MQTT	Haltian IoT MQTT
Authentication	Client certificates (.pem, .key)	API key (username/password)
Certificate Management	Renewed by Haltian (12 months)	Self-service via IoT Studio (90 days)
Device ID	TUID (in path and data)	UUID (in path only)
Topic Structure	Flat with region codes	Hierarchical with event types
Data Format	Complex JSON with metadata	Streamlined JSON

Authentication

Thingsee MQTT

Uses client certificates (.pem and .key files)
Certificates provided by Haltian
No username or password required
TLS encryption with certificate validation

Haltian IoT MQTT

Uses API key authentication
API Key ID as username, API Key Token as password
No client certificates needed
TLS encryption

Credentials Validity

Platform	Validity Period	Renewal Method
Thingsee	12 months	Haltian renews; old certs remain valid
Haltian IoT	90 days	Self-service via IoT Studio; old token invalidated

Important

When a Haltian IoT API key token is refreshed, the previous token becomes invalid immediately.

Measurement Mapping

Mon, 01 Jan 0001 00:00:00 +0000

This page provides a complete mapping between Thingsee IoT message profiles (tsmId + field) and the corresponding Haltian IoT measurement types. Use this as a reference when migrating your data parsing, integrations, or analytics from Thingsee to Haltian IoT.

How to Read This Table

Column	Description
Thingsee tsmId	The Thingsee message profile ID
Thingsee Field	The JSON field name in the Thingsee message payload
Thingsee Devices	Device models that send this message
HIoT Measurement Type	The Haltian IoT measurement type name (used in GraphQL API)
HIoT Query Field	The field name used in GraphQL queries
Unit	Unit of measurement

Key Differences

In Thingsee IoT, a single message (e.g. tsmId 12100) can contain multiple sensor readings bundled together (temp, humd, airp, lght). Your application must parse the message type and extract relevant fields.

AI-Assisted Migration

Mon, 01 Jan 0001 00:00:00 +0000

Use these prompts with your preferred AI assistant (ChatGPT, Claude, Gemini, etc.) to get hands-on help migrating your integration code. Each prompt contains the full technical context needed — just paste your existing code at the end.

How to Use

Security: Redact Credentials

Before pasting code into any AI tool, remove or mask all sensitive values: API keys, passwords, tokens, certificates, private keys, connection strings, and internal hostnames. Replace them with synthetic placeholders (e.g. YOUR_API_KEY_HERE, mqtt.example.com).