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 Streamline M2M data
  • › Decoded Streamline M2M data (v2)

Was this helpful?

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

Streamline M2M

PreviousStreamline LoRaNextViloc

Last updated 5 months ago

Was this helpful?

Streamline M2M

For all streamline M2M devices.

  • Supported network type(s): KPNSTREAMLINEM2M

  • Device Specification ID: supported-streamline-m2m

  • Device Specification UUID: 1ee3544d-1f5e-4d70-aba7-b50e80bad402

Decoders
decoderSpecificationUUID
Description

› Decoded Streamline M2M data

cf36febd-ba2e-4d1b-bbda-da4b6dbf2ca3

Decoder for selection of Streamline M2M data.

› Decoded Streamline M2M data (v2)

b5becc8a-ff52-5d2d-85ee-42b03a852bc4

Decoder for selection of Streamline M2M data.

› Decoded Streamline M2M data

Decoder for selection of Streamline M2M data.

Expected SenML records

name
type
unit

accelerationX

number

m/s2

accelerationY

number

m/s2

accelerationZ

number

m/s2

altitude

number

m

altitudeMargin

number

m

batteryVoltage

number

V

firmwareVersion

string

string

gpsTime

number

s

gsmNetworkId

string

string

heading

number

rad

latitude

number

lat

longitude

number

lon

phoneNumber

string

string

radius

number

m

temperature

number

Cel

velocity

number

m/s

› Decoded Streamline M2M data (v2)

Decoder for selection of Streamline M2M data.

The following SenML records can be present, amongst others:

name
type
unit
example
description

batteryVoltage

number

V

3.59

firmwareVersion

string

"474"

gpsTime

number

s

1664810842.4

heading

number

rad

0.7148868616168774

latitude

number

lat

51.90717

longitude

number

lon

4.48940

radius

number

m

velocity

number

m/s

Example SenML

[
    {
        "bn": "urn:dev:IMEI:999999999000090:",
        "bt": 1664810824.4,
        "n": "batteryVoltage",
        "u": "V",
        "v": 3.62
    },
    {
        "n": "firmwareVersion",
        "vs": "474"
    },
    {
        "n": "gpsTime",
        "u": "s",
        "v": 1664810842.4
    },
    {
        "n": "heading",
        "u": "rad",
        "v": 0.7148868616168774
    },
    {
        "n": "latitude",
        "u": "lat",
        "v": 51.90717
    },
    {
        "n": "longitude",
        "u": "lon",
        "v": 4.48940
    },
    {
        "n": "radius",
        "u": "m",
        "v": 0
    },
    {
        "n": "velocity",
        "u": "m/s",
        "v": 0
    }
]

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 .

Geolocation and Local Gateway
Understanding and Interpreting SenML Data