Skip to content
Hiveron

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.

1

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.

app.hiveron.net/register
The registration form — email and password; a 6-digit confirmation code follows.
2

Create a device type

Add a device type (for example “Water Sensor”). It groups similar devices, and firmware and devices both hang off it.

app.hiveron.net/admin/device-management
The “Add device type” dialog with the name field filled in as “Water Sensor”.
3

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.

app.hiveron.net/admin/device-management
The “Add device” dialog: serial number filled in, and the Generate keys button with the private-key download hint below it.
4

Upload firmware

Upload a firmware binary and give it a version name. It is attached to the device type, ready to roll out.

app.hiveron.net/admin/device-management
The firmware upload dialog with a version name (“v1.0.0”) and a selected binary file.
5

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.

app.hiveron.net/admin/device-management
The bulk roll-out dialog: target firmware selected, the optional “only devices currently on” filter, and the affected-device count.

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 each request with its private key (RFC 9421), then calls the /iot/* endpoints — it polls for firmware, posts telemetry, and drains queued commands. A signed reading looks like this:

POST /iot/telemetry
curl -X POST https://api.hiveron.net/iot/telemetry \
  -H 'Content-Digest: sha-256=:<base64 sha-256 of body>:' \
  -H 'Signature-Input: sig1=("@method" "@target-uri" "content-digest" "idempotency-key");created=...;expires=...;nonce="...";keyid="device:4:1";alg="ecdsa-p256-sha256";tag="iotnet-v2"' \
  -H 'Signature: sig1=:<base64 r||s>:' \
  -H 'Idempotency-Key: <uuid>' \
  -H 'Content-Type: application/json' \
  -d '{ "content": "{\"temp_c\": 21.4}" }'

# -> 204 No Content   (the C helper builds the signature headers for you)

The Device integration page explains the signature scheme in full (with a ready-made C helper), and the API reference lists every endpoint a device calls.

NextCore concepts