Adding a sensor

To add a sensor to the Nekta system, it is necessary to:

1. Go to the “Devices” section.

2. Click on the “Add new device”.

3. Select “Add meter”. 4. Select the “Sensors” category.5. Select “manufacturer, model, connection type, sensor name, time zone, serial number (device ID)”.

LoRaWAN v1.0.3 — Gotthardp (standard pre-installed LoRa server);

LoRaWAN v1.1 (NEW) — Chirpstack. For users with the NEKTA Server version, you must first update the NEKTA software to the current version and send a request to configure a new LoRa server to the technical support email:

The Serial number field is optional. It can be specified or changed after adding a meter by “editing”.


When choosing a model, it is necessary to understand whether the device has a built-in modem and move the toggle switch under the inscription “is the device connected via a built-in modem?” if the sensor is equipped with a modem.

6. Select the Authorization type.

In most cases, the authorization type is set by the manufacturer of the LoRaWAN module. For some metering devices, it can be changed by a special configurator provided by the device manufacturer.

Activation keys can be scanned from a QR. The manufacturer can also write them on the boxes of devices, directly on the device, in the device certificate, or send them at the user’s request in xml or xls using email.

7. Enter the activation keys.

ABP authorization type:

  • DevAddr — 8 characters
  • AppSKey — 32 characters
  • NwkSKey — 32 characters

OTAA authorization type:

  • DevEUI — 16 characters
  • AppKey — 32 characters

It is necessary to pay attention to the fact that AppKey (OTAA) and AppSKey (ABP) are different keys. Entering a key that is used for another activation method will cause the meter to not get in touch.

8. Specify the Connection type of the base station to the Internet through which the sensor transmits data to the server.

If a SIM card is installed in the base station and is used as a backup connection, and the main connection is wired, then select No.

If you are using an Internet connection with a long data transmission delay, for example via satellite, it is recommended to select Yes.

9. Select the “Frequency Plan”.

The selected frequency plan should be the same as on the base station and sensor. A mismatch will cause data transmission to be lossy.

Frequency description:

  • RU868 — Current frequency plan for use in the territory of the Russian Federation, approved by LoRa Alliance
  • Nekta is using the RU868 frequency plan used prior to the approval of the LoRaWANRegional Parameters v1.1rB document
  • Smartiko is using the frequency plan used on Smart—Aqua water meters prior to the approval of the LoRaWAN™ Regional Parameters v1.1rB document
  • EU868 is using the current frequency plan in the territory of the Russian Federation, approved by LoRa Alliance

Comparative table of frequencies.

Channel RU868 Nekta Smartiko EU868
0 864.100 MHz 864.100 MHz 868.780 MHz 868.100 MHz
1 864.300 MHz 864.300 MHz 868.950 MHz 868.300 MHz
2 864.500 MHz 864.500 MHz 869.120 MHz 868.500 MHz
3 864.700 MHz 864.640 MHz 864.100 MHz 867.100 MHz
4 864.900 MHz 864.780 MHz 864.300 MHz 867.300 MHz
RX2 869.100 MHz 864.920 MHz 864.900 MHz 869.525 MHz
5 869.100 MHz 868.780 MHz 864.500 MHz 867.500 MHz
6 868.900 MHz 868.950 MHz 864.700 MHz 867.700 MHz
7 869.120 MHz 867.900 MHz
LoraSTD 868.300 MHz 864.600 MHz 864.600 MHz 868.300 MHz
FSK 868.800 MHz 864.800 MHz 864.800 MHz 868.800 MHz

10. Specify the “ID” of the priority BS or leave the field empty (the field is optional).

Please see “Features of using a priority BS” before selecting.


11. Select the sensor’s “Polling Period”.

Please see “Features of the polling period” before selecting.


12. Check the sensor data and click the “Create button”. Sensor is added successfully.

   Send article as PDF