KPN LocationTag WS
Last updated
Last updated
© 2024 KPN - All rights reserved.
A small device using WiFi scanning for localisation.
Supported network type(s): KPNLORA
Device Specification ID: kpn-locationtag-ws
Device Specification UUID: 2c05af48-434e-4806-a0f3-837360f4f3cb
+ LoRa Geolocation data
decc2f80-10b3-4c7c-8a47-a2f704272e6e
Add LoRa Geolocation data to messages where location could be calculated.
= Raw LoRa payload
a1125bd2-1aaf-4284-b866-72e91a1a6862
Forward the raw LoRa payload and port number without decoding.
= Raw LoRa payload (v2)
2186c46a-04b7-5f24-a0ab-c46ebbd009f9
Forward the raw LoRa payload and port number without decoding.
= Raw LoRa payload Extended
3a1af5c6-6499-48a0-b3ff-682e5e496cea
Forward the raw LoRa payload and other metadata without decoding.
= Raw LoRa payload Extended (v2)
049ef907-3732-586e-b638-cdaddafa66c9
Forward the raw LoRa payload and lora network metadata without decoding.
› Decoded payload with WiFi scan results
94fb4c11-6d05-481d-b3e6-58a86c2bcea6
Decoder for Streamline LoRa message type 0xF1.
› Decoded payload with WiFi scan results (v2)
94b73332-ff18-59e5-873a-5ef7e8fad583
Decoder for Streamline LoRa message type 0xF1.
Add LoRa Geolocation data to messages where location could be calculated.
Forward the raw LoRa payload and port number without decoding.
Expected SenML records
payload
string
port
number
Forward the raw LoRa payload and port number without decoding.
This decoder also decodes Geolocation and Local Gateway data.
The following SenML records can be present, amongst others:
payload
string
"4D985C495AC4D8C9682CFD"
The LoRa hex payload
port
number
200
The LoRa port used to send this uplink
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.
Forward the raw LoRa payload and other metadata without decoding.
Expected SenML records
ADRbit
number
Channel
string
DevLrrCnt
number
FCntDn
number
FCntUp
number
FPort
number
LrrESP
string
LrrRSSI
string
LrrSNR
string
SpFact
number
SubBand
string
payload_hex
string
Forward the raw LoRa payload and lora network metadata without decoding.
Fixes from '= Raw LoRa payload Extended':
LrrRSSI
is changed to a number
.
LrrSNR
is changed to a number
.
LrrESP
is changed to a number
.
This decoder also decodes Geolocation and Local Gateway data.
The following SenML records can be present, amongst others:
ADRbit
number
0
Adaptive Data Rate indicator
Channel
string
LC255
Lora channel of the transmission
DevLrrCnt
number
0
Amount of gateways that received the message
FCntDn
number
21725
The downlink framecounter
FCntUp
number
30117
The uplink framecounter
LrrRSSI
number
0
Received Signal Strength Indicator
LrrSNR
number
0
Signal to Noise Ratio
payload
string
"4D985C495AC4D8C9682CFD"
raw hex payload string
port
number
1
LoRa port used
SpFact
number
9
Spreading factor used
SubBand
string
"G0"
Lora band of the transmission
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.
Decoder for Streamline LoRa message type 0xF1.
Decoder for Streamline LoRa message type 0xF1.
This decoder also decodes Geolocation and Local Gateway data.
The following SenML records can be present, amongst others:
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
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.