Appearance
Gateways
Open Gateways.
A gateway is a hub device. It connects the plant link (DTU, serial bridge, or edge box) to Autoconnecto. Meters and sensors behind it are child devices. LoRa network servers stay under Integrations — that is a different path.
Hub vs child vs standalone
| Kind | Where you manage it | Token you paste into hardware |
|---|---|---|
| Gateway hub | Gateways | Gateway token (same kind of secret as a device token, owned by the hub) |
| Child device | Devices (and the children table on the gateway) | Usually none on the modem — data rides the hub. The child still has its own token if you ever connect it directly |
| Standalone device | Devices | Device token on that device |
Create hubs only from Gateways → Add gateway. Devices → Create is for field devices (standalone or with a parent gateway).
Create and commission
- Add gateway — Modbus or generic relay. Optional hardware preset (for example PUSR DR154) fills manufacturer and model.
- Open the gateway. Show / Copy the gateway token. Use Check connectivity for MQTT topics and sample publish.
- Setup — MQTT serial, LAN host, or outbound tunnel for Modbus; edge role for transparent vs edge compute.
- Add device on the gateway — child with profile and (for Modbus) slave ID. Device type is a dropdown.
- Detach keeps the child in Devices as standalone. Delete removes the child.
Delete a hub only when it has no children (detach or delete them first).
Tokens in configuration
Every device row (including a gateway) has one device token. On a hub we call it the gateway token because that is what you put in the DTU or edge MQTT client.
- Modbus DTU (for example DR154): MQTT username, password, and client ID = gateway token. Topics use that token. Autoconnecto stores readings on each child by slave ID / map — not on the hub as the meter.
- Generic relay: publish to the hub MQTT/HTTP path with
childDeviceIdin the body. Auth is the gateway token. Telemetry is stored on the child. - Standalone device: paste that device’s own token into firmware. No gateway involved.
- You do not paste a child’s token into the modem when the child only sits behind the gateway.
Reveal and copy live on the gateway page and on device details. Prefer the gateway page for hub commissioning.
Status
A gateway shows Active when the hub itself is active or any linked child is active. Optional hub health: publish gateway.heartbeat on the gateway token (no childDeviceId).
Related
- Devices — child and standalone list
- DR154 Modbus MQTT — DTU walkthrough
- Device connectivity — protocols and relay
- Integrations — LoRaWAN and other cloud ingest (not this menu)
