Own LoRa device (preset connectivity)

Connect a LoRa device which has built in LoRa connectivity that came with the device. You will need to enter the DevEUI, AppEUI, and AppKey of this device during registration in KPN Things.

  • Supported network type(s): KPNLORA

  • Device Specification ID: own-lora-with-keys

  • Device Specification UUID: c11ef507-293f-4f04-ad82-e2f1c777c339

DecodersdecoderSpecificationUUIDDescription

+ LoRa Geolocation data

af9e394d-6c1d-4d46-9a29-73ac77be64b7

Add LoRa Geolocation data to messages where location could be calculated.

= Raw LoRa payload

c17e2392-bb83-4e79-b854-ed72196857ee

Forward the raw LoRa payload and port number without decoding.

= Raw LoRa payload (v2)

bc523b60-1b3f-5f33-b041-3afbe29d13e0

Forward the raw LoRa payload and port number without decoding.

= Raw LoRa payload Extended

b7557a3d-4222-43e5-8b19-98706b1302f7

Forward the raw LoRa payload and lora network metadata without decoding.

= Raw LoRa payload Extended (v2)

bc9628e5-2c18-5f4b-9baf-5023d8b4a37b

Forward the raw LoRa payload and lora network metadata without decoding.

› Decoded ThingsML for LoRa payload

0d7b7295-287e-4908-878d-00d667f6f923

Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN.

› Decoded ThingsML for LoRa payload (v2)

5c03dd6b-42a6-5cf4-8790-8db27551431a

Decoder for ThingsML for LoRa, a generic LoRa payload protocol by KPN.

EncodersencoderSpecificationUUIDDescription

= Raw LoRa payload

1abb958a-d85a-4d6a-a44f-521f7e52adcd

Send raw LoRa payload to your device.

+ 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.

Expected SenML records

nametypeunit

payload

string

port

number

= Raw LoRa payload (v2)

Forward the raw LoRa payload and port number without decoding.

The following SenML records can be present, amongst others:

nametypeunitexampledescription

payload

string

"4D985C495AC4D8C9682CFD"

The LoRa hex payload

port

number

200

The LoRa port used to send this uplink

Example SenML

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.

[
    {
        "bn": "urn:dev:DEVEUI:0123456789012345:",
        "bt": 1693136532.83,
        "n": "payload",
        "vs": "4D985C495AC4D8C9682CFD"
    },
    {
        "n": "port",
        "v": 1
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

= Raw LoRa payload Extended

Forward the raw LoRa payload and lora network metadata without decoding.

Expected SenML records

nametypeunit

ADRbit

number

Channel

string

DevLrrCnt

number

FCntDn

number

FCntUp

number

LrrESP

string

LrrRSSI

string

LrrSNR

string

SpFact

number

SubBand

string

payload

string

port

number

Raw LoRa payload Extended (v2)

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.

The following SenML records can be present, amongst others:

nametypeunitexampledescription

ADRbit

number

0

Adaptive Data Rate indicator

Channel

string

LC255

Lora channel of the transmission

DevLrrCnt

number

0

Amount of gateways that received the message

FCntDn

number

21725

The downlink framecounter

FCntUp

number

30117

The uplink framecounter

LrrRSSI

number

0

Received Signal Strength Indicator

LrrSNR

number

0

Signal to Noise Ratio

payload

string

"4D985C495AC4D8C9682CFD"

raw hex payload string

port

number

1

LoRa port used

SpFact

number

9

Spreading factor used

SubBand

string

"G0"

Lora band of the transmission

Example SenML

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.

[
    {
        "bn": "urn:dev:DEVEUI:0123456789012345:",
        "bt": 1693136532.83,
        "n": "payload",
        "vs": "8ca683bd93124178afc5ff"
    },
    {
        "n": "port",
        "v": 1
    },
    {
        "n": "FCntUp",
        "v": 30117
    },
    {
        "n": "FCntDn",
        "v": 21725
    },
    {
        "n": "LrrRSSI",
        "v": 0
    },
    {
        "n": "LrrSNR",
        "v": 0
    },
    {
        "n": "DevLrrCnt",
        "v": 0
    },
    {
        "n": "SpFact",
        "v": 9
    },
    {
        "n": "SubBand",
        "vs": "G0"
    },
    {
        "n": "Channel",
        "vs": "LC255"
    },
    {
        "n": "ADRbit",
        "v": 0
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

› 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.

Example SenML

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.

[
    {
        "bn": "urn:dev:DEVEUI:6E5E267F2E6FB3BF:",
        "bt": 1693136532.83,
        "n": "latitude",
        "u": "lat",
        "v": 51.90717
    },
    {
        "n": "longitude",
        "u": "lon",
        "v": 4.48940
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": 29.75
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.59
    },
    {
        "n": "extTemp",
        "u": "Cel",
        "v": 17.22
    },
    {
        "n": "io",
        "vb": false
    }
]

= Raw LoRa payload encoding

  • Protocol: LoRa downlink

  • Description: Send raw LoRa payload to your device.

  • Multiple commands in one downlink: No

Input mapping:

  • Name: payloadHex (raw input)

Last updated