Own LoRa device (programmable)
Last updated
Last updated
Connect a LoRa device for which you currently do not have LoRa connectivity credentials (DevEUI, AppEUI, and AppKey). These credentials will be provided during registration of the device in KPN Things.
Supported network type(s): KPNLORA
Device Specification ID: own-lora
Device Specification UUID: 1e7f596c-6eb4-44d2-bec6-0d93181d4330
Decoders | decoderSpecificationUUID | Description |
---|---|---|
+ LoRa Geolocation data |
| Add LoRa Geolocation data to messages where location could be calculated. |
= Raw LoRa payload |
| Forward the raw LoRa payload and port number without decoding. |
= Raw LoRa payload (v2) |
| Forward the raw LoRa payload and port number without decoding. |
= Raw LoRa payload Extended |
| Forward the raw LoRa payload and lora network metadata without decoding. |
= Raw LoRa payload Extended (v2) |
| Forward the raw LoRa payload and lora network metadata without decoding. |
› Decoded ThingsML for LoRa payload |
| Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN. |
› Decoded ThingsML for LoRa payload (v2) |
| Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN. |
Encoders | encoderSpecificationUUID | Description |
---|---|---|
= Raw LoRa payload |
| Send raw LoRa payload to your device. |
Add LoRa Geolocation data to messages where location could be calculated.
Forward the raw LoRa payload and port number without decoding.
Expected SenML records
name | type | unit |
---|---|---|
payload | string | |
port | number |
Forward the raw LoRa payload and port number without decoding.
This decoder also decodes Geolocation and Local Gateway data.
The following SenML records can be present, amongst others:
name | type | unit | example | description |
---|---|---|---|---|
payload | string |
| The LoRa hex payload | |
port | number |
| The LoRa port used to send this uplink |
SenML can be structured in different ways, and we do not guarantee the examples below will look the same as what you will receive on your Destination. To make sure you can handle the SenML optimally, take a look at our documentation about Understanding and Interpreting SenML Data.
Forward the raw LoRa payload and lora network metadata without decoding.
Expected SenML records
name | type | unit |
---|---|---|
ADRbit | number | |
Channel | string | |
DevLrrCnt | number | |
FCntDn | number | |
FCntUp | number | |
LrrESP | string | |
LrrRSSI | string | |
LrrSNR | string | |
SpFact | number | |
SubBand | string | |
payload | string | |
port | number |
Forward the raw LoRa payload and lora network metadata without decoding.
Fixes from '= Raw LoRa payload Extended':
LrrRSSI
is changed to a number
.
LrrSNR
is changed to a number
.
LrrESP
is changed to a number
.
This decoder also decodes Geolocation and Local Gateway data.
The following SenML records can be present, amongst others:
name | type | unit | example | description |
---|---|---|---|---|
ADRbit | number |
| Adaptive Data Rate indicator | |
Channel | string |
| Lora channel of the transmission | |
DevLrrCnt | number |
| Amount of gateways that received the message | |
FCntDn | number |
| The downlink framecounter | |
FCntUp | number |
| The uplink framecounter | |
LrrRSSI | number |
| Received Signal Strength Indicator | |
LrrSNR | number |
| Signal to Noise Ratio | |
payload | string |
| raw hex payload string | |
port | number |
| LoRa port used | |
SpFact | number |
| Spreading factor used | |
SubBand | string |
| Lora band of the transmission |
SenML can be structured in different ways, and we do not guarantee the examples below will look the same as what you will receive on your Destination. To make sure you can handle the SenML optimally, take a look at our documentation about Understanding and Interpreting SenML Data.
Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN.
Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN.
This decoder also decodes Geolocation and Local Gateway data.
SenML can be structured in different ways, and we do not guarantee the examples below will look the same as what you will receive on your Destination. To make sure you can handle the SenML optimally, take a look at our documentation about Understanding and Interpreting SenML Data.
The resulting SenML completely depends on the ThingsML input and can produce almost any type of SenML output. The decoded ThingsML provided below is just an illustration of what is possible.
Protocol: LoRa downlink
Description: Send raw LoRa payload to your device.
Multiple commands in one downlink: No
Input mapping:
Name: payloadHex
(raw input)