For the complete documentation index, see llms.txt. This page is also available as Markdown.

KPN LocationTag III v2

KPN LocationTag III v2

Streamline device configured to be used as Rotation Counter.

  • Supported network type(s): KPNLORA

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

  • Device Specification UUID: 65f45046-10e5-4b97-9367-7f3f7a3fd7bd

Decoders
decoderSpecificationUUID
Description

› Decoded payload for Asset Tracking application (v2)

dd211ae8-f914-5eb2-8db8-319f46901822

Decoder for Streamline lora messages encoded as P3K3 (loctagiiiv2) with RotationCount (byte length 2-49).

› Decoded payload with location and rotation counter (p3k3) (v2)

96eb6d63-b272-5551-a4fb-f435f2130a17

Decoder for Streamline lora messages encoded as P3K3 (loctagiiiv2) with RotationCount (byte length 2-49).

› Decoded payload for Asset Tracking application (v2)

Decoder for Streamline lora messages encoded as P3K3 (loctagiiiv2) with RotationCount (byte length 2-49).

This decoder also decodes Geolocation and Local Gateway data.

The following SenML records can be present, amongst others:

name
type
unit
example
description

batteryVoltage

number

V

devEui

string

Not present in detail level 1 messages

DvLat

number

lat

Latitude

DvLon

number

lon

Longitude

firmwareCRC

string

Not present in detail level 1 messages

firmwareVersion

string

Not present in detail level 1 messages

gpsActiveStill

boolean

true

gpsFixStill

boolean

true

gpsModuleActive

boolean

true

Not present in detail level 1 messages

nfcScanned

boolean

true

nfcState

string

Not present in detail level 1 messages

nrOfLoraTransmissions

number

Not present in detail level 1 messages

orientationX

number

Not present in detail level 1 messages

orientationY

number

Not present in detail level 1 messages

powerupTime

number

min

Not present in detail level 1 messages

rotationCount

number

rotationLeft

number

Not present in detail level 1 messages

rotationRight

number

Not present in detail level 1 messages

settingsCRC

string

Not present in detail level 1 messages

status

string

Not present in detail level 1 messages

temperature

number

Cel

18.334

transmissionTime

number

s

Not present in detail level 1 messages

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.

› Decoded payload with location and rotation counter (p3k3) (v2)

Decoder for Streamline lora messages encoded as P3K3 (loctagiiiv2) with RotationCount (byte length 2-49).

This decoder also decodes Geolocation and Local Gateway data.

The following SenML records can be present, amongst others:

name
type
unit
example
description

batteryVoltage

number

V

2.96

devEui

string

"0123456789012345"

not present in detail level 1 messages

firmwareCRC

string

"2143"

not present in detail level 1 messages

firmwareVersion

string

"cdab"

not present in detail level 1 messages

gpsActiveStill

boolean

true

gpsFixStill

boolean

true

gpsModuleActive

boolean

true

not present in detail level 1 messages

latitude

number

lat

51.90717

longitude

number

lon

4.48940

nfcScanned

boolean

true

nfcState

string

"NFC_RW"

not present in detail level 1 messages

nrOfLoraTransmissions

number

not present in detail level 1 messages

orientationX

number

255.0

not present in detail level 1 messages

orientationY

number

1.0

not present in detail level 1 messages

powerupTime

number

min

not present in detail level 1 messages

rotationCount

number

266

rotationLeft

number

33.0

not present in detail level 1 messages

rotationRight

number

29.0

not present in detail level 1 messages

settingsCRC

string

"7698"

not present in detail level 1 messages

status

string

"9a"

not present in detail level 1 messages

temperature

number

Cel

21.0

transmissionTime

number

s

not present in detail level 1 messages

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.

14 byte payload

49 byte payload

Last updated

Was this helpful?