Your gateways connect to Hermetry’s network server at an address that belongs to your organisation. You put this address on each gateway once. This page explains the address, where it comes from and how to read it.
What the address looks like
wss://<your organisation's web address name>.<network server host>wss://means a secure websocket connection (TLS). Gateways never connect over a plain connection.- The first part is your organisation’s web address name (its slug), the same name your free subdomain uses.
- The second part is the network server host of the Hermetry installation.
For example, an organisation whose web address is acme.<platform domain> connects its gateways to wss://acme.<network server host>.
All gateways of your organisation use the same address. Each gateway still has its own token, so the address alone lets nobody in.
Where to find it
You do not need to type the address by hand:
- Right after you add a gateway, the drawer shows the setup values with Copy buttons and lets you download the three configuration files.
- Later, open the gateway on the Devices page and its LoRaWAN tab. The Connect the gateway section shows the same address.
The setup section shows:
| Value | Meaning |
|---|---|
| LNS address | The address the gateway connects to (the gateway’s tc.uri). |
| Discovery address (some gateways ask for it instead) | The same address followed by /router-info. Some gateways first ask this address where to connect. |
| Token header | The authorisation line for the gateway’s tc.key. Shown only right after the gateway was added or its token rotated. |
The server certificate
Your gateway must trust the network server’s TLS certificate. The gateway’s tc.trust setting holds the certificate it trusts.
- When the installation hands out the certificate, step 3 of the setup says Set the server certificate (tc.trust): download it below, or choose the system’s certificate store if the gateway offers it. The
tc.trustfile is offered for download together with the token. - When it does not, step 3 says This installation does not hand out the server certificate. Use the gateway’s system certificate store. Choose the gateway’s built-in certificate store.
If your web address changes
The network server address follows your organisation’s web address name. When an administrator changes it, the address of your gateways changes with it. Update the LNS address on every gateway, or they cannot connect to the new name.
When no address is shown
If the setup says The LNS address of this installation is not configured yet. Ask your administrator., the installation has no network server address. Gateways cannot connect until the platform administrator sets one. On the hosted service the address is always set.
Ports
The address has no port when the network server is reached on the standard TLS port 443. If an installation uses another port, the address shows it (wss://name.host:port). Copy the address exactly as shown.
Read it through the API
GET /tenant/<tenantId>/api/iot/lorawan/setupNeeds the permission to view LoRaWAN gateways. The answer contains no secret:
{
"setup": {
"lnsUrl": "wss://acme.lns.example.com",
"routerInfoUrl": "wss://acme.lns.example.com/router-info",
"trustAvailable": true,
"region": "EU868"
}
}trustAvailable says whether the installation hands out the tc.trust file. The answer also lists the supported gateway protocols: Basics Station and the licensed router link (see Licensed routers as LoRaWAN gateways).