New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Connecting hundreds of devices: device profiles, bulk import and quarantine

Two ways to get hundreds of devices in: a CSV file you import, or devices that register themselves with a profile key. Profiles come first in both cases.

To bulk import devices into Hermetry, create one device profile per kind of device first, then load a CSV file with one row per device. Hermetry checks the whole file before it writes anything, creates each device’s credential itself, and hands the new credentials back in a file you can download once.

Hermetry 2.0, released on 26 August 2026, shipped devices over MQTT and HTTP with device profiles, credentials and provisioning. This guide covers two ways to get hundreds of devices in at once: import a file when you know the names, or let devices register themselves with a profile’s provisioning key. Profiles come first in both cases.

Why create device profiles before adding devices?

A profile decides how every device of one kind behaves, and changing it changes all of them at once. Every device uses exactly one profile.

The device profiles reference recommends one profile per sensor model, firmware family or security need, for example one TLS profile and one for old devices that cannot do TLS. Whether a kind of device should talk MQTT or HTTP is in my post on MQTT vs HTTP for IoT devices. An import row that names a profile which does not exist is refused, so the profiles have to be there before the file is.

How do you import IoT devices from a CSV file?

Download the template, fill in one row per device, and let the wizard check the file before you import it. The Imports page is there when the import module is on in your organisation, and you need the permission to create devices.

  1. In the import wizard, select Download a template and fill in one row per device. Only the name is required.
  2. Open Imports, select New import, pick IoT devices and choose the CSV file.
  3. Select Check the file. Nothing is written yet; you see the rows ready to import, the rows that will be skipped and the rows with a problem.
  4. Select Import n rows. Rows with a problem are left out.
  5. Download the new devices’ credentials. The file can be downloaded once.

Never put a secret in the file. A column named like a secret, such as token or password, is refused, and so is a cell that looks like an access token, because Hermetry creates the credentials itself. The bulk import guide lists every column and every refusal.

Self-provisioning or import for many devices?

Import when you know the device names in advance; use self-provisioning when each device should ask for its own credential on first start. The table compares import with the self-provisioning strategy Allow creating new devices.

ImportAllow creating new devices
Who creates the deviceYou, from the fileHermetry, with the name the device sends
Starts quarantinedNoYes, by default

What does device quarantine do?

It holds a device that registered itself until an administrator says it belongs. A device created under Allow creating new devices starts quarantined: it can log in, but its telemetry and attributes are acknowledged and dropped.

An administrator activates the devices they recognise, and their data is stored from then on. Quarantined devices count toward your device limit while they wait. Quarantine keeps a leaked provisioning key from filling your organisation with devices whose data you trust.

Frequently asked questions

Does an imported device start in quarantine?

No. Quarantine applies to devices that registered themselves under a profile that allows creating new devices. A device added from an import file or by hand was created on purpose by someone in your organisation, so it does not wait for an administrator to activate it.

What happens to data a quarantined device sent before activation?

It is not kept. While a device is quarantined, Hermetry acknowledges its telemetry and attributes and drops them. Once an administrator activates the device, it reconnects as an active device and its data is stored from then on, so activate devices before you rely on their history.

Why does the import refuse a column called token or password?

Because Hermetry creates every new device’s credential itself and returns the credentials in a file you download once, so the import file never needs a secret. It refuses columns named like a secret and cells that look like access tokens. I am glad of it: a file that carries secrets tends to be copied, mailed and left on shared drives.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.