LogoLogo
  • KPN THINGS USER GUIDE
    • Introduction
    • Getting started
      • Registration and setup
      • Device simulator app
      • Connect devices
        • SIM cards
        • Supported devices and KPN Devices
        • SODAQ R412M
        • Smartrak
        • Marvin development board
        • LoPy5
        • Arduino MKR WAN 1300/1310
        • Arduin MKR NB 1500
    • All videos
    • Tutorials
      • Configure a flow
      • Connect a HTTPs destination
      • Create a simple IoT web applicationPage
      • Send instruction to LoRa DevicePage
      • Send your data to Azure SQL
      • Technical overview
        • Management data model
        • Uplink communication
        • Downlink communication
        • Location data
      • Accounts and projects
        • Customer accounts and users
        • Projects
        • Customer management
        • Cost overview and contract
    • Frequently asked
      • Multi Factor Authentication
  • GENERAL FUNCTIONS
    • Quick reference videos
    • APIs
  • THE PORTAL EXPLAINED
    • Things Manager
      • Devices
        • Bulk operations
      • Data
        • Device data graph
      • Connectivity
        • LoRa connectivity configuration
      • Bulk reports
    • Things Creator
    • Support
      • News
      • Release notes
      • Real-time status
      • Service reports
      • Documents
      • Support tickets
      • Invoices
      • Contact info
    • Shop
  • BUILDING BLOCKS
    • Devices
      • Sensors
        • KPN Conditionsensor CO2 II
        • KPN Conditionsensor CO2 III
        • KPN Conditionsensor CO2 III motionPage 1
        • KPN FillTag I
        • KPN FillTag II
        • 1M2M ED1608
        • Elsys ERS
        • Device Simulator (Mobile Phone app)
        • Generic Device (Internet connected)
        • Generic LoRa device (preset connectivity)
        • Generic LoRa device (programmable)
        • Generic M2M device
        • Generic M2M device (with Internet connection)
      • Trackers
        • KPN Global Tracker Autonomous
        • KPN Global Tracker Wired
        • KPN LocationTag I
        • KPN LocationTag II
        • KPN LocationTag II v2
        • KPN LocationTag II v2 Expert Mode
        • KPN LocationTag II v3
        • KPN LocationTag III (with GPS)
        • KPN LocationTag III (without GPS)
        • KPN LocationTag III v2
        • KPN LocationTag III v2 Buffer
        • KPN LocationTag III v3
        • KPN LocationTag III v4
        • KPN LocationTag V
        • KPN LocationTag VI
        • KPN LocationTag WS
        • Streamline LoRa
        • Streamline M2M
        • Viloc
      • Routers
      • Gateways
        • KPN FSK Basestation
      • Device SDK
    • Connectivity
      • Connecting LoRa devices
        • LoRa connectivity configuration
      • Connecting M2M devices
      • Connecting Internet devices
      • Connecting MQTT Devices
    • Data Processing
      • ThingsML and SenML
        • ThingsML
        • SenML
          • Understanding and Interpreting SenML Data
          • Changes in KPN SenML
      • Device Twin
      • Decoders and encoders
        • Common measurements list
        • Decoder migrations
        • DIY Decoder
          • DIY decoder scripts
      • Merger
      • Device data
      • Devices
    • Destinations
      • HTTPS destination
      • MQTT broker
      • Cumulocity IoT Platform
      • Azure Event Hubs
      • Azure IoT Hub
      • Test Endpoint
      • ThingsBoard
      • Datacake
      • AWS Lambda
      • Google Cloud Run functions
  • IOT LINE UP
    • Freemium
      • Test SIM cards
    • Explorer
    • Modular
    • Tailored
    • Terms and Conditions
Powered by GitBook

© 2024 KPN - All rights reserved.

On this page
  • + LoRa Geolocation data
  • + Location by LoRa On Premises Gateway reception
  • › Decoded payload for Device Management
  • › Decoded payload for Device Management (v2)
  • › Decoded payload for Medical Tracker application
  • › Decoded payload for Medical Tracker application (v2)
  • ‹ Encoded device modes for Asset Recovery application

Was this helpful?

Export as PDF
  1. BUILDING BLOCKS
  2. Devices
  3. Trackers

KPN LocationTag II

PreviousKPN LocationTag INextKPN LocationTag II v2

Last updated 5 months ago

Was this helpful?

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

Decoders
decoderSpecificationUUID
Description

+ LoRa Geolocation data

d2593092-bc42-4b84-a053-2301f499bbc4

+ Location by LoRa On Premises Gateway reception

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

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

Encoders
encoderSpecificationUUID
Description

‹ 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

Expected SenML outputs

name
type/unit
example
description

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

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

name
type/unit
example
description

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:

name
type
unit
example
description

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

[
    {
        "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

name
type
unit

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:

name
type
unit
example
description

hasMovedSincePreviousTransmission

boolean

true

temperature

number

Cel

18.875

Example SenML

[
    {
        "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)

Add data to messages where location could be calculated.

Add location data to messages that are received by known .

Add data to messages where location could be calculated.

Add location data to messages that are received by known .

This decoder also decodes 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 .

This decoder also decodes 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 .

LoRa Geolocation
LoRa On Premise Gateways
Geolocation and Local Gateway
Understanding and Interpreting SenML Data
Geolocation and Local Gateway
Understanding and Interpreting SenML Data
LoRa Geolocation
LoRa On Premise Gateways