Getting started
There are two sides to Hiveron. You set your fleet up in the console — a point-and-click web app; nothing here needs the API. Then your devices talk to the API out in the field. This guide covers both.
Set up in the console
Do all of this at app.hiveron.net — no code required.
Create your account
Open the console, register with your email, and enter the 6-digit code it sends you. Confirming signs you straight in — no further setup.
Create a device type
Add a device type (for example “Water Sensor”). It groups similar devices, and firmware and devices both hang off it.
Register a device
Add a device with its serial number and type, then generate its keypair. The private key downloads once — keep it safe; you flash it onto the hardware.
Upload firmware
Upload a firmware binary and give it a version name. It is attached to the device type, ready to roll out.
Roll it out
Assign the firmware to the device type in bulk. Every matching device picks up the update the next time it checks in.
That's the whole console setup. Create an account and click through it — most people get here in a couple of minutes.
Connect your device
This is the part your firmware implements. A device authenticates by signing a short-lived token with its private key, then calls the /iot/* endpoints — it polls for firmware, posts telemetry, and drains queued commands. Posting a reading looks like this:
curl -X POST https://api.hiveron.net/iot/telemetry \
-H 'Authorization: Bearer <device-token>' \
-H 'Content-Type: application/json' \
-d '{ "content": "{\"temp_c\": 21.4}" }'
# -> 204 No ContentThe Device integration page explains how to build the token (with ready-made helpers for C, C++, and Python), and the API reference lists every endpoint a device calls.