See more information on HELIUM connection integration
Our AtlasLocator platform connects to the Lora Helium network through the HTTP protocol. Thanks to this integration you will be able to exploit all the data from your Helium network device on the AtlasLocator website.
You must already have your devices added and working on the platform. To integrate your Helium device with our platform, you must enter the control console of your Helium device.
Entering the Integrations option we will select the icon of a cloud with a + symbol that allows us to add a new integration.
Where we will choose, the first option, HTTP
Where we configure the parameters: Endpoint URL (Required): https://app.atlaslocator.com/api/v1/thirdparty/helium/v1
HTTP Headers (Optional usage for payload interpolation):
atl-key
LKmnH8NDdskYbslkjsHK9343KHKhhdsllHD
We will add in the blue button the integration under the name AtlasLocator
After adding the new integration we will add it in the Flows section to one of our sensors:
In the image we see our sensor in gray, the function in purple and the different integrations in green. In the example we have AtlasLocator plus another 4 extra from other platforms.
We will enter the devices section to collect the necessary data to register the device in the Atlas Locator platform:
We will select the device that we want to add to Atlas Locator and this screen opens:
The 2 parameters that are required in the integration of a HELIUM device with AtlasLocator are:
– Device EUI: It is seen on the current screen. (see image above).
– App EUI: It is seen on the current screen. (see image above).
With the two aforementioned data already obtained from the HELIUM platform, we can configure the device in the Atlas Locator platform, in the my devices section.
Initially configuring the communication protocol with the HELIUM platform.
And then writing in each field the values that we have been taking:
– Device EUI: GENERIC_DEVICE
– App EUI: GENERIC_APPLICATION
NOTE: When the purple block was defined in the Helium platform, we must define a template (script) for formatting the uplink payload.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.