Every gateway reports its connection and health to Hermetry. You see the current state on the gateway’s LoRaWAN tab, its health history as ordinary telemetry of its device, and all gateways together on the Gateway map.
Gateway states
| Badge | Meaning |
|---|---|
| Online | The gateway’s connection to the network server is open. |
| Offline | No connection. The time since it was last seen is shown beside the badge. |
| Disabled | Someone disabled the gateway. It is refused until enabled again. |
| Pending | A gateway that was seen but not accepted. This state belongs to LoRaWAN relays, which are in development; gateways you add are never pending. |
On the map, a gateway that never connected is shown as Never connected.
The gateway’s device follows the Live connection online rule of the built-in LoRaWAN gateway profile: the device is online exactly while its connection is open.
The gateway’s LoRaWAN tab
Open Devices, open the gateway, and select the LoRaWAN tab. The tab is read again every 10 seconds while it is open.
| Field | Shows |
|---|---|
| Gateway EUI | The EUI, with a copy button. |
| Protocol | Basics Station, or the licensed router link. |
| Region | EU868. |
| Network server | Cloud, or Local (on the gateway). |
| Round trip | Average time to the gateway and back, in ms. Marked above 800 ms. |
| Last seen | When the network server last heard from it. |
| Connected since | When the current connection opened. |
| Location | Latitude and longitude (and altitude when known), or Not on the map. |
Below the facts are the Connect the gateway steps, Frames this gateway heard (the last day, refreshed while the tab is open), and Devices heard recently (each device with its RSSI, SNR and when it was heard; No device heard in the last day. when empty). Select a device to open it.
Round trip and RX1
A Class A device listens for an answer one RX1 delay after its uplink (5 seconds by default on Hermetry). The network server must hand the answer to the gateway before that moment. A slow internet link at the gateway, such as weak mobile data, eats into this time. When the round trip is above 800 ms, devices with a short RX delay fall back to the second window (RX2). With the default 5-second delay, downlinks still make it.
Health telemetry
Once a minute, while the gateway is connected, the network server writes one health record to the gateway’s device. These are normal telemetry keys: chart them on dashboards and use them in alarm rules.
| Key | Meaning |
|---|---|
lora.gw.up_rx | Uplink copies received in the interval |
lora.gw.up_unique | Uplinks the gateway contributed after de-duplication |
lora.gw.rtt_ms | Average round trip in ms |
lora.gw.dn_sent | Downlinks the gateway confirmed it transmitted |
lora.gw.dn_failed | Downlinks that failed (refused by the gateway, or the connection was gone) |
lora.gw.dn_unknown | Downlinks with no result (Basics Station reports no failures) |
lora.gw.dn_failed_pct | Failed share of downlinks, when any were tried |
lora.gw.dc_used_pct.<band> | Share of the hourly duty-cycle budget used per EU868 sub-band (K, L, M, N, P, Q) |
Licensed routers report more keys; see Licensed routers as LoRaWAN gateways.
When the gateway connects, the network server also stores client attributes: lora.gw.station (gateway software version), lora.gw.firmware, lora.gw.model, lora.gw.protocol, lora.gw.mode and lora.gw.region.
Default health alarms
When alarms are available in your organisation, the built-in LoRaWAN gateway profile gets these rules. Change or switch them off on the profile’s Alarm rules tab.
| Rule | Raised when | Severity | Cleared when |
|---|---|---|---|
| Gateway offline | No connection for 10 minutes | Major, notifies admins | It connects again |
| Round trip | lora.gw.rtt_ms above 800 for 10 records in a row | Warning | Below 600 for 10 records |
| Failed downlinks | lora.gw.dn_failed_pct above 5 for 3 records | Minor | Below 2 for 10 records |
| Duty cycle nearly used up | Any lora.gw.dc_used_pct.<band> above 80 | Warning | All below 60 for 5 records |
| Offline buffer not draining | lora.gw.buffer_oldest_s above 3,600 for 2 records (licensed routers) | Minor | Below 1 |
| Temperature | lora.gw.temp_c above 75 for 3 records (licensed routers) | Major, notifies admins | Below 70 for 3 records |
The gateway map
- Open Devices.
- Open the ⋯ menu and select Gateway map.
The map shows every gateway of your organisation (up to 1,000), Basics Station gateways and licensed routers alike, coloured Online, Offline or Never connected. It refreshes every 15 seconds. Select a pin to open the gateway’s device page. Fit all zooms to show every pin.
Gateways without a location are listed under Not on the map. To place one:
- Select Place on the map beside it. The pin appears in the middle of the map.
- Drag the pin to where the gateway stands.
Each drop is saved at once, rounded to six decimal places. To move a placed gateway, drag its pin. You never type coordinates. Placing and moving needs the permission to manage gateways; others see the map read-only.
You can also set latitude, longitude and altitude through the API with PATCH /tenant/<tenantId>/api/iot/lorawan/gateways/<gatewayId>.