The LoRaWAN LNS Connector enables seamless integration with numerous LNS providers, over 400 device encoders and decoders, and leverages all of the existing northbound connectors
- Common encoding and decoding across all LNS providers.
- Most common fields extracted and normalized.
- Option to include raw uplink from LNS to take advantage of any LNS specific information.
- LNS Providers
- Actility (Uplink & Downlink)
- Chirpstack (Uplink)
- Everynet (Uplink)
- Helium (Uplink & Downlink)
- Loriot (Uplink & Downlink)
- NetMore (Uplink & Downlink)
- Senet (Uplink & Downlink)
- The Things Industries (Uplink & Downlink)
- Transcoders
The LoRaWAN LNS Connector service serves as an anchor for defined endpoints.
- Webhook Secret - Secret key used when configuring the HTTP integrations with the LNS providers.
- Include LNS information - Include the raw LNS information in the uplink packets, this is useful if you need to mine out LNS specific information from the uplink.
- Hostname - The hostname for the API server for your ThingPark instance, typically
api.thingpark.com or iotnz.thingpark.com.
- AS ID - The AS ID you created when configuring downlink security in the ThingPark portal.
- Tunnel Interface Key - The Tunnel interface authentication key you created when you configured downlink security in the ThingPark portal.
- Server Hostname - The API server to use for sending downlinks, typically
portal.senetco.io.
- API Key - The API key to access the API server.
- Server Hostname - The API server to use for sending downlinks, typically
<region>.loriot.io.
- API Key - The API key to access the API server.
The netmore connector uses MQTT, as such, additional configuration is required.
- Enable Netmore MQTT Connection - True/false if you would like to establish the MQTT connection to the Netmore Broker.
- MQTT Broker - The URL for the Netmore MQTT Broker, typically mqtt+ssl://mq.blink.services:8883.
- MQTT Username - The username assigned for your connection.
- MQTT Password - The password assigned for your connection.
- MQTT Client ID - The ClientID assigned for your connection.
- Service Provider - The service provider you wish to listen on for notifications.
- Customer - The Customer ID to listen on for notifications.
The LoRa endpoint contains information about each device that communicates with the IoT Bridge. Most importantly it holds the device EUI, and the device type fields.
- Device EUI - The device EUI is a hexidecimal string used to uniquely identify a LORA device. This field must be unique for a given service instance (required).
- Device Type - Optionally, you can select the device type from a list of over 400 decoders included in the platform. If a decoder is selected, then there will be a new field in the uplink event called
decoded that includes the decoded data from the payload. If a device type is not specified, then only the raw payload will be available.
This event fires when an uplink message is received by the LNS. The lns parameter can vary depending on the LNS source, and is subject to change as the LNS providers change their data formats. Additionally, the decoded field may vary from device to device as the decoders are specific to the device implementation.
{
"decoded": {
"batteryLevel": 0,
"batteryVoltage": 2.5,
"buttonPressed": 0,
"gnssAccuracy": 32,
"gnssFix": 8,
"latitude": 45.448847,
"longitude": -75.635177,
"temperature": 25
},
"deviceType": "tbol100-1.0.1",
"fCnt": 603,
"fPort": 136,
"gatewayCount": 2,
"lns": <varies>,
"location": {
"lat": 45.44879109595188,
"lng": -75.63522618379866
},
"radio": {
"channel": 1,
"frequency": 904.0999755859375,
"rssi": -63,
"snr": 14
},
"raw": "CAA5j361AhfmfXs=",
"source": "helium"
}
- decoded: The decoded data from the packet, only available if the
Device Type is specified in the endpoint.
- deviceType: The device type that was configured in the endpoint, this is useful for switch statements in triggers to process different device types.
- fCnt: The uplink frame counter.
- fPort: The port for the uplink message.
- gatewayCount: The number of gateways that saw the device, for some LNS providers this value will always be 1.
- lns: LNS specific information, will only be present if
Include LNS Information is set to true in the service.
- location: The location as determined by the LNS, any location available in the decoded data is not taken into account.
- radio: Common parameters related to the communications from the device.
- raw: The binary data received from the device, the value will be a byte array, but in the logs it may appear base64 encoded.
- source: The LNS type that received the data.
This event fires when a device joins the network
{
"gatewayCount": 2,
"location": {
"lat": 45.44879109595188,
"lng": -75.63522618379866
},
"radio": {
"channel": 7,
"frequency": 905.2999877929688,
"rssi": -42,
"snr": 14.199999809265137
},
"source": "helium"
}
- gatewayCount: The number of gateways that saw the device, for some LNS providers this value will always be 1.
- lns: LNS specific information, will only be present if
Include LNS Information is set to true in the service.
- location: The location as determined by the LNS, any location available in the decoded data is not taken into account.
- radio: Common parameters related to the communications from the device.
- source: The LNS type that received the data.
Schedule a downlink message for a device with the LNS provider.
// Schedule a downlink message to device 'mydevice' on fport 100.
lora.downlink('mydevice', convert.hexToBin('0102030405'), 100)
// Use the configured device type decoder to encode the message. You must know the format based on the device type you select.
lora.downlink('mydevice', { reportingInterval: 60 }, 100)
- endpoint: The platform endpoint key used to find the device to communicate with. Note that this is the endpoint key, not the device EUI.
- data: Data can either be a byte array or an object. If an object is specified, then the platform will use the configured device type encoder to convert the object to a byte array for the device.
- fport: The port to send the downlink message to.
- options: Reserved for future use.
The following events are considered billable:
- Device Join events
- Device Uplink events
- Device Downlink actions