KPN LocationTag WS
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
Decoders | decoderSpecificationUUID | Description |
---|---|---|
+ LoRa Geolocation data |
| Add LoRa Geolocation data to messages where location could be calculated. |
= Raw LoRa payload |
| Forward the raw LoRa payload and port number without decoding. |
= Raw LoRa payload (v2) |
| Forward the raw LoRa payload and port number without decoding. |
= Raw LoRa payload Extended |
| Forward the raw LoRa payload and other metadata without decoding. |
= Raw LoRa payload Extended (v2) |
| Forward the raw LoRa payload and lora network metadata without decoding. |
› Decoded payload with WiFi scan results |
| Decoder for Streamline LoRa message type 0xF1. |
› Decoded payload with WiFi scan results (v2) |
| Decoder for Streamline LoRa message type 0xF1. |
+ LoRa Geolocation data
Add LoRa Geolocation data to messages where location could be calculated.
= Raw LoRa payload
Forward the raw LoRa payload and port number without decoding.
Expected SenML records
name | type | unit |
---|---|---|
payload | string | |
port | number |
= Raw LoRa payload (v2)
Forward the raw LoRa payload and port number without decoding.
The following SenML records can be present, amongst others:
name | type | unit | example | description |
---|---|---|---|---|
payload | string |
| The LoRa hex payload | |
port | number |
| The LoRa port used to send this uplink |
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.
= Raw LoRa payload Extended
Forward the raw LoRa payload and other metadata without decoding.
Expected SenML records
name | type | unit |
---|---|---|
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 |
Raw LoRa payload Extended (v2)
Forward the raw LoRa payload and lora network metadata without decoding.
Fixes from '= Raw LoRa payload Extended':
LrrRSSI
is changed to anumber
.LrrSNR
is changed to anumber
.LrrESP
is changed to anumber
.
The following SenML records can be present, amongst others:
name | type | unit | example | description |
---|---|---|---|---|
ADRbit | number |
| Adaptive Data Rate indicator | |
Channel | string |
| Lora channel of the transmission | |
DevLrrCnt | number |
| Amount of gateways that received the message | |
FCntDn | number |
| The downlink framecounter | |
FCntUp | number |
| The uplink framecounter | |
LrrRSSI | number |
| Received Signal Strength Indicator | |
LrrSNR | number |
| Signal to Noise Ratio | |
payload | string |
| raw hex payload string | |
port | number |
| LoRa port used | |
SpFact | number |
| Spreading factor used | |
SubBand | string |
| Lora band of the transmission |
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 WiFi scan results
Decoder for Streamline LoRa message type 0xF1.
› Decoded payload with WiFi scan results (v2)
Decoder for Streamline LoRa message type 0xF1.
The following SenML records can be present, amongst others:
name | type | unit | example | description |
---|---|---|---|---|
batteryLevelLow | boolean |
| 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 |
| Operation modus. Either | |
settingsCRC | string | Settings info, only sent after device boot |
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.
Last updated