2. Create your first Destination

Go to the Flows > My first flow and click Link destination

Choose Create a new Destination.

Select HTTPS endpoint as destination type.

3. Fill in your Destination Information

After selecting HTTPS Endpoint, fill in the following information:

• Destination name: you can think of a good recognisable name for your first destination, like My First Destination.

• URL: this should be the URL you just copied from webhook.site.

• Shared secret: this is a kind of password that an application should use to verify that KPN Things sent the data to the endpoint. It should be at least 32 characters long and should contain at least an uppercase character, lowercase character, digit, and special character.

4. Test connection with test message

Send a test message, e.g. by using the Device simulator app. You should see incoming information on your webhook.

Congratulations! 🎉

You successfully set up your first IoT solution!

To continue learning you can continue with:

2. Link Device to Flow

Click on Add Devices in the Flow overview page.

Now you see all Devices you can add to this Flow. Click on your Device to link it to the Flow.

Now your Device is linked to the Flow!

3. Activate a Decoder

Open your Project, open your Flow, and then click Data Processing.

Click on the Device type for which you want to activate a decoder (#1 in the screenshot below). At this moment you probably have only one type of device linked to the Flow, so open that one. All available decoders are now shown (#2 in the screenshot below).

Here you can toggle on and off what (decoded) data you want to receive in your application (like indicated with #3 in the screenshot below). If you want to know more about the decoder, click on the link in the description.

Note that the "Add new Decoder" button and "Edit" button are only visibleif this is your own device type. Own Device Types and Decoders can be created using the Things Creator app.

Add the Device Simulator Web app

Follow the steps to add the Device Simulator Web app as a device.

Or connect your own test devices with our other device templates.

This video explains how the User Interface and main navigation works.

Tables

This video explains how Tables work.

Bulk by multiselect

This video explains how Bulk by multiselect works in the User Interface.

Bulk by file

This video explains how Bulk by file works in the User Interface.

Once you have registered you have a developer account. With this account you get a Freemium project. Here you can test LoRa and M2M connectivity for a limited number of devices for free.

Follow our step-by-step guide to further set up the environment.

KPN Things Explorer

You can easily upgrade this registration to a paid subscription later. This is our low threshold Explorer solution and suitable for even a couple of devices.

KPN Things Modular

An account will be created for you and you will receive an email to create a password. This is out dynamic solutions based on standard building blocks suitable for high-volumes.

KPN Things or Tailored

Accounts will be created for you and you will receive an email to create a password. This is our customized connectivity focussed solutions suitable for high-volumes.

Want to learn more about our propositions

KPN Things is available in four distinct propositions.

This video explains how Bulk by file works in the User Interface.

Device Type Overview

Within the Things Creator application navigate to Device-Type Management: Click on the new main menu item "All Device Types". View the overview of all available device types.

Create New Device Type

Click on the "Add new Device Type" button. Fill in the required information for the new device type, such as name, description, and any specific properties. Click "Add Device Type" to add the new device type.

Edit or Delete Device Type

If needed, you can edit or delete your own device types through the device type overview. Select the device type from the list and in the device type detail page, click Edit or Delete.

After creating your own device-type, this device-type can be selected in the Things Manager when adding new devices to your project.

Step 2: Creating a New Decoder

Decoder Overview

Navigate to Decoder Management: Click on the menu item "All Decoders". View the overview of all available decoders.

Create New Decoder

Click on the "Add new Decoder" button. Select the device type for which you want to create the decoder. Note that you can only add a decoder for one of your own device types. Be sure to create your own device type first. Fill in the required information for the new decoder, such as name and description. Click "Add Decoder" to add the new decoder.

You can add as many decoders as you like for your device-type.

For more information on creating your own decoders, please refer to this page.

Edit or Delete Decoder

If needed, you can edit or delete your decoder through the decoder overview. Select the decoder from the list and in the decoder detail page, click Edit or Delete.

Create and Test Decoder Script

After creating a decoder, the decoder script must be created. In the decoder detail page, click the "Create" button in the Script section. Write and test the script using the designated editors. Click "Save" to save the script.

The decoder scripts can be tested using the provided sample payloads, or you can create your own test payload. The Click "Run script with test payload" to test your decoder script. The output and log can be used to validate your script.

For more information on creating your own decoder scripts, please refer to this page.

Edit or Delete Decoder Script

If needed, you can edit or delete your own decoder scripts through the decoder detail page. Click "Edit" to edit the script and in the edit script dialogue: Click "Delete" to the delete the script. Click "Save" to store any changes to your script.

Step 3: Activating the Decoder in Flow

You have successfully created your own device type and one or more devices of this type have been added to your project. Then the decoder of your choice must be activated in your flow. This is done in the Things Manager application.

Activate Decoder

Select the flow in which you want to activate the decoder and click "Data Processing". In the Data Processing overview, select the device type for wich the decoder shall be activated and toggle the decoder of your choice. Alternatively, you can click the "Add new Decoder" to create a new decoder in the Things Creator application.

Localization

Using multiple measurements in a single domain to try to approximate the location of the device.

The following measurement values are outputted by KPN Things:

• latitude

• longitude

• radius (if available)

• source

GPS

The device determines location using GPS. An implementation works for a given device and decoder.

• Device: Should have a GPS module and send GPS location.

• Decoder: A decoder for each device type that sends GPS data (unless a Things protocol is used)

LoRa Geolocation

The LoRa network determines the approximate location of the device using three or more fine timestamps calculated by the gateways. An implementation works for all LoRa devices.

• Network: Should be KPN LoRa with a geo-enabled connectivity plan

• Decoder: LoRa Geolocation decoder should be enabled.

Wifi localization

There should be WiFi infrastructure, dense enough for a device to pick up multiple access points. A device should scan for available WiFi access points and send their MAC-address and received signal strength to Things DM. Things DM should then decode the payload whereafter an external service can be called to resolve the measurements to a latitude and longitude.

• Device: Device should be able to scan for WiFi access points

• Decoder: A decoder for each device type that scans for WiFi access points (unless a Things protocol is used)

• Processing: A WiFi Localization processor should translate incoming WiFi MAC+RSSI measurements to a latitude, longitude and radius using an external service.

Detection

Trying to detect another identifiable object with a known location and using the location of that object as approximate location of the device.

• detectedBeacon

• source

LoRa On Premises Gateway detection

The LoRa network forwards the identifier of the best receiving gateway. Using the user-administrated location of this gateway the general location of the device is determined.

• Network: Should be KPN LoRa.

• Decoder: Metadata embedded in the DevEUI_uplink message from Thingpark should be accepted as information to be processed in Things DM.

• Processing: One LoRa Metadata decoder for location detection using LoRa Gateway ID

Bluetooth beaconing

There should be managed infrastructure of Bluetooth beacons that transmit their identifier in a known manner. The locations of these beacons should be administrated in an (out-of-scope) application. There should be devices being able to detect the beacon and send the beacon identifier to Things.

• Device: There should be a beacon device transmitting a Bluetooth beacon. There should be another device picking up the beacon and sending its identifier to Things.

• Decoder: A decoder for each device type that sends a bluetooth beacon ID (unless a Things protocol is used)

• Processing: trancelate beacon to coordinates.

If you have an account on KPN Things Data Management, it belongs to a Customer account. All main objects in the KPN Things Data Management belong to a Customer: Projects, Devices, Destination and Network subscriptions.

A Network subscription contains information for network types for a specific client. Learn more about connectivity types.

Project

Each Project defines a solution you buy or build in KPN Things. Learn more about Projects.

Flow

With a Flow you link one or more devices to one or more plugs. So, if data is received from a device in a device group, its data will be forwarded to the plugs that are in the same device group.

A project has one or multiple activated decoders and encoders. These decoders prescribe which decoders should be used when data is received by a device that is in a device group that belongs to this project. Learn more about Flows.

Device

A Device represents a single physical device that can send data to the platform. When creating a device you tell the system the device specification it belongs to.

A Device specification has one or multiple supported network types. For all our supported device types, go to Devices.

For a device, you can create a Network info for each supported network type of the given device specification.

Destination

A Destination allows you to forward the data from your devices to an external system. For detailed information go to Destinations.

Then, the SIM cards should be visible in your KPN Things Portal on the All Connectivity page.

3. Obtain a Device

You now have a KPN Things SIM card in your possession, a SIM card that can be put in a programmable device to grant it direct access to KPN Things through a secure channel.

This SIM card supports connection to the following networks of KPN:

• LTE-M

• 2G

• 3G

• 4G

• 5G

Don't you have a programmable M2M Device yet? You should get one! We have some tips for you:

1. We have the most elaborate documentation on getting the SODAQ SARA AFF R412M to work with KPN Things, so getting such a device will provide you the best getting started guide that we have.

2. Other SODAQ SARA devices, like the SFF R412M or devices with a different modem should also work with our developer kit guide. You should only take into account some different settings.

   • For instance for SARA SFF devices, you should use Board type SODAQ SFF.

3. Our also contains example code for the Arduino MKR GSM 1400, laying the basics for all Arduino based M2M devices.

4. If you want to use non-Arduino based devices, you would need to write your own code to interface with KPN Things. This M2M interface is explained in the .

Application integration

KPN Things will connect to your application through a dedicated connection layer. To connect your application to KPN Things you can use one of the available Destination types. We support connecting plain HTTPS endpoints to KPN Things, but if you are developing in Microsoft Azure, you can connect directly to the Azure Event Hub.

The Destination types that support 'management' connect on a platform level and can also manage objects in the application. The Cumulocity destination for instance will create Device objects in the Cumulocity tenant for each Device that KPN Things sends data of.

KPN Things Portal

The KPN Things Portal is the web application through which you can manage and monitor almost all parts of the KPN Things solutions. You can manage each part of the KPN Things solution, from Device to Destination, to bring your IoT data from the real world to the digital world. You are also able to use KPN Things API's directly to manage your IoT solutions.

The KPN Things Portal is the visual interface with which you configure your solutions on the KPN Things Data Management platform.

IoT solution in KPN Things Portal

To manage your IoT solution you use Flows and in a Flow you link Devices, configure Data Processing and set up Destinations together. See how these components relate to each other in the Management Data model. Since network configuration, or Connectivity, is part of the Device in KPN Things, a Flow expresses the complete way how IoT data should be received, processed and forwarded, from the Device to the Destination and vice versa.

Learn why we built Things Portal and how it will benefit your IoT business

Quick reference instructional videos

For a kickstart, watch our instructional videos. They say more than a thousand words!

Look for the icon in the menu for more Quick reference videos.

explains about Getting started by creating an account and logging in for the first time.

Flexible Building Blocks

KPN Things offers you a flexible package of building blocks that you put together yourself. This allows you to set up and manage all your IoT solutions quickly and easily. You manage these building blocks in our KPN Things Portal.

Device Management

With KPN Things Device Management you have the insights and control over all your devices. ​

• Manage all your devices in one overview - From sensors to complex IP gateways and routers

• Device Twin - Insight in the status of every device

• Bulk actions - Manage solutions in bulk to control solution of any size​

• Firmware over the air - Update your devices remotely

Connectivity Management

Manage all your LoRa, LTE-M and M2M connectivity in a single platform.

• All your connectivity in one view - Manage LoRa, LTE-M and M2M connectivity in one view

• Manage connectivity for your device - Provide your devices with a connection

• Extensive network information - Have insights in your solutions all the time

• HTTP and MQTT protocols for M2M devices - You decide how to connect your devices

Destinations

A seamless integration of IoT data with any platform for maximum value.

• Platform Independence - Easily connect any data platform to the KPN Things environment, regardless of which platform you use or want to use

• Easy-to-Use Tools - We provide simple tools and extensive documentation to help customers create links and modify data.

• Extensive Functionalities - Access to a wide range of functionalities and additional services, allowing customers to use a platform that directly suits their specific use case

Customer and User Management

Provide your customers and users with a easy access to IoT solutions.

• Customer Management ​​- Manage IoT solutions of your customers

• Data Segregation - We provide in secure separation of data between your customers

• Customer Insight Overview - Have an overview of the different IoT solutions per customer

• Self Service - Provide your customers access to the Things Portal to manage their own solutions

• User Management - ​​Decide which users have access and to what functionality

Getting Started

To start using the API, you will need to:

• Obtain an access token to authenticate requests.

• Learn how to navigate error handling, pagination, filtering and sorting to efficiently retrieve data.

See the Getting Started guide for details.

Resources:

The API is organized around key resources. Each resource has its own dedicated reference page generated from the OpenAPI specification:

• Connector Bindings

• Devices

• Device Groups

Additional information

• Getting Started (authentication, pagination, filtering, sorting)

• Beta API (Deprecated)

SSL certificate information

The SSL server certificates of KPN Things and GRIP are signed by Sectigo and Certsign respectively.

Both certificate providers are trusted by default by most operating systems. If required for your security implementation, all certificate files of the chain can be downloaded here:

• Sectigo R46 root CA: https://crt.sh/?d=4256644734

• Sectigo R36 intermediate CA: https://crt.sh/?d=4267304690

• certSIGN ROOT CA G2: https://crl.certsign.ro/certsign-rootg2.crt

• certSIGN Public Web CA:

Click on the item Costs overview to navigate to the Costs Overview page. This page shows the costs that will appear on your invoices, presented in both a table and a chart. The costs are categorized by type; recurring costs, usage-based costs and one time costs (such as hardware). Any applicable discounts are already subtracted from the displayed amounts.

Costs details

Click on a row in the Costs table or on one of the bars in the chart to navigate to the Cost Details page for that billing cycle.

Under Base details information about the billing cycle, the rating period and the contract is shown. The items and discounts are shown under Items. The costs for the current month are a forecast of the upcoming invoice and are updated periodically throughout the billing cycle. Please not that the actual invoice may include additional costs and/or discounts that are not visible on this page. You can find all your previous invoices in MijnKPN Zakelijk.

The Previous and Next buttons above the card on the right allow you to navigate to the previous or next billing cycle.

Contract

To view your contract, go to the Project Overview page. To do this, click on the company name in the menu and then on the desired (Explorer of Modular) project. There you will see an item with the name of the contract.

Contract details

Click on the contract line to navigate to the Contract Details. Under Base details information about the contract, contract type and the activation date is shown.

Under Implementation, the project to which the contract is linked is shown. Items and discounts are shown per charge type, which can be recurring, one time or usage. These items are then grouped per product family. The regular price of each item is shown in the Unit price column of each row with a bold item name. If applicable, optional tiered discounts are shown below the corresponding row. The actual discount depends on the quantity, with the applicable range shown in the From and To columns . These columns are only visible if the contract includes at least one item with tiered discounts.

Costs overview

Users with an Explorer or Modular contract can view their costs per billing cycle in the KPN Things Portal. To view the costs overview, enable access by assigning the Finance Read-only role to your users in GRIP. If you need help with how manage your users, check the next page.

Starting point

The Organization details card shows an item called Costs overview (as shown in the image above), if at least one of your projects has an Explorer or Modular contract.

Costs overview

Click on the item Costs overview to navigate to the Costs Overview page. This page shows the costs that will appear on your invoices, presented in both a table and a chart. The costs are categorized by type; recurring costs, usage-based costs and one time costs (such as hardware). Any applicable discounts are already subtracted from the displayed amounts.

Costs details

Click on a row in the Costs table or on one of the bars in the chart to navigate to the Cost Details page for that billing cycle.

Under Base details information about the billing cycle, the rating period and the contract is shown. The items and discounts are shown under Items. The costs for the current month are a forecast of the upcoming invoice and are updated periodically throughout the billing cycle. Please not that the actual invoice may include additional costs and/or discounts that are not visible on this page. You can find all your previous invoices in MijnKPN Zakelijk.

The Previous and Next buttons above the card on the right allow you to navigate to the previous or next billing cycle.

Users

On this page, you will find an overview of the users under this account. Insight into the user details and which roles have been assigned to the user.

Contact Support

When support is needed, click on the Contact Support tile. This opens the General inquiries form.

lora for devices using ThingPark LoRaWAN

Connector Bindings let you precisely define how each device connects and communicates through the Things platform.

Lora Bindings

Download the specification.

HTTP Bindings

Download the specification.

MQTT Bindings

Download the specification.

The components are visually connected, allowing you to see at a glance how the flow is structured and if/how each element is linked.

Interactive editing

The Flows tab is not just a visual representation, it is also an editable interface. You can:

• Enable or disable components using toggle switches

• Edit components by clicking on the link, which takes you directly to the configuration page

• Remove a link, for example the Destination, by clicking the 'X' in the link

Error detection and warnings

If something goes wrong in the flow the affected component will be highlighted in orange. The visual cue helps you quickly identify where the issue lies. Clicking in the highlighted component (i) provides more details about the problem and suggestions how to fix it. The links in the highlighted component brings you to the configuration page, so you can fix it right away.

Examples of possible issues are:

• A required decoder is disabled or missing

• A destination is missing or misconfigured

• There's an incompatability between components

Report details

The report details show more report details on performance history.

1. Choose a from date and to date to present the graphs for a certain period

2. The KPI Value is the measurement of an availability for the specific month

3. The KPI Norm is the standard we strive for and use as minimum availability standard

4. Click SLA Report overview to go back to the Service reports page

Prerequisites

• KPN Things Account with active device

  • If you don’t have an KPN Things account create a free developer account.

• Azure subscription

  • If you don't have an Azure subscription, create a .

Step 1: Setting up the Azure environment

In this section you’ll be guided through the creation and configuration of an Azure event hub, a stream analytics job and an Azure SQL database. It’s advised to create a new resource group in which to bundle these newly created resources.

Creating and configuring Azure event hub

The Azure EventHub is used for the ingestion of data. Don't have an Azure Event Hub yet? Head on over to the Microsoft documentation to learn to create an Azure Event Hub:

From this point, when following the link, you’ve created everything to ingest data to Azure. You have created a resource group, an Event Hubs namespace, and an event hub.

Create an Azure SQL database with appropriate data tables

Now we have prepared the input data by creating the Event Hub. We can now proceed to the creation of the Azure SQL database for the data output. Don't have an Azure SQL database yet? Head on over to the Microsoft documentation to learn how to create an Azure SQL database:

At creation, remember to select the resource group created earlier. This way all resources for this quick start will be grouped together. Furthermore, make sure to write down the ‘Server admin login’ and ‘Password’. Under additional settings don’t select sample as we want to create our own data table later on.

Query the database

When the creation of the database is complete we can create the necessary table. Go to the query editor in the Azure portal as described in the documentation link:

In the query window run the query underneath to create a new data table in the database:

When completed a new data table called eventhub will be created. Additionally, two indexes will be created to enable quick searches on ‘bn’ and ‘bt’. These columns will hold the KPN Things device identifier and measurement timestamp. The newly created data table will be visible in the left view under tables.

At this point you’ve created the data input and the data output by leveraging an Event Hub and an Azure SQL database. In the next step we’ll set up the data stream from input to output by using Azure Streamanalytics.

Create and configure a Stream Analytics job

Now we have prepared the input data by creating the Event Hub and the data output by creating an Azure SQL data store. Now let’s set up Streamanalytics to tie it all together.

The following Microsoft quickstart will guide you through the creation of an streamanalytics job. The entire article describes the usage of an iothub for input data and blob storage for output. Remember in this quickstart we will be using Eventhub for input and Azure SQL database as output.

At ‘Configure job input’ select Event Hub and point to the Eventhub created earlier. Use ‘eventhubinput’ as alias.

At ‘Configure job output’ select SQL database and point to the Azure SQL database created earlier. Set the database table to ‘eventhub’ to match the table created during the previous step. Use ‘sqloutput’ as alias.

At ‘Define the transformation query’ select Query and update with the query underneath. Make sure you are using the input and output aliases as created under input and output

Now Save your input and start the Stream Analytics job.

At this point you’ve created a data ingestion point (Event Hub) a streaming data processor (Stream analytics job) and data storage (Azure SQL database) . In the next step we’ll connect KPN Things to Azure!

Step 2: Setup a KPN Things Flow with Azure Event Hub destination

Let’s put things together! Now everything is set up in Azure all we need to do is setup a data flow in KPN Things. This Flow will send device data towards an Azure Event Hub destination.

• Go to KPN Things and add a flow and give it a name and description

• Link new or existing device(s)

• Now go back to the flow and set up the data processing by enabling the decoders for the selected device

• Add a destination for the flow. Select ‘Create new Destination’. Fill in all necessary details related to the Azure event hub created in Step 1. Don’t know where to find all the required parameters? Follow the instructions here.

When all parameters are set the destination should be active. You should now have a working KPN Things Flow towards Azure Event hub.

Congratulations!

You’ve created your first flow towards Azure. All Data produced by the devices in the flow will now be sent to Azure, get processed by the Stream Analytics Job and will be stored in the Azure SQL database.

You can access email subscriptions in two ways.

1. Via My Things User Details (personal settings only)

2. Via Things Manager tab (change settings of all users, admin only)

Via My Things User Details

Via Things Manager Tab

Before you start

To manage email subscriptions of other users, you need the Things Manager - Admin role.

• Already an admin? Great! Let’s get started!

• Not an admin yet? Ask your organization’s administrator to grant you admin rights Not sure who that is? Contact us and we’ll help you out

2. Determine device identifiers

The LoPy4 is a LoRa device, and to register a LoRa-device to a network you need three values: DevEUI, AppEUI and AppKey. These values must be registered in KPN Things and in the device. For more information on these three values you can read Device Identification in the LoRa documentation.

3. Register your LoPy4 to KPN Things

Open the KPN Things Portal

Open the KPN Things Portal. Go to the All Devices page and click on Add new Device.

Fill in your device information

1. Select the Own LoRa device (preset connectivity) device type

2. Enter a name for your LoPy4

3. Click Add Device to continue

Provide Network Information

Fill in the three values you determined in the previous step Determine device identifiers. Then click Add Network Info to save the network information and then Finish to continue.

Check your newly created Device

You are now on the Device Detail Page. In the LoRa tab you will see the network status. This can temporarily be Pending creation, but if you refresh the page it should switch to Active. This means your device is correctly registered to the network.

If the network status sticks to Pending creation, you could try to delete the Device and register the device again.

5. Program your device

Use the LoRaWAN with OTAA example from Pycom to get your device connected with our LoRa network and have it send data to KPN Things.

Check incoming data in the Portal

Now your LoPy4 has joined and is sending data, you could visit the LoRa data tab on your Device Detail Page in the Portal. You should see your Join request and Join accept appear like in the screenshot below and at this point you will see more data as well.

Read more information about what you see on the LoRa Data History tab.

Setup data flow in KPN Things

You now successfully connected your LoPy5 device to KPN Things! To further setup your data flow in KPN Things, you can go to the next step:

2. Select your Device type

You can select an existing device-type offered by KPN Things, or create a new device type using the Things Creator app.

3. Fill in Device Information

• Name: Typically can be a Device ID or the name of a physical asset which the device is linked to.

• Barcode (optional): Barcode or serial number used to identify a device.

• Description (optional): Any additional device information.

When done, click Add Device to continue.

4. Provide or get Network information

This step will look differently, depending on the type of network information.

• Generated LoRa network information (programmable device)

• Provided LoRa network information (device with preset connectivity)

• M2M network information

Generated LoRa network information (programmable device)

If you selected Own LoRa device (programmable) device type in the previous step, the Portal will give you the OTAA join information (DevEUI, AppEUI and AppKey). Make sure to copy-paste or write down the provided identifiers. For security reasons the secret values will not be retrievable through the Portal after closing this page.

Click Finish to continue.

Provided LoRa network information (device with preset connectivity)

If you selected Own LoRa device (preset connectivity) or a supported device type, you should provide the LoRa network information for your device in this step.

Click Add network info to save the network information and then Finish to continue.

M2M network information

1. IMEI of your Device.

2. ICCID of your SIM-card - select the correct SIM card from the drop down. If you have an Early access SIM, you choose the option "Add early access SIM" and enter the ICCID of the SIM manually in the newly appeared input field (see A in the screenshot below).

3. Shared secret

After entering the values, click Add network info to save the information, or click Finish without adding Network to continue without adding network information to your Device object.

Internet network information

1. DvnUUID - the unique number to identify incoming data from your Device. Your Device UUID is prefilled, but you can enter any UUID you like.

2. Shared secret

5. Check incoming data in the Portal

You can visit the LoRa data or M2M data tab on your Device Detail Page in the Portal. You should see messages here as soon as the device has activity on the network.

You're ready for the next step:

Choosing the Right API

• Use actuator-style downlinks whenever possible. They are protocol-agnostic, simpler, and safer.

• Use connection-specific APIs if you need full control over the payload format or protocol-specific features.

Actuator-Style Downlinks

Download the /downlinks specification

HTTP Downlinks

Download the /http/downlinks specification

LoRa downlinks

Download the /lora/downlinks specification

SMS Downlinks

Download the /sms/downlinks specification

MQTT Downlinks

Download the /mqtt/downlinks specification

Next Step

To learn more about how to manage users within your specific IoT service, please select the page that matches your KPN IoT solution. Each section provides tailored guidance to help you manage users effectively within your environment.

Need your invoices now?

Click the tile below to open MijnKPN Zakelijk right away.

Invoices

Invoices can be accessed via the following options.

1. Click on Invoices in the menu

2. Click on the Invoices tile

Interactive Map

The Zone list map offers a global overview of operator availability by country. Key features include:

1. Zone filtering: toggle between Premium and Economy zones

2. Color Legend: easily identify zone types using the map legend

3. Country details: click on a country to view available operators

4. Dynamic updates: the map shows the filtered countries and their operators from the Zone list table, divided/shown by economy or premium maps

Zone list Table

The Zone list table provides detailed, country-specific information about available mobile technologies. Users can:

• Apply Filters: Narrow down results by country, zone type, technology and more

• Check Technology status:

  • Live: the technology is currently active and available

  • Ending: the technology is still available but is being phased out

This table is designed to support decision-making by offering granular insights into global technology availability. Click the information button (next to 'Zone list' at the top of the table) for tips on how to use the table and additional details about the displayed data.

Tips for use

• Use the Zone toggle on the top to toggle the map view between Premium & Economy zones

• Use Alt (Windows) or Command (Mac) + Scrollwheel to zoom in on the map, drag it to pan the map

• Use the toggle above the legend to make the map reflect what you filtered in the table

• Click a county to pin the data in the information field, click unpin to show data on hover again

• Use the right mouse button on the table to export to your spreadsheet software

• Hover on the link on the bottom of the table to see when the table was last updated

Zone information

In the list the 2 standard sets of zones are represented: the Premium zones (also known as full zones) and the Economy zones. The list contains as well a column with the name of the zone as a separate column for each zone.

Note: The Premium Zones are based on countries. All for KPN IoT available networks are accessible for usage within that zone. Each higher zone actually also contains the countries (and operators) in the earlier zone. If a Rate Plan doesn't contain one of the first zones, the countries will be included in the first next mentioned zone.

Note: The Economy Zones are based on a selected set of operators within a country. KPN IoT tries to make the best balance between coverage, quality and price. This means that not all for KPN IoT available networks are accessible for usage within that zone. Note as well that each higher zone doesn't contains the operators (and countries) in the earlier zone. This means that if a Rate Plan doesn't contain one of the first zones, the usage on those operators (in those countries) will NOT be included in the first next mentioned zone, but will be stated as usage in 'Other' (which is most of the times highly priced). Always make sure that when a Rate Plan containing these zones is connected to a subscription (SIM), that also the Communication Plan is related and handles the roaming restriction set that belongs to the economy zones.

KPN Things supports the devices as shown in the subpages of this page.

KPN Things Devices versus Supported Devices

We have two categories of Device types, namely KPN Things Devices, when you buy a Device from us, and Supported Devices, when you bring your own Device to KPN Things. Each categorie has its own set of Device Management features in the Portal.

Legenda ✅ - Available for this device type. 🟡* - Configurable for your own device, coming soon. ❌ - Not available for this device type.

Bulk actions

Next to the device list, you will see options for bulk actions, like activating or deactivating your M2M devices, or editing device settings in batches. These actions can be initiated by selecting multiple devices from the list or by uploading a CSV file that contains the necessary device information.

Exporting to CSV

You can easily download the Devices - Data result set by clicking the Download icon just below the Search icon.

This will generate CSV file, containing all devices in the current selection. The CSV file will contain the measurements accompanied with the timestamp of that specific measurement.

Click on the Bulk by CSV file button.

This step opens the process for uploading multiple devices at once via a CSV file. This saves time since you don’t need to add each device individually.

You are asked to upload a CSV file with the device data. Ensure that the structure of the file matches the template exactly, which you can download. Use a comma (,) as the CSV separator.

After uploading the CSV file, it will be validated.

This screen gives you feedback on the validation. All devices with valid data are displayed, and devices with errors won’t be processed. The system checks fields such as IMEI, ICCID, and other required fields.

After validation, choose the target project and flow where the new devices should be added. You can also specify the device details, such as the device type.

Here, you define the project and flow in which the new devices will be processed. You can also choose the type of devices being added, for example, M2M devices or another type.

Click on Add new M2M Devices to start adding the devices.

The system will now begin adding the devices. You can monitor the process by following the progress in the Bulk reports where you can see if all devices were successfully created.

• FPort: is the LoRa application port on which to send the data. If you don't use application ports on your device, you can just use 1.

• Payload: is the data you want to send to your device, written in hexadecimal characters. You could use for instance 010203.

Click Submit to request the downlink to be sent to the device.

2. Check status of downlink

After requesting the downlink, under Status Downlink your downlink will have appeared. Maybe you first see your downlink with the PENDING status, meaning it is still being processed, but if you hit the refresh button (#2 in the screenshot) you should see it switching to EXECUTING.

Queuing At most one downlink can be in EXECUTING at a time. When you submit more downlinks, they will stay in the PENDING state and they will be processed "first in first out". You can have at most 5 downlinks in PENDING. As long as a downlink is in PENDING mode, you can cancel it. If you do so, it will not be send anymore and the status will change to CANCELLED.

Learn more about downlink statuses. LoRa Downlinks sent through KPN Things are always Confirmed downlinks. That way we trigger an Acknowledgement (ACK) from the device in the next uplink, and with that information we can determine whether a downlink was received or not.

Click on the refresh button (#1 in the screenshot) to refresh your Data History table. There should now be an uplink record following your downlink record that contains an ACK (#2 in the screenshot).

• If the uplink containing the ACK was not received by the network, you will see your downlink is still in EXECUTING. When a next uplink is received we conclude the downlink as FAILED, since we do not know for sure whether the downlink has been received. You could state that the quality of service for downlinks through KPN Things is "at least once".

If you switch back to the Send Instruction tab, you should see that the status of your requested downlink has switched to DELIVERED. That means the acknowledgement has been received by the network.

Optional: send your data to Azure SQL