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 Asset Tracking
  • › Decoded payload for Asset Tracking (v2)
  • › Decoded payload for counting rotations
  • › Decoded payload for counting rotations (v2)
  • ‹ Encoded device commands

Was this helpful?

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

KPN LocationTag II v2

PreviousKPN LocationTag IINextKPN LocationTag II v2 Expert Mode

Last updated 5 months ago

Was this helpful?

KPN LocationTag II v2

Tag for localization and movement monitoring. Revision of KPN LocationTag II. Added functionality NFC and FSK.

  • Supported network type(s): KPNLORA

  • Device Specification ID: kpn-locationtag-ii-v2

  • Device Specification UUID: 43d4122f-b2ce-486b-9ede-d5463d2a822d

Decoders
decoderSpecificationUUID
Description

+ LoRa Geolocation data

19e12863-ad65-4fb7-a812-e6744be290d0

+ Location by LoRa On Premises Gateway reception

fa3928a9-8217-48a1-a3a6-1dcc945b4bb3

› Decoded payload for Asset Tracking

040627e5-0254-45ca-a0e1-cafab4c8b775

Decoder for Streamline LoRa short and long payloads containing a.o. NFC field detected flag, sabotaged flag, motion status, and battery voltage. Long payloads also contain a.o. firmware, power up, and transmission time.

› Decoded payload for Asset Tracking (v2)

1e530f69-1c43-54da-bc77-f3508486c21e

Decoder for Streamline LoRa short and long payloads containing a.o. NFC field detected flag, sabotaged flag, motion status, and battery voltage. Long payloads also contain a.o. firmware, power up, and transmission time.

› Decoded payload for counting rotations

10cf0159-822c-4039-a641-59d23cc38f49

Decoder outputting general information and specific rotation and orientation data

› Decoded payload for counting rotations (v2)

2aeeaef5-fb56-5b07-9675-58d568dc708f

Decoder outputting general information and specific rotation and orientation data

Encoders
encoderSpecificationUUID
Description

‹ Encoded device commands

9935fa32-6915-4fe9-b864-37e9913a97f9

Set the device mode and enabling of nfc writes.

+ 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 Asset Tracking

Decoder for Streamline LoRa short and long payloads containing a.o. NFC field detected flag, sabotaged flag, motion status, and battery voltage. Long payloads also contain a.o. firmware, power up, and transmission time.

Expected SenML outputs

name
type/unit
example
description

nfcFieldDetected

boolean

false

acceleratorActive

boolean

true

sabotaged

boolean

false

movementIndication

string

STATIONARY

indicates the devices movement status (STOP, STATIONARY, START, MOVING)

alarmMode

boolean

false

batteryVoltage

V

3.5

motionTime

min

2

temperature

Cel

21.0

firmwareVersion

only sent in long payload messages

firmwareCRC

only sent in long payload messages

settingsCRC

only sent in long payload messages

nfcState

only sent in long payload messages

RESERVED, NFC_READ_ONLY, NFC_OFF, NFC_RW

powerupTime

min

only sent in long payload messages

transmissionTime

s

only sent in long payload messages

nrOfLoraTransmissions

only sent in long payload messages

timeOrigin

string

NETWORK

indicates the origin of the timestamp

Example SenML message

[
	{
		"bn": "urn:dev:DEVEUI:7CC6C43012345678:",
		"bt": 1678778476
	},
	{
		"n": "nfcFieldDetected",
		"vb": false
	},
	{
		"n": "acceleratorActive",
		"vb": true
	},
	{
		"n": "sabotaged",
		"vb": false
	},
	{
		"n": "movementIndication",
		"vs": "STATIONARY"
	},
	{
		"n": "alarmMode",
		"vb": false
	},
	{
		"n": "batteryVoltage",
		"u": "V",
		"v": 2.96
	},
	{
		"n": "motionTime",
		"u": "min",
		"v": 39981.0
	},
	{
		"n": "temperature",
		"u": "Cel",
		"v": 15.0
	},
	{
		"n": "timeOrigin",
		"u": "enum",
		"vs": "NETWORK"
	}
]

› Decoded payload for Asset Tracking (v2)

Decoder for Streamline LoRa short and long payloads containing a.o. NFC field detected flag, sabotaged flag, motion status, and battery voltage. Long payloads also contain a.o. firmware, power up, and transmission time.

The following SenML records can be present, amongst others:

name
type
unit
example
description

acceleratorActive

boolean

true

alarmMode

boolean

true

batteryVoltage

number

V

3.56

firmwareCRC

string

"9e17"

Only sent in long payload messages

firmwareVersion

string

"0604"

Only sent in long payload messages

motionTime

number

min

142271.0

movementIndication

string

"STOP"

Indicates the devices movement status. Either "STOP, "STATIONARY", "START" or "MOVING"

nfcFieldDetected

boolean

true

nfcState

string

"RESERVED"

Only sent in long payload messages. Either "RESERVED", "NFC_READ_ONLY", "NFC_OFF", or "NFC_RW"

nrOfLoraTransmissions

number

7427.0

Only sent in long payload messages

powerupTime

number

min

1334707

Only sent in long payload messages

sabotaged

boolean

true

settingsCRC

string

"a3e5"

Only sent in long payload messages

temperature

number

Cel

23.432

transmissionTime

number

s

5180

Only sent in long payload messages

Example SenML

Short payload

[
    {
        "bn": "urn:dev:DEVEUI:0123456789012345:",
        "bt": 1693136532.83,
        "n": "nfcFieldDetected",
        "vb": false
    },
    {
        "n": "acceleratorActive",
        "vb": true
    },
    {
        "n": "sabotaged",
        "vb": true
    },
    {
        "n": "movementIndication",
        "vs": "START"
    },
    {
        "n": "alarmMode",
        "vb": true
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 2.96
    },
    {
        "n": "motionTime",
        "u": "min",
        "v": 22756
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": -8
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

Long payload

[
    {
        "bn": "urn:dev:DEVEUI:0123456789012345:",
        "bt": 1693136532.83,
        "n": "nfcFieldDetected",
        "vb": false
    },
    {
        "n": "acceleratorActive",
        "vb": true
    },
    {
        "n": "sabotaged",
        "vb": false
    },
    {
        "n": "movementIndication",
        "vs": "STATIONARY"
    },
    {
        "n": "alarmMode",
        "vb": false
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.01
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": 1
    },
    {
        "n": "firmwareVersion",
        "vs": "06a9"
    },
    {
        "n": "firmwareCRC",
        "vs": "ac01"
    },
    {
        "n": "settingsCRC",
        "vs": "ec36"
    },
    {
        "n": "nfcState",
        "vs": "NFC_READ_ONLY"
    },
    {
        "n": "motionTime",
        "u": "min",
        "v": 18418
    },
    {
        "n": "powerupTime",
        "u": "min",
        "v": 1156219
    },
    {
        "n": "transmissionTime",
        "u": "s",
        "v": 4142
    },
    {
        "n": "nrOfLoraTransmissions",
        "v": 3255
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

› Decoded payload for counting rotations

Decoder outputting general information and specific rotation and orientation data

Expected SenML records

name
type
unit

acceleratorActive

boolean

alarmMode

boolean

batteryVoltage

number

V

firmwareCRC

string

firmwareVersion

string

movementIndication

string

enum

nfcFieldDetected

boolean

enum

nfcState

string

enum

nrOfLoraTransmissions

number

orientationX

number

orientationY

number

powerupTime

number

min

rotationCount

number

rotationLeft

number

rotationRight

number

sabotaged

boolean

settingsCRC

string

temperature

number

Cel

transmissionTime

number

s

› Decoded payload for counting rotations (v2)

Decoder outputting general information and specific rotation and orientation data

Fixes from '› Decoded payload for counting rotations':

  • For the field nfcState, the values"NFC_READ_ONLY" & "NFC_OFF" were swapped.

The following SenML records can be present, amongst others:

name
type
unit
example
description

acceleratorActive

boolean

true

alarmMode

boolean

false

batteryVoltage

number

V

3.03

firmwareCRC

string

"3407"

Not present in detail level 1 messages

firmwareVersion

string

"06b0"

Not present in detail level 1 messages

movementIndication

string

"STATIONARY"

Indicates the devices movement status. Either "STOP", "STATIONARY", "START" or "MOVING"

nfcFieldDetected

boolean

false

nfcState

string

"NFC_READ_ONLY"

Not present in detail level 1 messages. Either "RESERVED", "NFC_READ_ONLY", "NFC_OFF" or "NFC_RW"

nrOfLoraTransmissions

number

27

Not present in detail level 1 messages

orientationX

number

21

Only present in detail level 3 messages

orientationY

number

7

Only present in detail level 3 messages

powerupTime

number

min

184996

Not present in detail level 1 messages

rotationCount

number

2

rotationLeft

number

1

Only present in detail level 3 messages

rotationRight

number

3

Only present in detail level 3 messages

sabotaged

boolean

false

settingsCRC

string

"42b5"

Not present in detail level 1 messages

temperature

number

Cel

24.3

transmissionTime

number

s

67

Not present in detail level 1 messages

Example SenML

[
    {
        "bn": "urn:dev:DEVEUI:0123456789012345:",
        "bt": 1693136532.83,
        "n": "nfcFieldDetected",
        "vb": false
    },
    {
        "n": "acceleratorActive",
        "vb": true
    },
    {
        "n": "sabotaged",
        "vb": false
    },
    {
        "n": "movementIndication",
        "vs": "STATIONARY"
    },
    {
        "n": "alarmMode",
        "vb": false
    },
    {
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.03
    },
    {
        "n": "rotationCount",
        "v": 2.0
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": -24.0
    },
    {
        "n": "firmwareVersion",
        "vs": "06b0"
    },
    {
        "n": "firmwareCRC",
        "vs": "3407"
    },
    {
        "n": "settingsCRC",
        "vs": "42b5"
    },
    {
        "n": "nfcState",
        "vs": "NFC_READ_ONLY"
    },
    {
        "n": "powerupTime",
        "u": "min",
        "v": 184996.0
    },
    {
        "n": "transmissionTime",
        "u": "s",
        "v": 67.0
    },
    {
        "n": "nrOfLoraTransmissions",
        "v": 27.0
    },
    {
        "n": "rotationLeft",
        "v": 1.0
    },
    {
        "n": "rotationRight",
        "v": 3.0
    },
    {
        "n": "orientationX",
        "v": 21.0
    },
    {
        "n": "orientationY",
        "v": 7.0
    },
    {
        "n": "timeOrigin",
        "vs": "NETWORK"
    }
]

‹ Encoded device commands

  • Protocol: LoRa downlink

  • Description: Set the device mode and enabling of nfc writes.

  • Multiple commands in one downlink: No

Input mapping:

  • Name: mode

    • Value: Missing (translates into → 118000000080000000)

  • Name: deviceControl

    • Value: Reset (translates into → 0200)

    • Value: NFC_Write (translates into → 1B11FA1816)

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