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

Frequently asked questions

Short answers to the questions new customers and firmware authors ask most, each with a link to the page that explains it.

This page answers the questions new customers and firmware authors ask most often. Each answer is short and links to the page with the full details.

Getting started

What do I need to connect my first device?

An organisation, a member with the Admin role (creating devices needs it by default), and a device or a computer that can run an MQTT client or curl. The network must allow outgoing TCP 8883 (MQTT over TLS) or 443 (HTTPS). See Connect your first device.

Where do I find the host name my devices connect to?

On the Connection details card of the device page. It shows the broker host, the port and the HTTPS address for that device. See Hostnames, ports and IP addresses.

Which ports must our firewall allow?

Outgoing TCP 8883 for MQTT over TLS, and 443 for the app and the device HTTP API. LoRaWAN gateways use the port in their network server address, 443 when it shows none. Nothing needs to come in, except for devices that Hermetry polls, such as SNMP agents and cameras. See Hostnames, ports and IP addresses.

Which browsers can we use?

Chrome, Edge and Firefox 111 or newer, and Safari 16.4 or newer. Passkeys, push, 3D views and camera video have extra needs. See Supported browsers.

Connecting devices

Which protocols can my devices use?

MQTT over TLS, the HTTPS device API, and LoRaWAN through Hermetry’s network server. Devices that cannot connect themselves can be polled (SNMP, cameras) or report through a gateway. See Choose how to connect.

Is MQTT 5 supported?

No. Hermetry speaks MQTT 3.1.1 (protocol level 4). A CONNECT for MQTT 5 is refused with CONNACK return code 1. See MQTT.

Can a device connect without TLS?

Only if its device profile allows plain MQTT on port 1883. Profiles are TLS only (port 8883) by default, and a device that logs in on port 1883 is then refused. See Device transport security.

How does a device prove who it is?

With an access token (the MQTT username, or a bearer token over HTTPS), an MQTT username and password, or an X.509 certificate. Each device should have its own credential. See Device credentials.

Which topic and payload do I send telemetry with?

Publish a JSON object to v1/telemetry, for example {"temperature": 21.5}, or an object with ts and values. See MQTT topics and payload reference.

Our firmware already publishes to v1/devices/me/telemetry. Do we have to change it?

No, if you give its profile the Legacy compatible topic scheme. That scheme carries telemetry and attributes only, with no command topics. See MQTT topics and payload reference.

How large can one message be?

64 KiB by default. A profile can set its payload cap between 1 KiB and 64 KiB. See Device profiles.

What happens to readings with a wrong time stamp?

A reading more than 10 minutes in the future is dropped, not corrected; the organisation’s telemetry settings can change that window. A reading without a time stamp gets the time it arrived, so a device without a synchronised clock should leave the time stamp out. See Timestamps, late and duplicate readings.

Firmware and remote access

How do firmware updates reach a device?

Hermetry writes the update as shared attributes, including fw_url, a short-lived HTTPS download link (15 minutes by default). The device downloads, checks and installs the image and reports its progress in fw_state. An unsigned image cannot be assigned unless the profile allows unsigned images. See Firmware updates (OTA).

Can we open a router’s web panel without a fixed IP address?

Yes, for claimed licensed routers whose firmware supports it. The router dials out when you select Open panel, so no port needs to be open on site. A router allows at most 3 open sessions. See Remote access to a router’s panel.

Organisation and security

Can we use our own domain?

Every organisation has a free address under the platform’s domain. A custom domain such as iot.example.com is available when your plan includes custom domains; you create the DNS records and the certificate is handled for you. See Web addresses and custom domains.

Why do sign-in e-mails come from the platform’s sender, not ours?

Sign-in codes, password resets, verification and invitation links always go through the platform’s own mail service, so no other mail server can read them. They still carry your organisation’s brand. See Account and security e-mails.

How can we protect our members’ sign-in?

Members can add passkeys, an authenticator app, or e-mail or SMS codes, and an owner can require two-step verification for every member. See Two-factor sign-in and passkeys.