HTTP V2 Integration
HTTP V2 forwards LoRaWAN device data and network events to an external HTTP endpoint. It supports V2 data converters and an extended metadata format.
Only V2 data converters can be used with HTTP V2.
-
Name
any unique Integration Name -
Type
Integration HTTP V2 Type -
Data Converter
Name of the Data Converter which will be used to decode and encode payload of Devices provisioned to the current Integration Only Converter v2 can be used with Integration v2. -
HTTP URL path
URL path part of Network Server endpoint which will be called by application to send downlink to device. Complete endpoint address will contain 3 parts:<Network Server domain name> <HTTP URL path> <automatically generated API key>Example:https://lorawan-ns-na.tektelic.com/api/v2/integration 36f77edf4a6440db80a6cecbf5b27c5ce7b63146fdfc485ca308a459cb6466f4NOTE: you have to provide Network Server URL before path part. API key will be generated once you will create HTTP V2 Integration (by pressing “Add”) -
Application address
Domain name of application endpoint which will be called by Network Server to send uplink from device. -
Port
port which is used by your application for HTTP protocol. -
Base path
URL path part of application endpoint which will be called by Network Server to send uplink from device. -
Enable HTTPS
Enable or disable TLS -
Authentication Method
Authentication method to be used -
Request Headers
Headers that can be added when Network Server calls application endpoint. -
Send empty payload
If selected LoRa packet will be pushed to application even if FRMPayload is empty -
Allow All Ports
Defines which LoRa ports can be used -
clientCertificate
clientCertificate can be:- passed as string
- drag-and-dropped
- uploaded file from PC
-
caCertificate
caCertificate can be:- passed as string
- drag-and-dropped
- uploaded file from PC
-
clientPrivateKey
clientPrivateKey can be:- passed as string
- drag-and-dropped
- uploaded file from PC
{
"devAddr": "076d51cf",
"adrBit": true,
"recvTime": 1393252152,
"margin": 0,
"deviceEui": "{devEUI}",
"deviceModelName": "{deviceModelName}",
"deviceName": "{deviceName}",
"deviceModelId": "{deviceModelId}",
"deviceClass": "{deviceClass}",
"fPort": 10,
"gatewayCount": 2,
"rfRegion": "EU868",
"dataRate": 5,
"fCntUp": 17,
"fCntDown": 1,
"battery": 0,
"confirmed": false,
"dataRate": 7,
"ackBit": false,
"frmPayload": "AQAACAQAAA3CAQAWAggAA2cBFgRoGGA/AWQ=",
"devStatusTimeMillis": 0,
"uLFreq": 867300000,
"applicationId": "{applicationId}",
"applicationName": "{applicationName}"
"gatewayRxInfo": [
{
"gwEui": "{gatewayMAC}",
"antennaId": 0,
"rssi": -112,
"snr": 2.5,
"lat": null,
"lon": null,
"alt": null,
"gatewayName": "{gatewayName}",
"channel": 1,
"codeRate": "4/5",
"crcStatus": 1,
"dataRate": {
"modulation": "LORA",
"spreadFactor": 7,
"bandwidth": 125
},
"gwTimeUtcMillis": null,
"gwTimeGpsMillis": null,
"rsig": null
}
]
}
-
recvTime
GPS Seconds - the moment NS received the UL, represented as GPS time in seconds (number of seconds since January 6, 1980). This is not a Unix/UTC timestamp: the two epochs differ by 315964800 seconds (3657 days), so arecvTimevalue read directly as Unix time is off by about 10 years. To convert:unixSeconds = recvTime + 315964800 - 18, where 18 is the number of leap seconds between UTC and GPS time as of 2017. -
gatewayRxInfo[].gwTimeGpsMillis
Gateway reception time in GPS milliseconds, using the same epoch asrecvTime. May benull. -
gatewayRxInfo[].gwTimeUtcMillis
Gateway reception time in Unix/UTC milliseconds. May benull.
{
"deviceEui": "647FDA0000000000",
"confirmed": false,
"msgId": "1",
"data": {
"field1": "value1",
"field2": "value2"
...
}
}
For REST API-based creation and the complete set of configuration options, see HTTP Integration v2 APIHTTP Integration v2 API.