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
  • › Decoded payload
  • + Location by LoRa On Premises Gateway reception
  • + LoRa Geolocation data
  • › Decoded payload v2
  • › Encoded payload

Was this helpful?

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

KPN LocationTag I

PreviousKPN Global Tracker WiredNextKPN LocationTag II

Last updated 5 months ago

Was this helpful?

KPN LocationTag I

Also known as Viloc Tag.

  • Supported network type(s): KPNLORA

  • Device Specification ID: kpn-locationtag-i

  • Device Specification UUID: 00338b9a-25f8-43e5-ba36-7555bc00ad83

Decoders
decoderSpecificationUUID
Description

› Decoded payload

84e9d55d-28b3-43c2-9b2d-80ebce35222f

Decoder outputting sabotage flag and temperature reading.

+ Location by LoRa On Premises Gateway reception

8ae50706-4ad1-4823-90c8-4db166180846

+ LoRa Geolocation data

c2f529b3-a1e2-417e-a1f8-2269f4245af1

› Decoded payload v2

fa85c8cb-0f64-58c5-beea-69c94c55fc0e

Decoder for Viloc payloads.

Encoders
encoderSpecificationUUID
Description

‹ Encoded device modes or send interval

15575b9a-4a5f-4445-9417-4b7a56080f20

Send device modes for Asset Recovery: Active (5h interval), Missing (5min interval), or change send interval.

› Decoded payload

  • UUID: 84e9d55d-28b3-43c2-9b2d-80ebce35222f

  • Description: Decoder outputting sabotage flag and temperature reading.

  • Exchange: decoder.lora.viloc.exchange

Expected SenML outputs

name
type/unit
description
example

temperature

Cel

21.0

sabotaged

boolean

indicates if the device has been sabotaged

false

batteryLevelLow

boolean

indicates if the battery voltage has been below the threshold

false

Example Message

Note: batteryLevelLow is sent only once per day

[
	{
		"bn": "urn:dev:DEVEUI:B12363D23123C123:",
		"bt": 1678778493
	},
	{
		"n": "temperature",
		"u": "Cel",
		"v": 21.0
	},
	{
		"n": "sabotaged",
		"vb": false
	},
	{
		"n": "batteryLevelLow",
		"vb": false
	}
]

+ Location by LoRa On Premises Gateway reception

  • UUID: 8ae50706-4ad1-4823-90c8-4db166180846

  • Exchange: decoder.lora.lrr.exchange

Expected SenML outputs

See below. Output is comparable to LoRa Geolocation data.

+ LoRa Geolocation data

  • UUID: c2f529b3-a1e2-417e-a1f8-2269f4245af1

  • Exchange: decoder.location.data.kpn.actility.exchange

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

together with latitude and longitude this defines the area where the device is expected to be located

locAccuracy

%

locPrecision

%

locTime

timestamp

1637165561

unix timestamp (in s) of the localization

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"
  }
]

› Decoded payload v2

Decoder for Viloc payloads.

name
type
description
example

sabotaged

boolean

indicates if the device has been sabotaged

false

temperature

number

the temperature measured by the device

14

batteryLevelLow

boolean

indicates if the battery voltage has been below the threshold

false

Example SenML-message

The batteryLevelLow field in the example below is optional and will not be present in every uplink.

[
    {
        "bn": "6E5E267F2E6FB3BF",
        "bt": 1693136532.0,
        "n": "sabotaged",
        "vb": false
    },
    {
        "n": "temperature",
        "u": "Cel",
        "v": 29
    },
    {
        "n": "batteryLevelLow",
        "vb": true
    }
]

› Encoded payload

= Raw LoRa payload

  • Protocol: LoRa downlink

  • Description: Send raw LoRa payload to your device.

  • Multiple commands in one downlink: No

Input mapping:

  • Name: payloadHex (raw input)

‹ Encoded device modes or send interval

  • Protocol: LoRa downlink

  • Description: Send device modes for Asset Recovery: Active (5h interval), Missing (5min interval), or change send interval.

  • Multiple commands in one downlink: No

Input mapping:

  • Name: mode

    • Value: Active (translates into → 010000646400D100C700DADA, 02D180AA00C40784038405840484060A14)

    • Value: Missing (translates into → 010000646400E1008600DADA, 02E180AA00C0077B0380057B047B060A147B0214091F0C1F0E010088)

  • Name: interval

    • Value: 1h (translates into → 010000646400E1008600DADA, 02E180AA00C0077B0380057B047B060A147B0214091F0C1F0E010088)

    • Value: 2h (translates into → 010000646400CD00CD00DADA, 02CD80AA00C20781038105810481060A14)

    • Value: 5h (translates into → 010000646400D100C700DADA, 02D180AA00C40784038405840484060A14)

    • Value: 11h (translates into → 010000646400D3005600DADA, 02D380AA00C4078A038A058A048A061914)

Add location data to messages that are received by known .

Add data to messages where location could be calculated.

Description: Add location data to messages that are received by known .

Description: Add data to messages where location could be calculated.

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 On Premise Gateways
LoRa Geolocation
Geolocation and Local Gateway
Understanding and Interpreting SenML Data
LoRa On Premise Gateways
LoRa Geolocation