KPN FSK Basestation

FSK Gateway

FSK Gatewayreports attach and detach events.

  • Supported network type(s): KPNM2M,KPNSTREAMLINEM2M

  • Device Specification ID: kpn-fsk-gateway

  • Device Specification UUID: 36c2a679-9ad5-473a-b2b4-2280c8806216

Decoders
decoderSpecificationUUID
Description

› Decoded payload for fsk gateway

d1a91443-1362-476e-9037-ef2dcdd7a7c2

Decoder for Streamline FSK Gateway.

› Decoded payload for fsk gateway (v2)

eb19583e-5d96-5107-af90-14ed7d1544cf

Decoder for Streamline FSK Gateway.

› Decoded payload for fsk gateway

Decoder for Streamline FSK Gateway.

Expected SenML records

name
type
unit

Altitude

number

m

AltitudeMargin

number

m

DvLat

number

lat

DvLon

number

lon

Event

string

Event:Device:DEVEUI

string

Event:Device:Serialnumber

string

FirmwareVersion

string

Version

GpsTime

number

s

LatLonMargin

number

Margin

› Decoded payload for fsk gateway (v2)

Decoder for Streamline FSK Gateway.

The following SenML records can be present, amongst others:

name
type
unit
example
description

FirmwareVersion

string

GpsTime

number

s

1698912211.2

DvLat

number

lat

Latitude

DvLon

number

lon

Longitude

Event

string

"attach"

LatLonMargin

number

m

Altitude

number

m

AltitudeMargin

number

m

Event:Device:Serialnumber

string

Event:Device:DEVEUI

string

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.

[
  {
    "bn": "urn:dev:IMEI:999999999000090:",
    "bt": 1664818024.4,
    "n": "Event",
    "vs": "attach"
  },
  {
    "n": "Event:Device:DEVEUI",
    "vs": "7CC6C43000024935"
  },
  {
    "n": "Event:Device:Serialnumber",
    "vs": "0B00300002493501"
  },
  {
    "n": "GpsTime",
    "u": "s",
    "v": 1698912211.2
  }
]

Last updated

Was this helpful?