KPN LocationTag II

Also known as Security Tag.

  • Supported network type(s): KPNLORA

  • Device Specification ID: kpn-locationtag-ii

  • Device Specification UUID: 2f16485d-1301-4d11-9fb8-1b74b5a8909f

DecodersdecoderSpecificationUUIDDescription

+ LoRa Geolocation data

d2593092-bc42-4b84-a053-2301f499bbc4

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

+ Location by LoRa On Premises Gateway reception

71703178-038d-4ea9-b865-00819fb42417

Add location data to messages that are received by known LoRa On Premise Gateways.

› Decoded payload for Device Management

aec28f98-7e78-4eb9-a314-04f435219bc5

Decoder for Streamline LoRa short payloads, containing firmware version, mode, and battery status.

› Decoded payload for Device Management (v2)

c0d1ea0f-2470-5f88-897c-c1ec25f360d6

Decoder for Streamline LoRa short payloads, containing firmware version, mode, and battery status.

› Decoded payload for Medical Tracker application

9e8b2100-537d-46f8-ab21-4fad11d04bc9

Decoder for Streamline LoRa message type 0xD282 containing only temperature and movement bit.

› Decoded payload for Medical Tracker application (v2)

6a7a4ef4-e7a3-5eab-90ba-6901cf360d08

Decoder for Streamline LoRa message type 0xD282 containing only temperature and movement bit.

EncodersencoderSpecificationUUIDDescription

‹ Encoded device modes for Asset Recovery application

9e2a47a3-a239-4f1f-b14b-f16fa70fe99d

Send device modes for Asset Recovery: Presales (24h interval), Active (2h interval), Missing (5min interval + BLE), or Inactive.

+ LoRa Geolocation data

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

Expected SenML outputs

nametype/unitexampledescription

locOrigin

string

KPNLORA

indicates the origin of the location data

latitude

numeric

51.79

longitude

numeric

4.68

radius

m

319

locAccuracy

%

locPrecision

%

locTime

timestamp

1637165561

Example SenML-message

This location info can be merged with the payload of the device

[
  {
    "bn": "urn:dev:DEVEUI:A41163C212345678:",
    "bt": 1637165561
  },
  {
    "n": "locOrigin",
    "vs": "KPNLORA"
  },
  {
    "n": "latitude",
    "u": "lat",
    "v": 51.794884
  },
  {
    "n": "longitude",
    "u": "lon",
    "v": 4.687986
  },
  {
    "n": "radius",
    "u": "m",
    "v": 319.730194
  },
  {
    "n": "locAccuracy",
    "u": "%",
    "v": 9999
  },
  {
    "n": "locPrecision",
    "u": "%",
    "v": 9999
  },
  {
    "n": "locTime",
    "vs": "1637165561192"
  }
]

+ Location by LoRa On Premises Gateway reception

Add location data to messages that are received by known LoRa On Premise Gateways.

Expected SenML outputs

See above. Output is comparable to LoRa Geolocation data.

› Decoded payload for Device Management

Decoder for Streamline LoRa short payloads, containing firmware version, mode, and battery status.

Expected SenML output attributes

nametype/unitexampledescription

mode

string

active

operation modus (production, active, presales, missing)

batteryVoltage

V

3.58

batteryLevelLow

boolean

false

indicates if the battery voltage has been below the threshold

timeOrigin

string

NETWORK

indicates the origin of the timestamp

firmwareVersion

string

firmware info, only sent after device boot

firmwareCRC

string

firmware info, only sent after device boot

settingsCRC

string

settings info, only sent after device boot

Example SenML messages

[
	{
		"n": "mode",
		"u": "enum",
		"bn": "urn:dev:DEVEUI:7CC6C40512345678:",
		"bt": 1678778462,
		"vs": "active"
	},
	{
		"n": "batteryVoltage",
		"u": "V",
		"v": 3.58
	},
	{
		"n": "batteryLevelLow",
		"vb": false
	},
	{
		"n": "timeOrigin",
		"u": "enum",
		"vs": "NETWORK"
	}
]

The first 10 messages after boot of a device contain firmware information attributes:

[
	{
		"n": "mode",
		"u": "enum",
		"bn": "urn:dev:DEVEUI:7CC6C40512345678:",
		"bt": 1678864786,
		"vs": "active"
	},
	{
		"n": "batteryVoltage",
		"u": "V",
		"v": 3.37
	},
	{
		"n": "batteryLevelLow",
		"vb": false
	},
	{
		"n": "firmwareVersion",
		"vs": "0443"
	},
	{
		"n": "firmwareCRC",
		"vs": "397f"
	},
	{
		"n": "settingsCRC",
		"vs": "a3e5"
	},
	{
		"n": "timeOrigin",
		"u": "enum",
		"vs": "NETWORK"
	}
]

› Decoded payload for Device Management (v2)

Decoder for Streamline LoRa short payloads, containing firmware version, mode, and battery status.

The following SenML records can be present, amongst others:

nametypeunitexampledescription

batteryLevelLow

boolean

false

Indicates if the battery voltage has been below the threshold

batteryVoltage

number

V

firmwareCRC

string

Firmware info, only sent after device boot

firmwareVersion

string

Firmware info, only sent after device boot

mode

string

"active"

Operation modus. Either "production", "active", "presales" or "missing")

settingsCRC

string

Settings info, only sent after device boot

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": "mode",
        "vs": "active"
    },
    {
        "n": "batteryLevelLow",
        "vb": false
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.59
    },
    {
        "n": "firmwareVersion",
        "vs": "0443"
    },
    {
        "n": "firmwareCRC",
        "vs": "397F"
    },
    {
        "n": "settingsCRC",
        "vs": "A3E5"
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

› Decoded payload for Medical Tracker application

Decoder for Streamline LoRa message type 0xD282 containing only temperature and movement bit.

Expected SenML records

nametypeunit

hasMovedSincePreviousTransmission

boolean

/

temperature

number

Cel

› Decoded payload for Medical Tracker application (v2)

Decoder for Streamline LoRa message type 0xD282 containing only temperature and movement bit.

The following SenML records can be present, amongst others:

nametypeunitexampledescription

hasMovedSincePreviousTransmission

boolean

true

temperature

number

Cel

18.875

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": 1633896968.04,
        "n": "temperature",
        "u": "Cel",
        "v": 18.875
    },
    {
        "n": "hasMovedSincePreviousTransmission",
        "vb": true
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

‹ Encoded device modes for Asset Recovery application

  • Protocol: LoRa downlink

  • Description: Send device modes for Asset Recovery: Presales (24h interval), Active (2h interval), Missing (5min interval + BLE), or Inactive.

  • Multiple commands in one downlink: No

Input mapping:

  • Name: mode

    • Value: Presales (translates into → 150098078051010080510115013F01001501FB018016)

    • Value: Active (translates into → 15009807201C0000201C0015013F01001501FB014016)

    • Value: Missing (translates into → 15009807F0000000F0000015013907000000000000001501FB01C1150402010115040E010015042C02050516)

    • Value: Inactive (translates into → 14009808FFFFFFFFFFFFFFFF110000000001000000)

Last updated