akenza.io
Search…
Swisscom LoRaWAN
This page describes the setup process of the Swisscom LoRa account to be used in akenza
Swisscom provides a swiss wide Low Power Network (LPN) over LoRaWAN. It already covers more than 96.7% of the Swiss population, making it one of the biggest public available LoRa networks in Switzerland.
The seamless integration from the LoRa network into akenza makes the management of already connected IoT devices and new projects effortless.
The integration does not require an account with the network provider, as this is provided by akenza. It should be noted that a monthly connection fee for each registered device applies when using said integration.

Connecting own account

In order to manage a Swisscom LoRaWAN account, only the username and password are required. For further communication with the system in question, an API-User will be generated by akenza.
Said password is never stored in akenza!
Integration Login
If the entered credentials are correct, the integration name and how the data is processed can be specified in the next step.
If the checkbox "Process Data in Akenza" is checked the data will be forwarded to akenza. This only affects devices created through akenza and has no impact on already registered devices. If this option is unchecked, the data will not be forwarded to akenza. Instead, devices created through akenza will have the default data route assigned, which can be configured on the Swisscom system. Alternatively, during the setup of the integration, a new data route can be created. If this option is selected, the newly created data route will be assigned to all devices created through akenza (in addition to the data route forwarding the data to akenza, if specified).
Integration name & Data Routes
When creating a data route, the content type and destination can be specified. It is highly encouraged to use uplink and downlink security. Otherwise, the IoT devices and applications can be compromised.
The Application Server ID can be any string, however, it would be best if a long and random generated string is used instead.
The Application Server Key needs to be a HEX string consisting of 32 characters. The functionality to generate such a random key is provided by us.
Creation of Data Route
After everything is set up, the integration is created and the initial synchronization is started. Depending on how many devices are registered, this could take several minutes.
Once the synchronization was successful, the devices appear in the Asset Inventory Overview. Now the devices can be managed through akenza.
Last modified 6mo ago
Copy link