IoT - myDevices Setup (Tektelic Gateway + Sensor)
While buying from myDevices directly, all gateways are pre programmed to communicate with the myDevices server, there are times when you may be purchasing from the vendor directly. In our case, the Tektelic Micro Gateway was purchased directly from Tektelic. Hence we need to edit the config file to ensure the gateway communicates to the myDevices server.
Step 1.
Download the KonaFT tool from the Tektelic Support Page.
Once installed and running, click on “Tools” tab and click “Find my gateway” and scan for it.
After the IP address has been found, click “Select”.
On the general tab, click on the “Start” button at the bottom (make sure the port number is 161)
As soon as the gateway is connected, the gateway info gets populated, now click on “Configuration” tab.
Next click on “Refresh” and you will see “/etc/default/config.json” in the drop down menu.
Select “Read” to view the config.json file.
Now we need to replace the server address in
"gateway_ID": "647FDAFFFE00BC53",
"server_address": "lorawan-ns-na.tektelic.com",
"serv_port_up": 1700,
to myDevice server which would be one of the following:
| Region | Server Address URL |
|---|---|
| United States | us-1.lns.mydevices.com |
| Europe | eu-1.lns.mydevices.com |
| Australia | au-1.lns.mydevices.com |
| Japan | jp-1.lns.mydevices.com |
| China | cn-1.lns.mydevices.com |
| Korea | kr-1.lns.mydevices.com |
Make sure to edit the “Gateway_ID” as well if it is incorrect.
After replacing the server address, click on “Write” and then click on “Reboot” at the bottom of the page.
Step 2.
In this section we will add the devices to the myDevices server. Since our Tektelic Gateway and Sensors were not purchased from myDevices, we need the support team at myDevices to allow these devices to access their server.
First go to “https://mydevices.atlassian.net/servicedesk/customer/portal/9” and submit a ticket to the support team with the DevEUI, AppEUI, and AppKey.
After a confirmation from the support team that the gateway has been added we can head to the myDevices portal to add our sensors.
Step 3.
Here we need to create a new location where all the devices will be grouped in so as to managed it easily.
First we create a new location in the portal.
Next we go to the “Menu” beside the location and add our devices. (Normally we would add the gateway first but in our case the support team has already done this part)
Now we go to the Menu and click on “Add Device”, fill in the DEV EUI or if you can scan the QR code to do the same.
Next we need to make sure that the sensor is active, follow the instructions of the sensor manual to activate it.
There may be a few hours wait time before the sensors become active.
Step 4.
Once the sensor is online, there are a few features that you can utilize on the myDevices Portal itself. Unlike the Tektelic server, you can view data here and use the platform for some basic needs.
You will notice there are a lot of fields that will appear empty in the sensor data. We can remove these by click on the sensor in the list and going into its settings.
Here you can uncheck anything that is not needed (example in our Tektelic Room Sensor, we have unchecked everything except a few key readings)
In the myDevices portal there are charts available for each reading of a sensor, which is something that was missing in the Tektelic Server that we discussed in our previous post. This allows for an ease of reading the data and exporting it for further use.
To check out a full suite of solutions available in New Zealand, check out the
Also, each location menu has settings for Alerts, Reports, which allows for further functionality. If you are a power user, there are Integrations myDevices provides to AWS, Azure and more, which we will discover in the following posts, starting with Azure IoT Central.
