Hardware manufacturers
Bring your device to the Marketplace
Share what it sends and work with the team on a simple integration sheet.
Talk to usPlatform · Marketplace
Stop integrating devices from scratch
Payload decoders, variables, uplinks and downlinks, already solved for devices from many manufacturers, for the network servers they travel through and for the tools around them. Install the integration and start from data, not from a datasheet.
The problem
Every new device is an integration project
The same temperature arrives in a different format from every manufacturer, and someone has to decode each one.
- MilesightEM320-THLoRaWAN
01 67D6 0002 68 52int16 LE · × 0.1Withoutem320-th.jsWithtemperature21.4°C - DraginoLHT65NLoRaWAN
CB F608 A201 9E 01 7F FFint16 BE · ÷ 100Withoutlht65n.jsWithtemperature22.1°C - ShellyPlus 1PMWi-Fi
{"temperature":{"tC":41.3,"tF":106.3}}JSON · field tCWithoutplus-1pm.jsWithtemperature41.3°C
What an integration brings
Everything a model needs to go from bytes to data
One hardware model, packaged once: how to read its messages, what it measures and how to talk back. Then reused in every project.
Worked exampleTemperature & humidity sensorLoRaWAN
The payload decoder
A few bytes optimised for air time. The decoder turns them into variables, so nobody reads the datasheet byte by byte.
The variables
Which measurements the device exposes, with units and structure, so applications never guess field names.
Downlinks and configuration
Sampling intervals, alarm thresholds or operating modes, built into the right downlink message.
A starting dashboard
Where it applies, a dashboard comes with the device, so data is visible from the first message.
Worked example from the Stop Integrating IoT Devices from Scratch article
Device integrations
Hardware from many manufacturers, grouped by the job it does
Pick a job to see what its hardware reports and a few models already in the catalogue.
Industry
Process data from the plant floor
What it reports
Cities
Street furniture that reports back
What it reports
Agriculture
Fields, silos and fences
What it reports
Buildings
Comfort, use and safety indoors
What it reports
Energy and water
Meters that read themselves
What it reports
Assets and fleets
Everything that moves
What it reports
Five models per job, from a much longer list. All of them are in the device catalogue
Network servers and connectivity
How it arrives, and what it means
The connectivity plugin decides how a message arrives, the integration what it means. Change the network server and nothing else changes.
The Things Stack
Configure the application ID and the console gives the webhook its endpoint, token and JSON format. One application, all its devices.
- Auto-provisioning
- Uplink
- Downlink
LORIOT
Connect a LORIOT application through its HTTP webhook. Devices and buckets are created by device type.
- HTTP webhook
- Device templates
ChirpStack
The same pattern for ChirpStack networks. Device integrations run on any of the three.
- Uplink
- Downlink
- Provisioning
Sigfox
Auto-provisioning, connection timeout alerts and downlinks written as JSON, encoded into 8 bytes.
- Uplink
- JSON downlink
- Timeout alerts
HTTP Device
Anything that can POST JSON: third party devices, cloud APIs or your own programs.
- HTTPS POST
- JSON
It all lands in the same console as devices on IOTMP, MQTT or HTTP. See Device Connectivity.
Plugins
Extend the platform with the tools you already use
A rule engine, a notebook or a monitoring stack is an install away, instead of another server to host and wire up.
Development
Node-RED next to the platform, with Thinger.io nodes. Jupyter, RStudio and VS Code install the same way.
- Node-RED
- Jupyter
- RStudio
- VS Code
Monitoring
Grafana opens from the console over device data, alongside Prometheus and Alertmanager.
- Grafana
- Prometheus
- Prometheus Exporter
- Alertmanager
Infrastructure and more
A container registry, file transfer and an MCP server.
- Docker Registry
- SFTPGo
- MCP Server
How it works
Find it, install it, let the devices arrive
Nothing to deploy by hand: the Marketplace is part of the console.
Step 1: In the console
Find it
The Marketplace sits next to devices and dashboards, with a readme and requirements per integration.
Step 2: One click
Install it
Installing creates the product: auto-provisioning, decoder, buckets, a dashboard and the downlinks.
Step 3: First message
Let the devices arrive
Point the network server at the platform. Each device provisions itself, already decoded.
Missing a device?
Every integration raises everyone’s starting point
Manufacturers bring their hardware, project teams ask for the model they need. Either way, it is built once and listed for everyone.
Project teams
Ask for the device you need
Tell us which model is missing, and how it reaches the platform.
Request an integrationyour-device/plugin.jsonProduct profile- Payload decoder
- Uplink and downlink
- Buckets and auto-provision
README.mdMarketplace pageassets/Product image
Marketplace · DevicesYour device
Now starts from data
- Your next project
- Another team’s project
- A customer deployment
Teams with their own hardware can also write custom plugins, following the Marketplace documentation
Next step
Start from a device that already sends meaningful data
Look up your hardware in the Marketplace and see what is already solved for it. Missing a model? Tell us, and it may be the next one in the catalogue.