Things PortalLoading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
See here what's new to the KPN Things Portal!
We aim to release updates as soon as we finish them. In these updates you can expect new features, upgrades of existing features and fixes
This is our first release of 2023. To start the year with a clean slate, we cleaned up a large part of our code base so we can bring you nice features this year. Also:
The Connectivity page is extended. Now it is possible to easily select all connectivities (across all pages) with just a few clicks.
We changed an url validation on the Destination Details page.
This is a user guide to the KPN Things Portal, the online portal to manage your IoT devices and solutions.
Plugs → Destinations As of Version 10 of the Portal (21th April '20), Plugs are now called Destinations!
Groups → Flows As of Version 13 of the Portal (2nd June '20), Groups are now called Flows!
The KPN Things Portal is the self-service website for the KPN Things platform. The portal allows you to connect your devices to one of KPN's mobile networks, decode the device payload and forward the payload to any given endpoint.
If you register for free for KPN Things, you get a KPN Developer account. With this account you get free limited access to the KPN Things Portal:
One project on the KPN Things platform.
Access to our Device SDK to get you started with programming your Device.
Integrated KPN LoRa functionality:
Free registration of up to 3 devices to KPN's nationwide LoRaWAN network.
Free use of LoRa Geolocation.
Insight in LoRaWAN network communication.
Additionally, you can order KPN Things SIM cards to connect M2M devices to KPN Things:
Connect up to 2 M2M devices to KPN Things for free.
Data communication over HTTP (MQTT will be available in the future).
Access to our LTE-M, 2G, 3G, 4G, and 5G networks.
European roaming included.
Optional payload decoding for supported device types.
Forward your data to up to 3 different destinations.
KPN Things access is subject to your Terms of Use.
If you are interested in more features than the Developer account has to offer, please contact our commercial support on iot@kpn.com for more information.
Added
We introduced the All Flows pagina, giving you an overview of all the Flows in all your Projects, complete with sorting and searching!
Fixed
You can now clear the barcode property of your Device in the Portal again.
Update shared secret for M2M and Internet devices is fixed.
Sometimes a LoRa Device could not be deleted when the backend system had a hickup, this is now fixed.
Added
You can now delete multiple Devices at once on the All Devices page using the bulk functionality in the Portal.
Changed
When ordering Freemium M2M SIMs, we now offer you a very nice online form in order to enter your information, instead of a redirect to your mail client.
Fixed
The landing page after unlinking a SIM from a Device is now fixed.
Some small frontend bugs for Connectivity have been fixed.
Added
The lock icon indicating whether a device is managed has been added to the Devices in Flow page.
Changed
A tooltip now explains why a certain bulk action button is disabled.
Fixed
If your Project does not support Flows, the Add Flow button is now disabled on the Project overview page, to make it more clear that you cannot add Flows.
When creating a second Device of the Things Device simulator app type in a row, the QR code that was shown was incorrect. We fixed this.
SIMs can now be linked to a Supported M2M Streamline device or a LocationTag VI.
Added
Introduced a more granular Device Management rights model, allowing for the coexistence of KPN (a.k.a. managed) and Own Devices in the same Project.
The Device list pages now show whether a Device is a Managed Device with a lock symbol.
You can now edit the name, description, and processing status of any KPN Device you have in your account.
If you have multiple Projects, you can now move Devices in bulk from one Project to another.
Changed
If you have KPN Devices in a Project with a Device limit, the KPN Devices will now be excluded for the Device limit.
Several error notifications have been made more descriptive.
The default page size is now 50 on all list pages, such as the All Devices page.
Fixed
When reloading a list page, we now load the table on the page you were when you left.
We fixed the link from the Device tab to the Internet tab on the Device detail page of Internet connected devices.
this release contains some small tweaks and fixes. Keep your eyes peeled for upcoming releases, because we have been working on something big!
Added
It's now possible to update a shared secret of an Internet device after it has been created
Changed
We implemented a new cookie notification
Fixed
Fixed interpreting user rights for linking SIM cards
Added
When you are authorized to send firmware updates over the air to your devices it is no longer necessary to log in to a separate FOTA environment. Through a link on the all devices page and on the device detail page you can directly access the FOTA functionality.
Changed
Several adjustments have been made to allow customers to change name, description and network information for devices in their own customer environment with the appropriate permissions.
You can also remove devices with the correct permissions.
When you want to add devices to a flow you will only see the devices that are available to add in this overview.
Freemium users: When the device limit is reached, it's still possible to add devices to another flow.
Changed
If you didn't create a network for an internet device, you now have the possibility to do this later.
Device twin: There is a new function in the device twin that directly request values and attributes from the encoder, even when devices haven't had any messages yet.
It's now possible to change the device to another project. You can manage this on the device detail page. It comes in handy since a device can only belong to one project.
You can now link a device to a flow within the project environment. You will not see flows from other projects anymore.
If during bulk actions devices are selected from different projects, a new build in function makes sure that devices can not be added to various flows.
The network type from the internet card on the device & connectivity detail page is slightly changed. If the network type is unknown it will say 'internet (with credentials)'
Device Twin: you can now reset all reported states so that any previously created attributes that were not used can be removed.
We build in an extra check to make sure that device limits can't be exceeded and that devices can not be added to expired projects or have invalid device specifications.
We slightly changed the page style: more uplifting background and rounded corners. This way we are more in line with the new MijnKPN Zakelijk style.
Device Twin: you can now set metadata even before you have added the Device to a Flow, configured the Device Twin, and received the first Reported state for a Device.
Device Twin: we added a refresh button for you to refresh only the Device Twin without having to reload the whole page.
When adding a Device while you have multiple Projects, you now will be asked to select the Project to which you want to add your Device.
We updated the KPN LocationTag I encoder, such that mode changes for this Device type will now be executed faster.
We fixed moving your Device to another Project through an API call.
We fixed the KPN LocationTag I decoder that was still visible on the Data Processing page while it was already deleted.
The Raw LoRa Payload decoder is now available for all supported Device types.
Starting today, all your Devices will always belong to one Project. With this change we prepare for the future, where customers can have multiple Projects in order to express different commercial contexts/contracts. And since different contracts can mean different things you can do with a Device, we need to know to which commercial context/contract a Device belongs. Next release we will introduce a Flows column on the All Devices page, allowing you to again see which Devices are (not yet) linked to Flows.
Coming from the GRIP Developer Portal, you will automatically log into the KPN Things Portal after clicking the KPN Things tile. Previously you still had to click on "Log in" on the Things Portal.
When in a sub-customer environment, the Your profile link would not work anymore. This is now fixed.
We added an optional field in the registration form to provide a phone number. We will use this phone number to contact you for commercial talk if you want.
On certain pages you could run into loading errors, which only a page reload would fix. This has been corrected.
We fixed the timezone for dates related to Bulk reports.
Data processing for Devices can now be activated and deactivated in bulk on the All Devices page and Devices in Flow page.
You can now see the Data processing status on the All Devices page and Devices in Flow page.
Performance of the Link Device to Connectivity page for M2M SIM cards has been improved.
If you clear your search field while you did not commit the search, it does not trigger a refresh of the data anymore.
After changing a table view, for instance by opening a different page of your data table or by changing the sorting, the page will now scroll to the top of the table.
It is now possible to switch SIM cards for Streamline M2M and LocationTag VI devices.
After opening a linked SIM card through the All Connectivity page and then unlinking it from the Device, you will now end at the detail page of the SIM card instead of the Device.
When you have M2M in your account, the network info card on your Customer detail page now has the correct title.
Fix for Bulk reports side menu link when switched to sub customer.
We fixed the icon for unlinking.
When you do multiple registrations at once with the same email address, only one will succeed from now.
We added a notification when you edit the Flow data configuration, so it is more clear that a change has been committed.
The checkboxes for bulk operations are now hidden if no bulk operations are available for your user.
Registration had some major issues, rendering registration almost impossible. Sorry for this! We fixed it now.
We have eliminated multiple error messages with the same content. This will now be only one message.
Some performance issues on the Destination pages have been fixed.
The layout of detail pages has been fixed for situations with a long Flow name.
Notifications in the Portal are now shown as toasts, so page content will not move anymore when displaying a notification.
When you are editing something in a pop-up and you click outside the popup, we will now first check whether you really want to stop editing and close the pop-up.
Linking a single Device to a Flow from the Device detail page does not trigger a bulk report anymore.
The registration email is now in English instead of Dutch.
We fixed the table header on the All Devices page.
The breadcrumb link on the Customer Overview page has been fixed.
It is now possible to deactivate the Data processing of individual Devices. Useful if you want to (temporarily) disable the data flow of a certain Device.
You can now add multiple Devices to a Flow from the All Devices page! After selecting your Devices you get a pop-up allowing you to select an existing Flow or create a new Flow to which the selected Devices will be added.
When adding a new Destination, we now give you a link to the documentation on Destinations.
When you just changed the status of a SIM, we now indicate if the state change is still pending.
The backend now allows a bit higher load, preventing weird behavior when you are browsing the Portal in a fast pace.
When you access the APIs directly with an invalid token, the API will now respond with a 401 status code instead of a confusing 302 redirect to the login page.
The "Add network subscription" work around for older accounts has been fixed.
Released after one week delay
We introduced sorting for all columns in the All Device page and Link existing Devices to Flow page.
So now you can find the Devices that are not yet in a Project by sorting by Projects.
And you can find Devices that did not communicate recently by sorting by Last message.
And you can find Devices without network identifier by sorting by DevEUI / IMEI / DvnUUID.
We switched the Last message and Projects column on all the Device pages.
The loading time of all the Device pages has been improved significantly! (All Devices page, Devices in Flow page, Device Detail page, Link existing Devices to Flow page)
Pagination on the Link existing Devices to Flow page has been fixed.
The Devices on all Device pages are now properly sorted alphabetically!
The loading time of the Data Processors page has been improved as well.
The Downlink status table has been fixed for M2M downlinks.
When linking Devices to a Flow, you can now select multiple Devices and link them to the Flow at once!
The "this is still the KPN Things Portal" notification has been removed from the login page.
The company name is now shown for all types of paying customers in the top right account info block.
Pagination on the All Destinations page has been fixed as well.
Learn how to start with KPN Things
Register for a . This account will grant you access to the KPN Things Portal with a freemium registration.
After registration you receive an activation email. It could take some time. Click the activation link (Stel uw wachtwoord in via accountbeheer) in the email and create a password. Now your KPN Developer account is activated.
After registration you will end on a login page asking for your user name. Enter your email address here.
Then enter your newly created password and click Doorgaan to continue.
. A mobile phone app that transforms your smartphone into a KPN Things Device. Especially handy if you don't have a LoRa or M2M device at hand.
The column Flows has been added to the , such that you can check which Devices are not yet added to a Flow.
The columns on the have been updated: we added the columns Device name, APN, and Bundle/rate plan, and removed the column Flows.
Today we launch our biggest feature for the KPN Things Portal for 2021 up until now: the Device Twin! In the Twin of a Device, KPN Things will keep track of the state of your Device in several ways, and present this state in the Portal.
Two configurations have been added to the Cumulocity Destination type: Bidirectional behavior and Auto refresh credentials. More information on this can be found on the .
The SenML decoders for the Own M2M and Own Internet device types have been upgraded to supports both SenML and !
All historical bulk operations can now be found on the new .
You can now find you GRIP tenant ID on the page, useful when starting to use our .
If we spot a possible issue with your Flow's data processing configuration, we now say so on the , , and on the if the issue concerns the Device you are looking at in the Portal.
You can now unlink multiple Devices from a Flow from the using multiselect.
For M2M connectivity (SIM cards) you can now toggle the connectivity status between Deactivated and Active on the .
You are now on the KPN Developer Portal home screen. . Open the KPN Things Portal by clicking on the KPN Things icon.
When visiting the KPN Things Portal in the future, you can access directly as well via .
Added
The changes you make to how a table is displayed (column visibility and ordering) are now remembered. That means that the next time you visit the table, you will find it just like you left it.
The changes you make to the filtering of a table are also remembered, and filtering is now part of the URL, meaning that you can share your view of a table by just copying the URL.
Changed
You can no longer configure the device twin to display only certain values from the device message. You will simply get all the values that the device emits.
Fixed
We fixed a number of issues in the All customers table.
Added
Introduced an All Devices page (crossing boundaries) for the lucky few who also have access to the All Customers page.
Bulk change Comm and Rate Plans for testers.
Changed
Links in tables can now be opened in a new tab. Hold the CTRL or Command key to take advantage.
Rearranged columns in Connectivity for clarity.
Fixed
Tooltip bugfix on HTTPS Destination form.
Changed
Various changes for KPN operators
Added
Proper feedback in Destination URL validation.
Extra tooltip on bulk (de)activate devices.
Changed
Multiple M2M network subscriptions are now possible.
Icon usage aligned between sidebar and account page.
Added
We added the new 'Synchronized' column to the All Connectivity table (hidden by default). This column tells you when the Connectivity was last synchronized with its source (e.g. Cisco Jasper).
Fixed
Some bug fixes and small improvements.
Added
In the devices table you can now use the 'in' filter on a column to search for devices by a list of names, deveuis, imeis or dvnuuids.
Changed
Pressing Enter in filter field now triggers application.
Added
Improved the empty state of tables.
Added
We added an 'Add new Flow' button to the Flows overview. We already had that button on the project, but adding it to the flows overview makes it easier to find and brings it more in line with other overview pages.
Changed
This is the first Things Portal version delivered through our brand new Continuous Deployment. Expect more frequent improvements and when needed, faster fixes.
Improved filtering on devices overview
Improved flows overview
Added
We added a column to the table on the devices page that shows the connectivity status of each device. We also put the search field back, and we improved the filtering on the columns of the table.
On the device detail page of a LoRa device that resolves location data, we added information about what method was used to resolve the location. So if you've always wondered if RSSI or TDAO was used, now you know!
For the real power users we introduced the possibility to activate and deactivate device connectivity in bulk. We'll be adding a lot of bulk functionality in the future so expect to see new features pop up!
Fixed
Selecting all devices out of a very large list was broken. We fixed that. Now when you select all devices, you're really selecting all of them.
Added
We log client side errors now to make it easier to find problems that things users may experience.
Changed
We're improving the usability of tables. We're currently working on the devices table.
Changed
The all devices tables has received a major upgrade, making it easier to sort and filter devices.
Changed
We are improving the usability of data tables in Things. In the coming releases you will notice that table columns can be rearranged, hidden or shown, sorted upon or searched through. For a sneak preview, see the all destinations page.
Fixed
The device simulator app on Android was unreadable if your phone was set to dark mode. We fixed that.
Added
We added some sprinkles to our Welcome page.
Changed
We removed the possibility to add ICCIDs by hand (aka Early access SIMs).
We are improving our release process so that in the future we can bring you more features, faster!
Added
Upgrading from Freemium to Explorer (unlimited devices, invoiced monthly) is for real. The Upgrade-button on the home page offers Freemium users pricing & features info and access to a form for the actual upgrade. Other user still get the old school upgrade through an e-mail.
Changed
Improved data synchronization for more speed and flexibility.
More details for M2M connectivity.
Added
A simpler, fresh looking Welcome page.
Groundwork for something big.
Fixed
A few things you hopefully never noticed.
Added
M2M Things+ SIM cards (still in testing phase) are now also shown in the SIM cards dropdown in step 2 of Adding a new M2M device.
Added CSRF/XSRF security measures to the Things Portal.
Fixed
Stability and security updates.
Added
M2M Things+ SIMs (which are still in testing phase) can now also be selected when linking Connectivity to a Device
For Cumulocity destinations, "Autorefresh credentials" is now only made available for KPN Things Cumulocity accounts, since those are the only accounts we can autorefesh
Added
On the Devices in Flow page, you can now see the date and time from when a Device was added to the Flow! Unfortunately this information is only available for Devices linked after March 17th 2021.
The column widths of the All Projects, All Destinations and Status Downlink tables have been optimized.
The order of the downlink history in the Device details page is now fixed to always be descending in send date.
Sometimes you would get an error when linking a SIM to a Device, while in the end they would end up linked anyway. This is now fixed.
The button style on the Link Device to Flow page has been fixed.
After switching projects when adding a Device in the Portal, sometimes you would see the wrong device types. This is now fixed.
Standardized the “do you want to upgrade” popup on different places in the Portal.
If you visit a specific Portal page while not logged in, we will now redirect you back to that page after logging in.
Columns with numbers in them are now aligned to the right.
Sorting on device type did not work in some cases on the Device pages. Now it works again
Learn how to connect your device to KPN Things
We have several manuals to get you started with specific devices:
SODAQ R412M - a LTE-M device to start using Things M2M
Marvin development board - an easy to use LoRa device
LoPy4 - Micropython development board with LoRa
But if you are interested in a more general description of connecting a Device to KPN Things, head on over to the Add new Device documentation.
The Portal now supports devices types that have composite downlinks, where one downlink message can contain multiple instructions.
If you open the Data Processing for Flow page for a Flow that contains only Devices of one type, the Decoders and Encoders for that Device type are directly visible.
M2M connectivity: you can now also link Devices to your SIM card that previously were linked to a different SIM card. This was a bug, now not anymore.
We fixed the "Add Destination to Flow" page. If you had more than 20 Destinations, some Destinations could not be selected to be added.
Linking SIMs to Streamline M2M Devices is now fixed.
Do you want to get started with M2M connectivity in KPN Things! Use the notification link on the Portal homepage to order your own M2M SIMs now!
You can now send downlinks to your Device through our KPN Things APIs! Head on over to the Developer Manual on API access to get started.
We added support for 1M2M ED1608 devices.
Customer Management: when you revisit details of your customers through for instance a bookmark, the page will now directly open instead of redirect you to the All Customers page.
The M2M tab on Device detail page has been improved.
The device type selection boxes have been upgraded:
Moved Feedback button a bit down.
In rare cases, clicking on "Log in" would not forward you to the login page. This is now fixed.
When unpairing a SIM card from your M2M Device, the M2M network info (IMEI and shared secret) will now be kept.
Fixed (anonymous) usage logging to Adobe Analytics.
The tables on the All Customers, All Devices, and All Connectivity pages and on the LoRa data history tab on the Device detail page have been given sticky headers and sticky action columns. That way the most important information will never scroll out of sight.
The loading time of the device detail page has been reduced significantly!
We are preparing a performance improvement for several Portal pages that load slowly for customers with large number of Devices.
M2M Connectivity: It is now possible to unlink your SIM card from a Device.
The Send instruction tab for Device types with predefined commands has been updated to support devices with multiple commands.
All existing LoRa devices now use the new LoRa Geolocation algorithm Both! This change improves the success rate of LoRa Geolocation by using the received signal strength to calculate a more course location when a fine location calculation does not succeed for a message.
All Device type images have been updated.
The message on why sending instructions is not available for your Device has been made more clear.
Customer management: when switched to a sub customer:
Only "Home" and "All Customers" will be visible from the top menu in the side bar.
The sub customer resource links don't have the word "All" in them anymore.
In sporadic cases, the whole Portal would go grey if a certain type of error occurred. This is now fixed.
Deleting a Device is now fixed in Firefox.
Device management: The device identifier (DevEUI for LoRa, IMEI for M2M, DvnUUID for Internet) is now shown and searchable on the All Devices page.
M2M Connectivity: It is now possible to link your SIM card to an existing Device.
M2M Connectivity: It is now possible to link an existing Device to a SIM card.
Customer management: It is now possible to open different Customers is different tabs of your browser. Before, you could only have one Customer environment opened at a time.
Some search terms did not work as expected on the All Devices page. This is now fixed!
For customer environments without Projects the company name will now be displayed in the top right account information.
Customer management: a new page is introduced to give you a better overview of your customer: the Customer overview page.
M2M connectivity: The detail page of a Things M2M device now shows you more information: MSISDN, Activation date, and Rate plan.
The login page has been changed to accommodate loging in with your MijnKPN Zakelijk account.
We now use different icons for the big resource buttons on the home page:
MijnKPN Zakelijk users will see a link to the service portal instead of a link to the developer portal on the home page.
Newly created LoRa-devices will use an upgraded version of LoRa Geolocation. Existing LoRa-devices will follow.
When clicking on the current page in de side menu, the page will now reload.
Customer Management: when switched to a customer the access rights used to disable buttons was wrong, this is now fixed.
The mobile menu will now close when you click on the current page.
Devices with M2M or Internet connectivity are now supported by the Add new Device page.
For non-freemium customers the customer name will be displayed in the account name in the upper right.
General
If you would register with an email address that was already registered with the KPN API Store, you account would not be set up correctly. This is fixed.
For customers with multiple users, the correct user name will now be shown in the upper right.
Some notifications still used the old names for Flow and Destination (those were Device group and Plug respectively). We fixed those notifications.
It was not possible to view the Devices or Destinations in a client environment which has no Project. This is also fixed.
Device management
Last message time is now displayed for all Devices, not only Devices with LoRa connectivity.
Customer management
When switching to a client did not succeed, the Portal would keep stuck on the Please wait screen. This is now fixed.
When switching back to your own client environment, sometimes you would still see the Projects of the previous client environment you switched to. This is fixed as well.
Introduced All Connectivity page and Connectivity detail page for users starting with M2M connectivity (early access feature).
Added last message time information to Device detail page.
We extended LoRa data history documentation and added a link to the text in the Portal.
Error notifications will not disappear automatically anymore, since this wrongly suggested that the error was fixed.
Introduced anonymous tracking for users that declined advanced cookies as according to our cookie consent.
Font size of data in tables is now one pixel smaller (15px), making the data a bit easier on your eyes.
There is now a search bar on the All Devices page, to allow you to search for a Device by name.
You can now link your Device to a Flow from the Flows tab in the Device detail page.
The Portal will now disable buttons and give an informative popup when you are not allowed to perform certain actions.
It is now possible to send predefined downlinks to KPN devices in the Portal.
It is now possible to send raw SenML downlinks to Own M2M devices and Own Internet devices in the Portal.
The Destination status will be Not yet linked when the Destination is active but not linked to a Flow.
The toggle button with which you enable and disable your Data Processing configuration will not toggle if there was an error while processing the request.
The device detail page has gotten a face lift!
The names of the Own LoRa device types have been made more clear:
Own LoRa Device → Own LoRa Device (programmable)
Own LoRa Device with preprogrammed keys → Own LoRa Device (preset connectivity)
Listing available decoders when adding a new Device to a Flow is now a bit faster.
The backend for LoRa Key issuance has been updated, making it a bit faster as well.
We now check the TLS version and cipher of the endpoint of an HTTPS endpoint destination and we do not allow unsafe TLS versions and ciphers anymore. This means TLS should be version 1.2 or above. And you find here more info on the supported ciphers.
On the All Customers page you can now search for a certain customer by name.
Non-freemium customers can now have multiple users.
The Device detail page could temporarily show incorrectly that your Device was not linked to a Flow. This is now fixed.
For customers with the Customer Management add-on, the All Customers link in the side menu is now visible.
The news will now be refreshed automatically without possible cache issues.
We introduced Customer Management for customers who want to manage their own customers as separate environments in KPN Things. This is a payed feature giving you an overview of your customers and the ability to view or edit the configuration of your customers.
The icons have been tweaked slightly.
We gave the skeleton loader new colors, making it stick out more against the background color.
The Portal now works again in Firefox and Safari
On the Project overview page and Flow overview page, the links to sub-objects have been made smart. So, for example, when your Flow does not have any Destinations, like in the screenshot below, clicking on Destinations will directly bring you to the Add Destination to Flow page. Another example: if your Flow only has one Device, clicking on Devices will directly give you the details of that Device.
When you want to post feedback using the Feedback button, and you are already logged in, your personal data will be prefilled!
The multiselect field in the form for the Cumulocity destination type has been replaced by a checkbox group
The account menu has been upgraded to have three links:
Customer Details (renamed) - Shows you details of your customer environment in KPN Things.
Your Profile (new) - Your personal page for your user account. From here you can change your password for example.
Sign Out - Sign Out of the KPN Things Portal.
We upgraded the API Gateway, making our systems more resilient.
Support for the Elsys ERS devices is added!
The downlink send form is now only visible when it is possible to send downlinks.
When switching from the device list of one Flow to the list of another, there was a short window of time where you would see the devices from the first Flow. This is now fixed.
A major release with a new home page, the introduction of Flows, and new icons!
Decoder and encoder management has been improved! We created the Data Processing in Flow page as replacement of the activated decoders and encoders on the project detail page. Now you can manage your data processing for each individual Flow (formerly known as Group).
All icons in the Portal have been updated!
The home page is upgraded! The layout has been improved and we introduced the news section!
The names and descriptions of decoders and encoders have been updated.
The bèta label has been removed from the page title.
Activated decoders and encoders have been removed from the project detail page.
After creating a destination, you are now redirected directly to the destination detail page.
Delete buttons now show a spinner when the action is pending.
The i-button for downlinks have been made clickable.
Implemented usage tracking with Adobe Analytics (for users that allowed cookies).
You can now delete a Group that still has linked Devices and/or Destinations. These links will be removed on deletion as well.
The LoRa Data History has been visually tweaked for even better usability.
The Azure IoT Hub Destination type has been added! Connect KPN Things to your IoT Hub now! More info here.
The MQTT broker Destination type has been added! This means you can now have KPN Things forward your device's data to your MQTT broker. More info here.
On the page Devices in Group you will now see the Device type instead of the manufacturer and model in the second column.
Finally we got rid of the false registration error! (Sometimes you could get an "registration failed" error, but your registration would succeed anyway).
When adding an existing Destination to a Group, the Destination type is now more human readable.
While logging in, sometimes you saw a scroll bar. This is now fixed.
We added a cookie consent pop-up to enable us to start Portal usage monitoring.
When a device's network subscription is in inventory status, you can now activate the device in the Portal.
In line of the upgrade of our terminology, Plugs are now called Destinations!
The interface has been tweaked to be more mobile friendly! Like the side menu:
It is now not mandatory anymore to add a plug to a new group if you had one. You can now just add a plug after creating the group.
The action links block has been phased out.
The overflow menu in table rows has been phased out.
When clicking on the backdrop of a modal, the modal will now close.
Spaces in a SAS key entered when creating or editing an Azure Event Hub plug are now removed in the input field.
When creating or editing a Cumulocity Plug for the application Asset Insurance, you can now also enter the input field Missing Asset Device Group ID.
When adding a device, you now will see the loading spinners again when a step is loading.
We introduced the ThingsML for LoRa payload decoder! ThingsML is a generic payload protocol you can use to let KPN Things automatically decode your device payload before sending it to your application. More information on ThingsML can be found here. Enable the decoder when adding another device or on the project detail page.
In the list of activated decoders and encoders in your project, the device type is now shown, making it more clear for which devices the decoder/encoder works.
You can now add a device via the All Devices page, making it easier to first work on your device and later on your data processing
When adding a device to your group, you can select existing devices now as well!
The header logo and favicon have been upgraded.
Deleting a device has now been improved.
Sometimes when registering you would get a "Registration failed" error, but the registration would succeed nonetheless. This false error is now fixed.
On the project detail overview page an activated encoders section is added together with an extra column named 'device specification name'. This column was also added to the activated decoders section.
On the All Tenants Page (only visible for specific user roles) a user is able to click and impersonate a certain other user in a certain tenant for which the user is authorized.
When you start impersonating the sidebar is adjusted to help the user find the correct information and see which user he is impersonating
Notifications will now automatically disappear after ~9 seconds
The Delete Plug dialog has been improved and now automatically deletes the plug from all its group(s)
All table headers have been improved and aligned
On the all plugs page, for each plug is now shown in which projects and to how many groups this plug is linked. This should create some more context when working and managing plugs and should visualize the impact of a configuration change.
The device detail page has been improved! By introducing the tabs the user has a more focused view on the data he is interested in. The tabs provide convenient access to existing elements such as the data history and downlink messages. Furthermore in the groups tab you can now see to which groups your device is linked.
Forms have been reworked over the entire portal to be more descriptive and at the same time less intrusive. Navigating through the fields of a form will not immediately show any errors. Errors will start showing up when the user really starts interacting with the form (editing a field, clicking submit ...)
Titles of several tables have been improved to better reflect what is shown.
All notification messages will now disappear after 9 seconds (regardless of the type/ severeness of the notification). When the user hovers his mouse over the notification, it will stay put. As soon as the mouse leaves, the 9-second timer will start again.
On the data history tab of the device detail page, clicking on refresh will now cause the expanded data row to collapse.
The plug detail page has been improved! By introducing the tabs you can now also see to which groups your plug is linked.
Clicking on a plug on the plug overview page now directly gives you the newly improved plug detail page.
The plugs in group has been introduced and it has been connected to the new plug detail page as well!
Certain product definitions on your project would break the product detail page. That is fixed now.
Page titels (the one in the green bar) has been corrected and standardized over all pages.
Breadcrumbs on all pages have been corrected if necessary.
Now all submit buttons of forms will show a spinner while processing input, so fast people cannot add objects multiple times anymore.
We introduced new overview pages for both projects and groups! Overview pages will provide you with one clear overview of the project or group. You will find the new pages when browsing through your Portal starting from "All Projects".
The LoRa message logger has been improved! Head over to the device detail page of your LoRa devices to see the result.
The complete table has been reconstructed for better usability
LoRa Geolocation results are now much more clear
We added a date filter and a "show more" button
The automatic time-out of your session due to inactivity is extended to 2 hours.
The visual margins of page content have been tweaked.
Sometimes when creating a device you would get the incorrect error of "You do not have a LoRa subscription". This has been fixed.
A minor fix to the applications field in the Cumulocity plug form has been deployed.
Sometimes when creating a plug, errors would be displayed correctly.
Enforcement of plug limits for freemium users has been fixed.
It is now possible to send downlinks to your LoRa device! Head over to your device detail page and you will find the newly introduced "Send data to device" field. If you want to learn more about sending downlinks to your LoRa device, read on here.
You can now add existing plugs to existing device groups! Before, you could only add a plug to a device group when creating one of the two. Now, when you go to your device group detail page and you click on the Add plug button, you get a page where you can either select a plug that is not yet connected to that device group, or you can create a new plug.
When entering your DevEUI/AppEUI/AppKey while creating a LoRa device, the values will be validated before sending it to the server and the feedback is more descriptive.
The HTTPS plug form has been improved
Added explanation of the shared secret
Made the headers field optional
When updating, you do not have to reenter your shared secret anymore
The Azure Event Hub plug form has been improved
The explanation of the URL field is improved
The SAS key and SAS key name fields have been switched
The Cumulocity plug form has been improved
When updating, you do not have to reenter your username and password anymore
When getting an error when creating a device, we now really don't create the device
Deleting a device at the device overview page does not remove the network info anymore when it says the deletion has failed
The login and logout pages now correctly show that you are a "KPN Developer"
URL validation is now even more correct
Not entering a custom fragment for a Cumulocity Plug does not create a custom fragment with value empty string anymore
When trying to create a Cumulocity Plug that does not send measurements and does not send location update events, it will now succeed
The tooltip for the FCnt column in the advanced data logger has been fixed
With the newly introduced All Devices page you have a quick overview of all the devices you have in your Things Portal. It also gives you quick access to the details of one of your devices.
The login and registration page now have a nicer side image
The side menu has been upgraded! It now provides a better overview of all accessible features and you can access your projects even faster.
When deleting a device, the device would disappear, but I would not be deleted from the database. That is fixed now.
When entering a DevEUI, AppEUI or AppKey with hyphens (-) or underscores (_) we will ignore these characters.
Add refresh button to advanced data logger for LoRa devices. Now you can check for new messages without having to refresh the complete website!
Implemented cache busting to provide a smooth upgrade of the application code
Change order of DevEUI/AppEUI/AppKey fields to better match what others do
Order the decoder options alphabetically in the device provisioning
Add more explanations on login and register pages
Multiple registrations with the same email address are not possible anymore
Device can now be edited again
On device detail page really show DevEUI value, not SenML base name
Notifications now disappear when going to another page
Learn how to connect your application through HTTPS
Learn more about Destinations in KPN Things.
You can use KPN Things Destinations to forward your device data to any supported platform or destination. KPN Things Destinations are part of KPN Things Data Management component. Read more here.
The tool Webhook.site is used for this tutorial. Although we have good experience with this tool, KPN is not responsible for the proper working of the tool.
Go to https://webhook.site. Webhook.site is a service with which you can easily inspect incoming HTTP requests. When vising the site it will automatically create a unique HTTPS endpoint for you. Use the Copy to clipboard button that is highlighted in the screenshot below to copy the URL of your new endpoint.
Go to the All Destinations page and click on Add new Destination.
After selecting HTTPS Endpoint, fill in the following information:
Destination name: you can think of a good recognizable 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.
Click Add HTTPS Endpoint to save the destination.
At the moment, Destinations cannot be tested stand-alone in the Portal. To verify the connection to your server or application, you need to continue with the next tutorial. After linking the Destination to a Flow with a Device, you will be able to verify the proper working of your Destination, since you then will be receiving data from your Device.
We are working on bringing Destination verification and testing to the Portal.
Learn how to forward the data from your device to your application
Learn more about Flows in KPN Things.
If your Project was delivered with already a first Flow, you can skip this step.
Click in de side bar on My first project to open your Project
Click on Flows in the submenu to see the Flows in your project
Click on Add Flow (#3 in the screenshot)
Enter a Flow name, like My First Flow, and click on Create Flow.
Click on Add Devices in the Flow overview page.
In the next screen, click Link an existing Device.
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!
Open your Project, open your Flow, and than 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 above). Click on the link in the description of a decoder of you want to know more.
Again, go to your freshly created Flow overview, but now click on Add Destinations.
In the next screen, open the drop down and select the destination you created in the previous step (Step Connect an HTTPS endpoint).
Last thing to do is to click Add Destination.
Now your Destination is linked to your Flow.
Learn how to send a dowlink to your LoRa device.
Go to the All Devices page and click on the device you want to send a downlink to.
Open the Send Instruction tab. There you will find the input fields to send a downlink to your LoRa device:
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.
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.
Downlinks will only be send to LoRaWAN Class A devices in answer to an uplink, so in order to receive the downlink we should trigger a message from our device. Then the downlink should be send in one of the receive windows.
For example for a Marvin device, the uplink and downlink messages should appear as such in the module communication log:
Now when you refresh your status downlink table, you will see that an i-icon appeared, stating the following when you hover over it:
This means that your downlink has been sent to your device by our network.
Now go to the Data History tab and click on the top downlink record (#2 in the screenshot). You should find your requested downlink information, FPort and Payload, back in the Content data (#3 in the screenshot).
If you get all the confirmations of your downlink in the Portal, but not on your device, that means your device dit not have enough network coverage to receive the downlink. Sometimes devices have better uplink coverage then downlink coverage, so it can happen that downlinks do not reach your device. Or random physical phenomena are the cause of your lost downlink. Move to closer to the window of you are inside or just retry your downlink to get success.
It could happen that the downlink switches to FAILED on trying to send the downlink to your device. In that case also an i-icon has appeared in the downlink status table, stating the reason why it was not possible to send your downlink. Often it has to do with the network. If this happens, please send your downlink again, the error should not happen often.
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.
Are you interested in sending downlinks to your Devices through API calls instead of through the KPN Things Portal? That is also possible! Head on over to our API access documentation in the Developer Manual to learn how.
💎 Add-on feature This feature is only available when purchased the Customer Management add-on. Please contact iot@kpn.com if your are interested!
With Customer Management, you get the possibility to manage your own customers using separate customer environment in KPN Things. It is an extra administrative layer in the KPN Things Portal.
If you have Customer Management enabled in your KPN Things license, you will have an additional link in your side menu: All Customers (as indicated in the screenshot below). Click on it to open your customer list.
After clicking All Customers in the side menu, you will get an overview of all your customers.
In the screenshot the following elements are highlighted:
The number of Customers in your current view and your total number of Customers.
The company name of your Customer.
The name of the primary contact of your Customer.
The number of Projects your Customer has.
The number of Devices your Customer has.
The number of Destinations your Customer has.
A quick link to the All Devices page of your Customer.
Clicking on a row in the table will direct you to the Customer details page of the selected Customer.
A search bar to search for a specific Customer name.
After opening one of your Customers, your submenu will change. The top part will stay the same and will provide you a way back to your own Customer environment (#1 in the screenshot below). The bottom part of the side menu will now show you navigation for the environment of your Customer (#2 in the screenshot below), allowing you to open and/or manage the objects in the environment of your Customer.
Adding new Customers will be added later. For now, if you want to add a new Customer, you should contact our service desk through the service portal.
The Customer overview page provides you with a quick overview of the environment of your customer.
On this page you find:
A summary of the properties of your Customer.
A link to the Customer details page.
The number of Projects of your Customer and a link to those Projects.
The number of Devices of your Customer and a link to those Devices.
The number of Destinations of your Customer and a link to those Destinations.
Quick links to add new objects to your Customer (buttons are disabled if you do not have rights)
After switching to the Customer environment, you see the Customer details page. This page gives you a quick overview of the Customer details, like name and email address.
Devices with M2M connectivity have some specific tabs on the to display M2M specific information.
When registering an M2M device to KPN Things, some information needs to be provided:
IMEI - The IMEI number that uniquely identifies your device. This value is used for authenticating the device when IoT data is received by the system.
Shared Secret - The pre-shared password used for authorizing ingestion of IoT data from the device by the system. This value is not required for all types of M2M devices.
Additionally, Things needs to know the ICCID of the SIM card that is inserted in the Device. The ICCID that uniquely identifies the SIM card. This is used for connectivity management and sending SMS to the device if configured.
Learn more about .
MSISDN - MSISDN is a number uniquely identifying your M2M subscription in the mobile network. It is also known as phone number, or 06-nummer in Dutch. Although M2M SIM cards often have a 079-nummer.
Rateplan - The commercial bundel of your SIM card.
Coming soon
Devices with Internet connectivity have some specific tabs on the to display Internet specific information.
DvnUUID - UUID to uniquely identify the Device data coming in.
Shared Secret - The pre-shared password used for authorizing ingestion of IoT data from the device by the system.
Learn more about connecting your Device .
When generating your own DvnUUID we advice to use a .
Each project defines a solution you buy or build in KPN Things.
A project has the following attributes:
UUID - the technical identifier of your project.
Name - the name you give to your project.
Description (optional) - further explanation of your project.
Creation date - the moment your project was created.
Subscription - the type of project you have, determined by what product you bought.
The project subscription determines what you can and may do in the KPN Things Portal. Some KPN Things provide you with more features in the Portal then others.
Depending on the Subscription of your Project, one or more of the following restrictions can apply:
This is an overview of all your Projects. Each Project defines a solution you buy or build in KPN Things. If you are a free user, you will get one project named My first project.
The number of Projects you have.
Information about all your Projects
Do you want to upgrade one of your Projects? Click on Upgrade Subscription.
The Project overview page gives you a handy overview of a selected Project.
The name, description and type of subscription of the selected project.
Depending on the number of Flows in your Project, you will have
No Flows: A link to create the first Flow in your Project
1 Flow: A direct link to the one Flow in your Project
The number of unique Devices in your Project. A Device that is linked to two Flows in your Project still counts as one.
The number of Destinations links in your Project. A Destination that is linked to two Flows in your Project counts as two.
On this page you will find technical details of your project.
At the project details page, you can edit the name and description of your project yourself.
This page lets you manage the Flows in your Project. This page can be reached quickly using the "Flows" link in the side menu for the Project you have opened.
It shows you:
The number of Flows you have in the current Project.
Button to add another Flow to your Project.
After clicking on Add Flow on the Flows in Project page, you see the following screen:
Here you can enter a name for your new Flow (#1) and an optional description (#2). Then click Create Flow (#3) to create the new flow in your Project.
Since (2nd June '20), Groups are called Flows.
With a Flow you configure the way your IoT data should flow through KPN Things. You link one or more Devices to one or more Destinations through the Flow, and you determine the Data Processing in between. So, if data is received from a Device that is linked to a Flow, it's data will be processed as configured and then forwarded to the Destinations that are linked to the same Flow.
A Flow has the following attributes:
UUID - the technical identifier of your Flow.
Name - the name you give to your Flow.
Description (optional) - further explanation of your Flow.
Data Processing can be configured on the .
Data Processing configuration is the most important part of a Flow. It expresses how data from and to your Devices should be processed by KPN Things. This processing is useful, because your Destination does not always understand what your Device is saying, and vise versa. This data should be transformed or interpreted between your Device and Destination.
We distinguish two type of actors that process data:
Decoders process data coming from your device (uplink data).
Encoders process data going to your device (downlink data).
We distinguish three types of data that can be enabled to forward to your Destination. Each type has its own symbol that is used in the name of the Decoder.
Downlink data configuration has to do with the data send to your Device. Often you want to send a clear instruction to your Device, which is transformed under water into a technical data message to your Device. This is where Encoders come into play. Next to that, also raw data can be send to your Device.
We distinguish two different ways of sending data to your Device, identified by a symbol in the name of the Encoder.
This page gives you an overview of the configuration of a Flow.
It shows you:
The name and description of your Flow.
Removed. The configuration of Device Twin values has been removed in favor of showing all possibles values by default.
The number of Destinations in your Flow and a smart link to the Destinations in your Flow.
The smart link allows you to quickly get to the Devices and Destinations in your Flow from the overview page. Depending on the number of Devices or Destinations you have in your Flow, the card will link you to a different view:
The Flow detail page shows the details of your Flow (#1 in the screenshot) and it allows you to edit the name and description of your Flow by clicking Edit (#2 in the screenshot).
This page shows you the Devices that are linked to the current Flow.
Elements on this page are:
The number of Devices in the current Flow.
The list of devices, showing their name, device type and last message time.
You can sort the Device list by clicking on the column header you want to sort by.
A button to add another Device to this Flow.
Checkboxes that allow you to start bulk actions.
After selecting one or more Devices you enter the bulk editing mode. This allows you to select several Devices (#1 in the screenshot below) or all Devices at once (#2 in the screenshot below). After you completed your selection, click on the desired action in the bulk action bar in the bottom of your screen. In this case, you can Unlink all selected Devices from the current Flow.
When you have reached the maximum number of unique devices in your Project, you will not be able to add another device to your Flow. The Add Device button will then be grey and disabled.
Also, it can occur that you have reached the total maximal amount of Devices in your account. Then you can only link an existing Device to your Flow, you cannot add a new Device. In that case the Add a new Device button will be grey and disabled.
When adding another Device to a Flow, you have two choices:
Add a new Device - register a complete new device to KPN Things and directly add it to the Flow.
Link an existing Device - link a device that is already registered to KPN Things. You can add one Device to multiple Flows.
This page will show you an overview of all Devices already linked to your Flow and other available Devices. There are two methods to link existing Devices to a Flow:
By clicking Link on the row of a Device, you link that single Device to the Flow.
By selecting a checkbox in a row of a Device, you start with linking multiple Devices to the Flow.
After selecting one Device you can select more using the checkboxes (#1 in the screenshot below), or even select all Devices you have using the checkbox in the top row (#2 in the screenshot below). When you finalized your selection you can commit the linkage with the button Link selected (#3 in the screenshot below).
The Data Processing in Flow page shows you the configuration of the data processing for Devices in that Flow.
When you visit the page, it first shows you the Device types that are present in the Flow. For each Device type it shows the number of devices linked to the Flow (#1 in the screenshot below), and the number of Decoders and Encoders enabled for that Device type (#2 in the screenshot below.
If there is a possible issue with your data processing configuration, a warning icon is shown for the concerning Device type (#1 in the screenshot below) and a warning message is shown explaining the issue (#2 in the screenshot below). We offer three possible solutions for the issue:
Show you where to fix the issue (#3 in the screenshot below)
Fix it for you (#4 in the screenshot below)
Let you ignore the warning (#5 in the screenshot below)
This page shows you the Destinations linked to the current Flow.
On this page you can see:
The number of Destinations in the current Flow.
A button to add another Destination to your Flow. If you have reached the maximum number of Destination links in your Project, this button will be disabled.
When you have reached the maximum number of Destination links in your Project, you will not be able to add another Destination to your Flow. The Add Destination button will then be grey and disabled.
Also, it can occur that you have reached the total maximal amount of Devices in your account. Then you can only link an existing Destination to your Flow, you cannot add a new Device. In that case the Create a new Destination option will not be available in the drop down.
When adding a Destination to a Flow, you have two options, as illustrated in the screenshot above:
Create a new Destination
Select an existing Destination to link to your Flow
After selecting the desired Destination in the drop down menu, click Add Destination to link the selected Destination to your Flow.
A Device represents a single physical device that can send data to the platform. When adding a device to KPN Things, you register the following information:
Name - A descriptive name of the Device.
Barcode (optional) - The serial number of other code that is visible on the outside of the Device.
Description (optional) - More information about your Device.
Device type - What type of Device it is.
Network info - The information required to register the Device to the correct network.
In KPN Things the Device type is used to express the connectivity and data capabilities of a Device, like whether it is a LoRa or an M2M device, and its compatibility to Data Processing components such as decoders and encoders.
We have two categories of Device types, namely Own Devices, where you bring your own Device to KPN Things, and KPN Devices, where you buy a Device from us. 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.
Each Device in KPN Things will have a processing status. This will tell you whether data from and to that Device will be processed by KPN Things.
To connect a Device to KPN Things it needs either to be registered to our LoRa or M2M network, or it needs to be an Internet-connected device running our SDKs or other KPN Things compatible software.
Separate pages will explain more about the supported network types:
On the All Device page, you have an overview of all your Devices.
Elements on the page are:
Total number of Devices you have and see on the current page.
Device list of all your Devices with some information:
The Device name.
The Device type.
The primary identifier of your Device.
For LoRa this is the DevEUI
For M2M the IMEI
For internet the DvnUUID
The moment Things last received a message from the Device.
The Project the Device belongs to.
The number of Flows your Device is in. Hover over the number to get a popup with a list of Flow names.
Search element to search for your specific Devices. You can search by Name and Primary identifier.
Bulk manipulation options. Select some or all Devices and choose the bulk action from the action bar at the bottom of the page.
Sorting options, by clicking on a specific table header the table will sort by the selected value.
This is the place where your register new Devices and add them to KPN Things and our networks.
If you have more than one Project, you will have to select to which Project you would like to add your Device.
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.
This step will look differently, depending on the type of network information.
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.
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.
IMEI of your Device.
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).
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.
DvnUUID - the unique number to identify incoming data from your Device. Your Device UUID is prefilled, but you can enter any UUID you like.
Shared secret - kind of password.
The most impotant difference is that: Device deactivation can be used temporarily and is neccesary when you want stop data from devices being send to devices. As an example: a customer has not paid his invoice and in response this customer receives no data. Deletion is permanent. When you want to delete a device, you can log a ticket via our IoT Servicedesk to ask them to delete your devices. After the deletion, you can't onboard this device again.
In the table below you can read about the differeces between deleting a Device and deactivating a Device.
This page offers you all detailed information about your Device and its connectivity.
The elements on this page are:
Connectivity information card for your Device, depending on your network type.
A button to delete your Device. This will completely remove your Device from KPN Things! (Not available for KPN (managed) devices).
The Device information card contains general information about your Device:
The name of your Device.
The Device type.
The Flows linked to your Device.
The LoRa information card contains more LoRa specific information of your Device.
The DevEUI of your Device.
The moment KPN Things last received data from your Device.
The M2M information card contains more M2M specific information of your Device.
The IMEI of your Device.
The ICCID of the SIM card linked to your Device.
The MSISDN of the subscription linked to the SIM card in your Device.
The moment KPN Things last received data from your Device.
The moment your SIM card has been activated.
The rate plan of the subscription linked to your SIM card.
Button to unlink the current SIM card from your Device. (Not available for KPN (managed) devices).
The Internet information card contains more Internet specific information of your Device.
The SenML base name
The moment KPN Things last received data from your Device.
Currently you can only send data to your Device if your Device is linked to at least one Flow!
On this tab you can send data or instructions to your Device, and you can see the status of requested data/instructions. Data to LoRa devices is also called a downlink.
Depending on your device type, different ways of sending data/instructions to your Device will be available. These could be:
Some Device types allow you to send raw LoRa data to your Device. To do this, you need to enter two values in the form as shown below:
FPort - the LoRa application port you want to send the data on.
Payload - the data you want to send to your Device in hexadecimal characters.
Things M2M devices and Internet devices can communicate with SenML. So downlinks to these devices should also be SenML.
For KPN Devices we provide a predefined list of human readable commands that you can send to the Device. Simply select the desired command to send by clicking on the radio button (if multiple commands are available), select the desired value for the command from the drop down, and click submit.
If downlink is not available for your Device, you will see the following:
Often data or an instruction sent to your Device is not received immediately. Often the Device is in sleep mode and will be able to receive the data when it wakes up again. So to monitor the status of the requested data/instructions to your Device, you can check the downlink status table on this tab.
There are five downlink statuses, illustrated in the diagram below and further explained in the table below.
If your LoRa Device is not yet registered on the LoRa network, you can click Register Device on Network here. This will open a modal for you to enter the LoRa network information for this Device.
Additionally, you can perform some M2M specific actions:
2. Edit M2M Device Configuration - allows you to generate a new shared secret for your M2M device. 3. Switch SIM card - allows you to administratively switch the SIM card of your M2M device. 4. Unlink SIM card- allows you to administratively remove the SIM card from your M2M device.
In the Flows tab you can see:
A list of all the Flows your Device is linked to and the Project this Flow is in.
You can click on a Flow to open it.
You can click on Unlink from this Flow to remove the Device from that Flow.
Also you can add your Device to another Flow.
After you click on Link to another Flow in the Flows tab, a modal will open.
In this modal you can:
Select the Project to which you want to add the Device, if you have more than 1 Project.
Select the Flow to which to link your Device.
Optionally create a new Flow to which to link your Device.
Devices with LoRa connectivity have some specific tabs on the to display LoRa specific information.
Currently only LoRaWAN 1.0.x is supported. Also, only OTAA is available. ABP is not available since it is less secure.
DevEUI - Unique LoRa device identifier.
AppEUI - LoRa application identifier.
AppKey - LoRa device authentication and encryption root key.
Learn more about .
This tab shows you detailed information about the messages send to and from your Device from the perspective of our LoRa network.
Messages in LoRa data history are stored up to 1 month.
The message overview of LoRa data history gives you an overview of all message to and from your Device in descending order of time. So the most recent message is at the top of the list of messages.
What you can see here is:
The type of LoRa message.
Whether it was an uplink (🔵 blue) or downlink (🟢 green) message.
Whether it was a Join request, Join accept or regular message.
Whether the message was confirmed or unconfirmed, or whether the message carried an ACK.
Whether the messages contained data, mac, or both.
The exact timestamp of the message, with millisecond accuracy.
The frame counter value of the message. Uplink (FCntUp) and downlink (FcntDown) communication has its own counter.
An indication of the signal strength the message.
Click on the chevron at the end of a row to see more details of a message.
Search bar to see the message history up to a certain point in time.
Button to load more data history (if available).
When you open the details of a message by clicking the chevron at the right side of the row, you can see the following:
Details about the message signal:
The used Spreading factor.
The used LoRa channel.
The number of gateways that received the message (uplink only).
The Received Signal Strength Indicator (RSSI) of the message (uplink only). This gives you an indication of how strong the message's signal has been received by the best receiving gateway.
The Signal to Noise Ratio (SNR) of the message (uplink only). This gives you an indication of the amount of noise when the message was received by the best receiving gateway.
The Estimated Signal Power (ESP) of the message (uplink only). ESP is calculated from RSSI and SNR and gives an indication of the used link budget.
Details about the content of the message:
The LoRa application port on which data was send or received (if applicable).
The exact payload of the LoRa message (if applicable).
The exact MAC content of the LoRa message (if applicable).
Flags that were in the LoRa message, like ACK, FPending or ADRAckReq.
Details of the LoRa Geolocation result:
Coordinates of the calculated location.
Radius in meters, the theoretical inaccuracy of the LoRa Geolocation result.
This section will explain what you can expect when you first connect your LoRa Device to KPN Things.
In the screenshot below you can see the beginning of a typical LoRa data history. The message are shown in descending order of time, so the first message is at the bottom of the list of messages.
This means the network does not see any activity from your device. Try one of the following actions to fix:
Maybe the network coverage is not ideal at your current position. Thick walls or a sub-optimal antenne can cause issues. Try to move to a more exposed location for better coverage, like moving closer to a window.
It could be that your device is not sending the join request on SF12, the spreading factor with the farthest reach. Program/configure your device to use this spreading factor when joining to increase coverage of your device.
After receiving the join request, the network will check whether the Device is known and whether the security details are correct. If so, the network will respond with a join accept.
This means the network sees your requests to join the network, but there is a (security) reason not to accept your join request. Try the following to fix it:
Check if your device is programmed/configured with the correct AppEUI.
Try to remove your device from the Portal and re-add it, maybe you made a typo when registering your device.
After your Device has received and processed the join accept, it can begin sending data.
This means the join is completed from the network point of view, but somehow your device does not see it the same way. Try the following to fix it:
Often join accepts are sent on the RX2 receive window. Is your RX2 receive window correctly configured? This should be 869525000 MHz and DR0 (SF12). Some device manufacturers have the device wrongly configured with the RX2 receive window listening on DR3 (SF9). (This is a common issue with Dragino devices!)
Sometimes the link budget for downlink is smaller than uplink, meaning downlinks are harder to receive than it is to send uplinks. This accounts for worse coverage for downlink than for uplink. Try to move to a more exposed location and try again.
It could be that there is a programming error in your Device that causes your Device to incorrectly process the Join accept. Please refer to your device manufacturer documentation for more help on that.
It could be a LoRa reception problem, due to configuration problems or insufficient coverage. You can check the possible solutions for "I don't see uplink data appearing in the LoRa data history!" above for more info.
Download messages are messages send by the network to your Device. These can be mac messages, containing commands to your Device about LoRaWAN transmission settings, or they can contain data from your application or from KPN Things.
After a Device has joined, the network will send up to three downlink messages with mac commands in them.
Now your Device will go into normal operation, often meaning periodically sending uplink messages. In the screenshot below you can see a typical LoRa data history.
Make sure your Device does not send more often than once every 5 minutes on average.
Each mac command consists of a request and an acknowledge message. So mac messages should come in pares in the LoRa data history.
If this is often not the case and you see that downlink mac messages are not answered by the Device, please check your Device, because there might something wrong. If your Device does not follow up mac commands, the transmission settings cannot be optimized.
Make sure your Device responds to all mac commands.
Not every uplink message will give a new calculated LoRa Geolocation. This is normal. It can be caused by the fact that too few gateways received the uplink, or if other circumstances were sub-optimal.
When a value for FCntUp is missing in the LoRa data history, it means that that specific message has not been received by the network. In LoRaWAN communication it is normal to have lost messages, your application should take this into account. It is a side-effect of the very energy efficient way LoRaWAN works. In normal situations you can expect up to 5% message loss. If your losses are higher, coverage on the location of your Device might be temperate.
If you see a join ceremony before each first message (FCntUp = 0), there is something wrong with your Device. Maybe it is losing power in between data transmissions or there is another reason your Device rejoins after each message.
Your Device should not rejoin after each message, because it puts unnecessary stress on the battery consumption of your device and it prevents the network to optimize the LoRaWAN transmission configuration through mac commands.
Make sure your Device remembers its join in between uplink messages.
If you see your Device (almost) only send Confirmed uplink messages, your Device is not properly configured. Sending too much Confirmed uplink messages puts too much demand on downlink communication, since every Confirmed uplink message requests a downlink message containing an ACK (acknowledgement) from the network. The network has not been designed to handle constant Confirmed uplink messages. This will negatively impact the overall capacity of the network. Therefor the use of Confirmed uplink messages is part of our Terms of Use.
No more than 10% of the uplink messages of your Device may be Confirmed messages. All other messages must be Unconfirmed.
The KPN Things Portal is the website where you manage and control your 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.
The KPN Things Portal is the visual interface with which you configure your solutions on the KPN Things Data Management platform.
After you logging into the KPN Things Portal, you will see the home screen. This will give you an overview of everything you can on the Portal. Below the numbered items in the screenshot are explained.
The Customer Details page can be reached through the account menu drop down (in the top right of the Portal interface).
This page shows you the details of the subscription you or your company has on KPN Things.
On this page you see the general details of your KPN Things account:
The customer details we have on you.
The unique Customer ID of your account. Useful when contacting support.
Additionally the page shows which network subscriptions are part of your Things account.
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
Write a captionWrite a caption
You can find applicable restrictions on the of a Project.
Link to the .
2 or more Flows: Link to the in the selected project.
An overview of the Flows in the current Project, the number of Devices in those Flows and a link to the and .
Uplink data configuration has to do with to the data send from your Device and possible metadata coming along when data is send by your Device. An example of the latter is , location data that the LoRa network can determine when receiving the message from your Device.
A link to the , where you can edit the name and description of your Flow.
The number of Devices in your Flow and a to the Devices in your Flow.
A summary of the Data Processing in your Flow and a link to the .
A delete button to remove your Flow. All Devices and Destinations that were linked to the Flow will not be deleted, they can still be found on the and respectively after you deleted your Flow.
If there is an issue with the configuration of your Flow, a warning icon is shown in the description of the concerning part of the configuration. Click on the warning label to .
When you click on a table row, you are sent to the of the selected Device.
This page is identical to the coming from the , with the additional step of Decoder activation.
At this step you can select the decoders you want to enable for this device type in the current Flow by checking the corresponding decoder (like #1 in the screenshot above). If you have previously activated decoders on this Flow for this Device type, they will be already checked (like #2 in the screenshot above). .
After you clicked on one of the Device types, all available Decoders (#1 in the screenshot below) and Encoders (#2 in the screenshot below) are shown for that Device type. The toggles to the right of the list (#3 in the screenshot below) indicate whether a Decoder or Encoder is enabled for that Flow. .
A list of the Destinations in this Flow with their name, status and type. By clicking on a Destination, you will go to the of the selected Destination.
This page is identical to the coming from the .
| Status | Description |
|---|
Clicking on a row will open the of that Device.
Link to .
A lock 🔒 icon for KPN (Managed) devices. For such devices fewer editing options are available. We have a .
Depending on your , available Device types may vary.
| Deactivate Device | Delete Device |
|---|
for devices with LoRa connectivity.
for devices with M2M connectivity.
for devices with Internet connectivity.
Connectivity data tabshowing you detailed data history to and from your Device.
tab for devices with LoRa connectivity.
tab for devices with M2M connectivity.
tab allowing you to send data to your Device.
tab showing you more details about your Device.
tab showing you the Twin of your Device.
Connectivity info tabshowing you more details about the Connectivity configuration of your Device.
tab for devices with LoRa connectivity.
tab for devices with M2M connectivity.
tab showing you detailed information about the Flows your Device is linked to.
The of your Device, which you may be able to update.
Clicking on the Device name or Device type will open the with more information about your Device.
The .
Clicking on the DevEUI or the Type = LoRa part of the card will open the with all LoRa specific information of your Device.
The with the possibility to change its value.
Clicking on the IMEI or the white part of the card will open the with all M2M specific information of your Device.
The .
Clicking on the base name or the white part of the card will open the with all Internet specific information of your Device.
LoRa data history will show you all data and mac traffic sent to and from your Device up to one month ago. Learn more about .
- for own LoRa devices and supported LoRa devices.
- for any Things M2M or Internet device.
- for KPN devices. Learn more about .
- for devices that do not support downlink communication.
To see which methods are available for your device type, you can check the .
The input form in the Portal should be filled in with a valid SenML measurement list formatted as JSON. . The entered SenML measurement list does not have to contain base values, KPN Things will add those before sending the downlink to the Device.
If your Device is not yet linked to a Flow, doing this could enable Downlink for your device. A Flow is required to enable an encoder that is required for downlink communication. in de Developer Manual.
More information on sending data to your Device can be found in the .
This tab shows you detailed information about your Device configuration. Learn more about the .
This tab shows you the Twin of the selected Device.
You can read more about the you can find on this tab.
The M2M tab shows you detailed information about your M2M connectivity. You can read more about the you can find on this tab.
If your M2M Device is not linked to a SIM card, you can click Link Connectivity here. This will open a new page to allow you to link your Device to a SIM card. The steps you take for this action are the same as for .
If there is a possible issue with one of the Flows your Device is in, a warning icon is shown on the Flow tab link and in the row of the concerning Flow. By clicking on the warning icon of a Flow, you will continue to the .
Whether a result could be determined on that message (only available for uplink).
Below at the section you can find an even more elaborate example. If your LoRa data history is not the same as in the screenshot above, you can continue reading to understand the chronology of LoRa data history.
The first thing your device should do is try to join our network. With a join request, the device will ask to network whether it may join. Learn more about .
Check whether the LoRa registration was successful by checking the connectivity status on the .
Check if your device is programmed/configured with the same DevEUI you find in the connectivity details on the .
Check if your device is sending the join request on one of the default LoRaWAN channels.
Maybe you are completely out of reach of the network. You can check online.
Check if your device is configured with the correct AppKey. This could also have to do with the with which you should enter the AppKey in your device.
Using the timestamps for consecutive uplink messages you can determine the average sending interval of your Device. This sending interval should not be too high, since you might be violating the of KPN Things.
Want to learn more about LoRa connectivity? Head on over to our !
To manage your solution, you will have in KPN Things. These Projects can contain one or more , and in a Flow you link , Data Processing configuration and together. 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 vise versa.
The GRIP tenant ID of your account, useful when starting to use .
Symbol | Expected instruction |
| An instruction that will be transformed into data that the Device will understand. |
| Raw data that is forwarded as is to your Device by KPN Things. |
🟢 Active | Data coming from and going to your Device will be processed. |
⚫ Deactivated | Data coming from your Device will not be processed or forwarded by KPN Things. Also downlinks will not be sent to your Device. Data history will still be available, since Things will still accept data from your Device. The network connection is not denied. |
⚫ Not yet linked | Your Device is not connected to a Flow, so data will not be processed in KPN Things. |
Why use it? | Temporarily disable data from Device. (example: disable data for sub customers) | The device is end of life and should be tossed out. |
Can customers do it themselves? | Yes, in bulk and for individual devices. | No |
Is it permanent? | No, you can easily Activate the Device again in the Portal in bulk and individually. | Yes, the Device is removed from all KPN systems. You can not use this the device again. |
Does it influence billing? | No, remove from Flow to have it stop being counted (applicable to Modular customers, E2E customers are being billed by information in C8Y) | Yes, because it is also removed from the Flow. |
Impact on battery if Device is still turned on | Connection between Device and Network is not changed, so the Device continues operating as normal. | Network registration of Device is removed. Depending on how the Device is programmed it may continue operating as normal, but it will probably change to a more energy consuming mode because the device will (uselessly) try to reconnect to the Network. |
Can you check the operation afterwards? | Yes, because the Device object still exists, only has the attribute "STATUS" changed to "Deactivated". But once the Device is reactivated, you cannot see when it has been deactivated. | No, the Device is completely removed from all systems. |
Status | Description |
Pending | When a downlink is requested on the Actuator API the command will get the status Pending. This means the downlink is accepted by Things and will be processed shortly. If there is another downlink of the device already in Executing, the downlink will stay in Pending until the other downlink reaches a final status. Downlinks will be processed by KPN Things in order of request date, so FIFO. After the previous downlink has been finalized, it can take up to an hour or so for the next pending downlink to be taken into execution. We are working on it to shorten this period. |
Cancelled | Pending downlinks can be cancelled. Since a pending downlink is not yet being processed by network systems, KPN Things can safely remove the downlink from its queue. Cancelled downlinks will not be processed any further and will get the final status Cancelled. It is not possible to cancel a downlink that is in Executing, since we cannot guarantee the withdrawal of a downlink request that is already being executed by the network system. |
Executing | When there is at least one downlink in the queue for a device, so with status Pending, it will be processed further by the system. It will then be de-normalized and sent to the device. During de-normalization, sending and waiting for feedback on delivery, the downlink is in Executing. Only one downlink per device can be in Executing. |
Failed | When KPN Things does not receive acknowledgement of the successful delivery of the downlink, or if KPN Things receives a timeout on sending the downlink, the downlink will get the final state Failed. |
Delivered | When the delivery of the downlink is acknowledged by the device, the downlink will be set on final state Delivered. |
This page tells you the historical status of the KPN Things Portal.
LoRa data history unavailable in the Things Portal
Due to issues in the LoRa network, LoRa data history was unavailable for a short period of time.
The processing of LoRa messages was not effected by this issue.
Login unavailable for Things Portal
Due to an unforeseen certificate renewal by the login provider, it was not possible anymore to log into the KPN Things Portal. By updating the trusted certificates in our systems, we had the login flow working again at around 11:40.
We have received mentions that the same error was already present on Friday 12 September, so the issue could have been present during the preceding weekend.
LoRa message outage
During the aftercare period of the release of KPN Things Portal version 5 we detected that all data coming from LoRa devices was not being forwarded to applications. We solved this in the afternoon, meaning applications should only be missing data from 9:45 through 18:00 on that day.
You could use the LoRa message history to fetch missed payloads. Any questions you have regarding the platform disturbance can be posted below.
Limit | Description |
End date | The moment your project will expire. Make sure to extend your Project before this date to prevent loss of data. |
Device limit | The maximum number of unique devices allowed in your Project. Devices that are linked to multiple Flows in the Project only count as one. |
Flow limit | The maximum number of Flows allowed in your Project. |
Destination limit | The maximum number of Destinations allowed in your Project. Destinations that are linked to multiple Flows. will count for the number of links they have in this Project. |
Allowed Device types |
Allowed Network types | The type of networks that are available in this Project. |
Symbol | Output data type |
| Decoded data, so incoming encoded data transformed into understandable measurements in SenML format. |
| Additional data (decoders) enabling metadata corresponding to the message send by your Device. |
| Raw data, just forwarding data like it is received by KPN Things. |
Can be recognized by the 🔒 symbol in the Device list. |
Bring or Buy | Bring yourself | Buy |
Add to / remove from Portal | ✅ | ❌ |
Edit name and description | ✅ | ✅ |
Activate / deactivate in Portal | ✅ | ✅ |
Send / receive raw payload | ✅ | ❌ |
Send commands | 🟡 * | ✅ |
Device Twin - Reported state | ✅ | ✅ |
Device Twin - Clear measurements | ✅ | ❌ |
Device Twin - Desired state | 🟡 * | ✅ |
Device Twin - Metadata | ✅ | ❌ |
Status | Description |
⚪ Not yet linked to a network | Your Device is added to KPN Things, but Network information is still missing in able to register your Device to the network. |
🔵 Pending create | Your Device is being registered to the network. |
🟢 Active | Your Device or SIM card is registered to the network and should be able to join and send data. |
⚫ Deactivated | Your Device or SIM card is registered to the network, but labeled as Inactive, meaning incoming connections will not be accepted. |
🔴 Failed | The Device could not be registered to the network. Probably the Network info you entered to register your Device was incorrect or already in use. |
⚫ Inventory |
Number | Explanation |
1 |
2 |
3 | Quick actions block. Will contain more quick links in the future. |
4 | This block allows you to quickly access our support resources.
|
5 | Your license information. |
6 | Release notes with the latest information about updates and features of the Portal. |
7 | Your account menu drop down:
|
You need an account to get access to KPN Things. This can be a KPN Developer account or a MijnKPN Zakelijk account.
Both types of account are part of our GRIP platform. Grip is developed by KPN to provide secure and easy access to your (KPN) applications. Through the GRIP Portal you can manage your KPN application subscriptions and you can perform user management. The exact functionality you have in the GRIP Portal depends on the subscriptions you have for different KPN products. Learn more about GRIP.
If your MijnKPN Zakelijk account has administration rights for your company, you can perform user management in the GRIP Portal, which is accessible through the link below.
While user management is available in the GRIP portal of KPN Developer accounts, KPN Things only allows the primary user of a KPN Developer account to access KPN Things.
If you want to be able to access KPN Things with multiple users from your account, you need to upgrade to a paid KPN Things subscription.
If you have registered for free for the KPN Things Portal, you have acquired a KPN Developer account. Currently, only the KPN Things Portal is accessible for a KPN Developer account. In the near future, other KPN Developer products, such as the KPN API Store can be accessed using your KPN Developer account.
Do you want to get a KPN Developer account for KPN Things? Register for free here!
Do you wish to delete your KPN Developer account? Please send an email to iot@kpn.com with the request to be deleted from the KPN Things Portal.
Please attach a screenshot of your Profile page so we have the right information to remove your credentials from our system.
Are you interested to use KPN Things with your company? Or do you already have a MijnKPN Zakelijk account and do you want to add KPN Things to the products you are purchasing from KPN? Please contact our sales support through iot@kpn.com for more information.
✨ Early access feature Connectivity Management is an early access feature for M2M connectivity in KPN Things. If you are interested in testing this feature, please contact iot@kpn.com!
Connectivity management is part of Device management in KPN Things, just like Connectivity is part of your Device in real life. This is also explained on the concepts overview page.
But what if connectivity is not yet linked to a Device? For instance, you want to view all KPN Things SIM cards you have that are not yet put into a Device. For that and other overviews of your (unlinked) Connectivity we created the All Connectivity page.
This page gives you an overview of all Connectivity items you have.
The following elements can be found on this page:
The number of connectivity items you have.
An overview of your connectivity items, displaying the following information:
Type - Type of connectivity.
ICCID / DevEUI - Unique connectivity identifier.
Connection - Whether the connection is active or not.
Activated on - (only for M2M) When the connectivity was first activated.
Device - The Device name of the Device the connectivity item is linked to.
Bundle/Rate plan - (only for M2M) The set of applied rules for your SIM card, i.e. whether you may roam and how much data you can use.
APN - (only for M2M) the APN(s) your SIM card may connect with.
Clicking on a row will open the Connectivity detail page of the selected connectivity item.
A search bar to search in Type, Identifier and Connection.
It is not yet possible to order more SIMs through the Things Portal. If you want to add more SIM cards to your account, please contact us:
For Developer accounts: through iot@kpn.com
For MijnKPN Zakelijk accounts: through the IoT service portal.
Once your Connectivity is linked to a Device, the Connectivity detail page will be unified with the Device detail page. i.e. They will be identical.
The Connectivity detail page gives you insight into Connectivity items. It depends on the Connectivity type what information can be given exactly.
On the Connectivity detail page of an unlinked Things M2M Connectivity item - a SIM card - you can see the following:
Information of the SIM card:
The ICCID of the SIM card.
The MSISDN of the SIM card.
The connectivity status - Active or Deactivated.
The moment the SIM card has been activated for the last time.
The rate plan of the SIM card.
Button to link SIM card to a Device.
Once your SIM card is linked to an Things M2M device, the Connectivity detail page is the same as the Device detail page.
After clicking Link Device on the Connectivity detail page, you will be given a list of Device that do not have a SIM card linked to it.
On this page you can search for the Device you are looking for using the search bar (#1 in the screenshot above). By clicking Link in the row of the desired Device (#2 in the screenshot above), you will link the SIM card to that Device.
Next, if the selected Device does not have M2M device information yet, you will be prompted to enter the IMEI and shared secret for the Device (#1 in the screenshot). If you want, you can let the Portal generate a new shared secret for your Device with the Generate button (#2 in the screenshot). After entering the values, click Save to continue (#3 in the screenshot). Learn more about M2M device information.
After linking your SIM card to a Device, you will land on the Device detail page.
Since LoRa connectivity can only exist as part of a LoRa Device, the Connectivity detail page for a LoRa device is similar to the Device detail page.
In the KPN Things Portal it is possible to perform certain actions in bulk, meaning a single actions is performed on multiple objects at the same time. The following operations are currently supported as bulk action:
Add Devices to a Flow in the Link Devices to Flow page.
Add Devices to a Flow in the All Devices page.
Remove Devices from a Flow in the Devices in Flow page.
All historical bulk operations can be found on the Bulk Report page, directly accessible through the side menu in the KPN Things Portal. This page shows you all executed bulk operations and their results.
By clicking on a specific Bulk report you open its details.
The Bulk report detail page shows you every operation of the bulk action and whether the result was successful or not. This allows you to review past bulk operations and maybe fix some things if neccesary.
If you are interested in automating an administrative operation in the KPN Things Portal, you could also look in to KPN Things API access, allowing you to write your own scripts to perform certain actions in your KPN Things account.
Since Version 10 of the Portal (21th April '20), Plugs are called Destinations.
A Destination allows you to forward the data from your devices to another system. This could be a proprietary application or a cloud platform. When adding a Destination to KPN Things, we ask for the following information:
Name - A descriptive name for your Destination.
Description (optional) - Some more information about your Destination.
Destination type - The type of Destination you are adding. KPN Things supports several.
Created Destinations have additional information:
UUID - The technical identifier of your Destination.
Destination status - The operational status of your Destination.
Currently five different Destination types are supported by KPN Things. Each Destination type has its own configuration attributes and specific working, explained on the corresponding More info page.
The All Destinations page can be reached by clicking on All Destinations in the side menu of the Portal.
On this page you will find:
The number of Destinations you have.
A table with information about all your Destinations:
Their name.
Their Destination type.
In which Projects they are used.
To how many Flows they are linked.
Their Destination status.
A button to add a new Destination.
Clicking on a row in the Destinations table will link you to the Destination detail page for that Destination.
When adding a new Destination, you first have to select the type of Destination you want to add. Each Destination type has its own input form presenting you with all configuration options you have for the Destination.
Check out all available Destination types and click on More info to get more details about that Destination type. All configuration options are explained, as well as the detailed working of each Destination type.
After entering the correct values, click the Add button to add your Destination.
This page offers you with all detailed information about your Destination.
The elements on this page are:
The name of your Destination.
General information about your Destination.
Status information about your Destination:
The Destination status.
The Flows your Destination is linked to.
Button to deactivate your Destination. If your Destination is deactivated, this will be an activation button.
Destination Specification tab showing you detailed information about your Destination configuration.
Flows tab showing you detailed information about the Flows your Destination is linked to.
A button to delete your Destination. This will completely remove your Destination from KPN Things!
The Destination Specification tab shows you detailed information about your Destination (#1 in the screenshot below). Displayed information differs for different Destination types. The tab also offers you an Edit link to edit the configuration of your Destination (#2 in the screenshot below).
Secret values like passwords and access keys are never displayed in the Things Portal and are even not retrievable from our systems. This ensures complete security of these values.
The Flows tab offers you a list of all the Flows your Destination is linked to and the Project this Flow is in. You can click on a Flow to open it, or you can click on Unlink from this Flow to remove the Destination from that Flow. The option to link your Destination to another Flow from here will be added in the near future.
The Device Twin is a digital representation of your Device. It expresses how your Device is doing, so it gives you a clear overview of the state of your Device!
The image below illustrates how the Device Twin data are set and used. All data can be read through the Portal and the API per Device.
Below the four parts of the Device Twin are :
Reported state - the most recent values of (a part of) the data sent from your Device. So if your Device sends a temperature measurement and you have configured that temperature should be stored in the Device Twin, you will find the last known temperature of that Device in its Twin.
Desired state - the state you want your Device to be in. For instance, if your Device supports changing the sending interval, you set the desired state of your Device to the desired interval, Things will recognize the desired state is different from the reported state and a downlink message is send to the Device to switch to a different interval.
Observed state - information that KPN Things can derive from the behavior of your Device. Here you can find for instance the Device sending interval.
Metadata - static information about your Device you want to store in the Device Twin. For instance in which batch the Device was produced, or the color of the casing of the Device. That way you store all important information for Device management in KPN Things.
The exact content of a Device Twin depends on the data a Device sends, the commands a Device can process, and the metadata you add manually to the Device Twin. Not all attributes may have a desired part, and sometimes an attribute with a desired state may not have a reported state. Closing the loop on desired and reported state is in the end something you should do.
In order to get the Twin up and running for a Device, some parts need to be configured in advance.
Before the Device Twin is able to show some values, the Device must be added to at least one Flow. This triggers processing of the data and allows the system to feed the Device Twin.
All data we receive from the Device is shown in the Device Twin. Previously you were required to configure in the Flow, which values you wanted to see before anything was shown. This setting has been removed from the Flow configuration.
Currently the available controls for the Desired state of a Device is determined in the Device type. Since the Own device types include a large set of different devices, we cannot yet provide a Desired state for own devices.
So, the Desired state is only available for KPN Devices.
In the near future, it will become possible to define your completely own Device type and with that define the Desired state options for your Device.
When you open de Device detail page of a certain Device, the Device Twin tab will provide you with all the information from the Device Twin of that Device.
Before the Device Twin will work:
Your Device should be in at least one Flow.
The Device Twin tab will point you in the right direction if the prerequisites is not yet fulfilled.
After all the configuration is in place, the Device Twin will start filling up with every incoming message from your Device.
In the screenshot below you see an example of a filled Device Twin with labeled:
The reported state
The desired state
The observed state
The metadata
Additionally the Device Twin tab provides you with links to the Device Twin documentation (#5) and a link to the Device Twin configuration page (#6). There is also a refresh button (#7), allowing you to refresh the Device Twin values without having to refresh the complete page.
The state section has been divided into two sections:
Device – showing all state expressing the Device, for instance firmware information, battery information and mode of operation. The name of the measurement is used by KPN Things to determine whether it is a Device state.
Other – all other values.
Below we will discuss every part of the Device Twin in detail.
The reported state of the Device Twin is composed of (a selection of) the most recent values of measurements KPN Things received from your Device. For each measurement where a reported state is known, its value and unit is displayed, as well as the moment when this value was last received. If you hover your mouse over the exact date and time, a popup will show you how long ago the reported state was last set.
Some trivial units will be hidden in the Portal, like enum, /, and string.
In a future release it will be possible to change the desired state even before the first reported state has been stored in the Device Twin of a Device.
The desired state of a Device expresses how you want the Device to behave. It depends on the Type of device which desired state values are available for control. For each state value where desired state control is available the most recent requested desired state is shown.
Next to the desired state value the exact date and time is shown of the moment the most recent desired state change was last requested. If you hover your mouse over the exact date and time, a popup will show you how long ago the reported state was last set. A blue timestamp with a blue circle next to it shows that the desired state change is still underway. If this is the case, the popup will also show you that the state change is still underway.
You can click on a certain desired state to change it (not available for read only accounts). Some values can be edited with a dropdown (#1 in the screenshot below), other values with a free input field (#2 in the screenshot below). After committing the desired state change, the state change will be communicated with your Device. Since the desired state change translates in to a downlink, you can see further information about the status of the downlink on the Send instruction tab of your Device.
The observed state tells you about the behavior of your Device from the perspective of KPN Things.
Currently only the Send interval is determined by calculating the time difference between the two most recently received messages. That means that in the case of a LoRa device, the interval may show a multiple of the expected send interval, since the lost message was not received by KPN Things.
In the metadata of the Device Twin you can (manually) store information about your Device in a key-value manner.
By clicking on Add a metadata property (#1 in the screenshot below) you will be given the input fields to add new metadata and its value. Click Save to store the new metadata property. You can edit the value of existing metadata by simply clicking the value (#2 in the screenshot below) after which an input field is shown and a Save button to store the change. If you want to remove a metadata property you can simply click the corresponding delete icon (#3 in the screenshot below).
In the future it will be possible to view a selection of the Device Twin values on the All Devices page, allowing you to search, sort and filter on these values. This feature is still in development.
Below you find a list of the values you can expect in the Reported state of the KPN Devices.
BatteryVoltage in Volt
CO2Concentration in parts per million
Humidity in % relative humidity
Illuminance in lux
Motion in count
Temperature in Celsius
BatteryVoltage in Volt
CO2Concentration in parts per million
Humidity in % relative humidity
Pressure in Pascal - the measured atmospheric pressure
Temperature in Celsius
VOC in parts per million - measured Volatile Organic Compound concentration
BatteryLevelLow as true/false
BatteryLevelLow_beacon as true/false - the battery level low indication of the detected beacon
Count_LidOpen - number of times the bin lid has been opened
DetectedBeacon - DevEUI of the last detected beacon
Distance in meters - distance to the detected object from the fill sensor
DistanceMeasurementIsValid as true/false
LidOpenedSincePreviousTransmission as true/false
Temperature in Celsius
BatteryLevelLow as true/false
Sabotaged as true/false
Temperature in Celsius
BatteryVoltage in Volt
FirmwareCRC - unique code to express the firmware on the Device
FirmwareVersion
Mode
SettingsCRC - unique code to express the settings on the Device
AcceleratorActive as true/false
AlarmMode as true/false
BatteryVoltage in Volt
MotionTime in minutes
MovementIndication
NfcFieldDetected
Sabotaged as true/false
Temperature in Celsius
No additional data.
AccX in m/s2 - measured acceleration in the X-axis
AccY in m/s2 - measured acceleration in the Y-axis
AccZ in m/s2 - measured acceleration in the Z-axis
CompX in Tesla - measured compass orientation in the X-axis
CompY in Tesla - measured compass orientation in the Y-axis
CompZ in Tesla - measured compass orientation in the Z-axis
DvLat - geographical latitude
DvLon - geographical longitude
GpsFix
Heading in radians
Io31 in 1/0 - arbitrary bit
IoButt in 1/0 - whether the Device's button was pressed
IoMot in 1/0 - whether the Device is in motion
IoRxd in 1/0 - Device's external digital i/o value
Speed in m/s
Temp in Celsius
VBat in Volt - measured battery voltage
MovementIndication
BatteryVoltage in Volt
FirmwareVersion
Altitude in meters
GpsTime in seconds
Heading in radians
Latitude
Longitude
Radius in meters - the accuracy of the geographical latitude and longitude
Status
Temperature in Celsius
Velocity in m/s
TIME_ORIGIN or TimeOrigin
Interval in minutes or hours - sending interval of Device
Latitude
LocAccuracy - deprecated
LocOrigin
LocPrecision - deprecated
LocTime
Longitude
Radius - the accuracy of the geographical latitude and longitude
Find the answer to frequently asked questions on this page
For security reasons our platform uses the latest browser technologies for the KPN Things Portal. This means that the Portal will not work optimally in not-up-to-date browsers and underdeveloped browsers. Please use an up-to-date version of Google Chrome or Mozilla Firefox for the best user experience.
Your Portal will automatically log out when you are inactive for more than 2 hours. Use the button to go to your KPN Developer account homepage, or reenter https://portal.kpnthings.com in your browser's address bar to login again.
When you get this error, first check whether you already have registered a KPN Developer account with the email address you are using. Do this by trying to login. If you reach a page where you can enter your password, you do already have an account. You can use the forgot password link to reset your password in case you forgot.
You can read all the differences here.
To reset your password, execute the following steps:
Click Login
Enter your Email address and click Doorgaan
Click Wachtwoord vergeten
Enter your Email address again in the field for Gebruikersnaam and click Doorgaan
Choose E-mail naar ****@*****
Check your email for the authentication code, enter it in the field for Code in and click Doorgaan
Enter a new password and click Doorgaan
It should be between 10 and 100 characters
It should contain at least three of the following types of characters: capital letter, small letter, number, and special character
Your password has now been reset
You probably have an account from the early days. Back then, the LoRa network subscription was not enabled by default on you profile.
To fix this, click on your name in the top right (#1 in the screenshot) and click Profile (#2 in the screenshot). Then click Add Network Subscription (#3 in the screenshot).
In the following popup, submit the form. Then return to adding your Device to KPN Things. Now it should work.
When adding a device you can get the error "The network identifier already exists for this network type". This means the network identifier, DevEUI for LoRa or IMEI for M2M, you are using to register your device is already known in our systems.
You should delete the device record from the device table page using the three dot menu on the right side of the column.
When you are sure you did not register the same device earlier, please contact our support through our contact form and state the network identifier with which you got the problems. If you are trying to register a device that was also registered in the LoRa Developer Portal, please state the account name in your question to our support as well. We could transfer your keys from the LoRa Developer Portal to the Things Portal.
This means you try to add more devices to your account than is allowed by your subscription. You could try to remove another device from your registrations or you can contact our commercial support on iot@kpn.com to get more information on upgrading your subscription.
This means your LoRa device could not be registered to our LoRa network. Probably the DevEUI is already in use in another application on our network like Thingpark or the LoRa Developer Portal. If you want to register your device in the Things Portal, first remove the device registration from the other application. Then you can re-add the devices in the Things Portal.
After (re-)registering the device in the Things Portal, you should rejoin your Device to the network.
Since the DevEUI's you are trying to register are still registered in the LoRa Developer Portal, they cannot be registered in the Things Portal. DevEUI's can only be registered once in our network.
Please send an email to iot-developer@kpn.com stating your account name (email address) and the DevEUI's you want to be able to move. We will remove them from the LoRa Developer Portal and our network and we will answer you when we did it. From then on you can register your device in the Things Portal.
If you have a device with pre-programmed identifiers and key that you cannot change, you should contact your supplier to get the information.
If you registered a device and got the identifiers from KPN Things, then there is no way to reset your AppEUI or AppKey for your device at the moment. You should delete your device from your account and add it again, get new identifiers and program the device with the new identifiers.
In time you will be able to view the AppEUI in the Portal and you will be able to generate a new AppKey for your device without having to delete and re-add it.
Head on over to the What to expect on first use of the LoRa data history part of our documentation to find the solution to this problem.
The data from your device travels the following path to your application:
Device → Network → Processing (Decoder, etc.) → Destination (your endpoint or application)
You can check the following configuration items in the Portal to verify whether the path is correctly set up:
Does your device have (the correct) connectivity information configured?
→ Visit the device detail page and go to the Connectivity tab. You can check the information and if necessary add connectivity information.
Is the connectivity indeed activated?
→ Visit, on the device detail page, the Connectivity tab and verify that Network Status is set to ACTIVE. If not, read this FAQ.
Can you see data coming in from your device in the Data History?
→ Visit, on the device detail page, the Data History tab to verify incoming data. If you do not see your device joining, you could get more info in this FAQ. Else you should use your device documentation to get it to send data.
Is your destination configuration correct? E.g. the URL, etc.
→ Visit, on the destination detail page, the Destination Specification tab to check your destination configuration.
→We are working on giving you more insight into the logs of a destination, stay tuned!
Is your destination status Active?
→ Visit the destination detail page. The Processing status in the top right card should say Active. If this is not the case, click the Activate button in the top right of the card to activate the destination again.
Is your Device linked to the Flow?
→Visit, on the Device detail page, the Flows tab to check to which Flows your Device is linked. If the correct Flow is missing, go to Devices in Flow page, click Add Device, click Link an existing Device, and select your Device from the list.
Is your Destination linked to the Flow?
→ Visit, on the Destination detail page, the Flows tab to check to which Flows your Destination is linked. If the Flow is missing, go to Destinations in Flow page, click Add Destination, click Link an existing Device, select your Destination from the drop down and click Add Destination.
Is the correct decoder activated?
→ Go to the Data Processing page of your Flow. Click on the Device type of your Device. Verify that one or more Decoders are enabled (The device type can be found in the main card of the Device detail page).
→ If no correct Decoder is activated, click on the toggle of the desired Decoder(s) to enable it.
Do you have a question that is not answered here? In that case you can ask your question via our contact form!
Do you have any feedback on a specific page or element in the Portal? Use the Feedback button hovering on the right of the Portal pages to send your feedback to us!
Do you have a question, suggestions, complaint or compliment? Please feel free to discuss anything related to the KPN Things Portal with your peers via our contact form.
This page explains what you should take into account when transfering from the LoRa Developer Portal.
Your LoRa Developer Portal account will not work on the Things Portal. You should register for a new KPN Developer account to get access to the Things Portal.
If you connected your LoRa Devices using ABP, you should switch to OTAA. We do not support ABP anymore.
Don't register your devices in the Things Portal before requesting deletion of their DevEUI's from the LoRa Developer Portal.
Your devices should rejoin the network after the transfer.
If you have devices connected to the LoRa Developer Portal that are using OTAA, it is possible to move them to the Things Portal. You should request the deletion of your devices from the LoRa Developer Portal by sending an email to stating your account name (email address) and the DevEUI's you want to be able to move. We will remove them from the LoRa Developer Portal and our network and we will answer you when we did it. From then on you can register the devices in the Things Portal.
The data format received by your HTTPS endpoint will be different after switching to the KPN Things Portal. So you should update the code of your endpoint.
In the LoRa Developer Portal you configured one destination URL per device. In the Things Portal your will configure one HTTPS endpoint Destination for each destination URL you have. Then you will use to link the data from devices to this HTTPS endpoint.
The content of the HTTPS request your endpoint will receive is also changed. The data is now formatted as SenML and there is less metadata present in the data. Also the Token that was present in the query parameters is replaced by the Things-Message-Token header.
The HTTPS endpoint is fully documented here:
For the free access to the KPN Things Portal.
KPN Things Freemium enables Users to use KPN Things for free and speed up their development of IoT solutions. After reaching the limits of the free tier it is possible to upgrade to a paid subscription. In order to use KPN Things Freemium and included services such as LoRa keys, M2M SIMs (upon request), manuals and all other relevant services and materials, you have to agree with the following terms and conditions:
KPN Things Freemium is a free to use version of KPN Things. It is meant for testing and experiencing the KPN Things IoT product.
KPN Things Freemium is provided as-is: we do our best to keep the service running, but no agreements are made about availability, coverage, continuity or any other service level.
It is possible to upgrade to a paid subscription of KPN Things, for which separate or additional arrangements shall be agreed upon.
The KPN Things Portal is the user interface which gives access to the features of KPN Things (Freemium).Access to the KPN Things Portal is included with KPN Things Freemium.
The access to the KPN Things Portal shall include the possibility to use LoRaWAN devices/connections. This usage is limited to a maximum of 3 LoRaWAN devices/connections in this free period.
Users may send a maximum amount of 300 uplink messages and 30 downlink messages per day during this free period per device within the limits of regulatory duty cycles*. Users shall adhere to any regulatory requirement regarding the use of the services.
Users may send at most 10% of the uplink messages as Confirmed uplink message.
Usage is limited to the basic KPN LoRaWAN features, focused on getting started fast. Not all features of KPN LoRaWAN are included in this offer.
KPN has the right to stop offering any feature of the KPN LoRaWAN and the KPN Things Freemium at any time without giving reason.
Integration with User systems are conducted through same principles as the commercial KPN LoRaWAN service. This means that transition from the KPN Things Freemium to the commercial KPN LoRaWAN service should be relatively easy. However, it is not guaranteed to be seamless and will require effort from the User.
Any credentials, access codes, passwords KPN provides or user itself generates for access to the KPN Things Portal or KPN LoRaWAN, are the full responsibility of user. Any abuse thereof shall be for the account of user and user shall be responsible to keep these confidential and secure. KPN cannot be held liable for any abuse thereof and user indemnifies KPN for any damage as a result of such abuse.
Users can request 2 M2M SIM cards to experience and test with the KPN M2M connectivity (2G, 4G and LTE-M).
Roaming with the SIM cards is allowed within the EU.
Per SIM it is allowed to use 10MB per month.
The SIM cards cannot be used to access the open internet.
Whenever usage is detected that does not comply to the terms of use, KPN is allowed to terminate the connection.
Documentation that is available for KPN Things is meant to help Users get started. The materials found in this section are provided ‘as-is’ and with best-effort without further obligations from KPN or its partners.
KPN will offer no direct support for users of KPN Things Freemium. All questions will be answered via our .
Solutions with high security risk are not allowed in KPN Things Freemium. The User is responsible for the determination of such security risk.
Depending on the application of the KPN Things Freemium by the User, User may need to take additional security measures, such as additional protection of a Device, additional security of application servers used by User or additional encryption of customer data. User acknowledges that the foregoing falls outside the scope of responsibilities of KPN, appropriate measures need to be taken by the User.
Use of KPN Things Freemium is at User’s own risk. KPN has no responsibility regarding the use by user of KPN Things Freemium. Under no circumstances KPN can be held liable for any damages user may incur following this agreement or the use of KPN Things Freemium, unless such damages are the result of willful intent or gross negligence by KPN. The liability of KPN for any consequential damages, which shall at least include loss of profits, loss of goodwill or loss if data, is explicitly excluded.
KPN reserves the right, in its absolute discretion, to withdraw or to modify KPN Things Freemium and its conditions at any time or to stop providing access to user without prior notice and with no liability.
User is required to fill out personal details fully and truthfully and keep it up to date in the KPN Things Portal for the duration of the usage.
Subject to the limitations and conditions set forth in these Terms and Conditions, KPN shall grant User a non-exclusive, non-transferable right to use any software, hardware or other items provided for using KPN LoRaWAN and KPN M2M, such license is provided solely for internal purposes. KPN reserves the right, in its absolute discretion, to revoke any such grant at any time without prior notice and with no liability.
It is not foreseen that KPN shall process personal data on behalf of user. If user intents to use such personal data for which KPN may be considered processor, user shall inform KPN of its intention and it shall agree with the data processor agreement provided by KPN, before its actual processing of such personal data.
Any processing of personal data by KPN on its own behalf shall be in accordance with the relevant laws and regulations, including the GDPR and the Dutch Telecommunications Act, and the privacy statement of KPN at .
User represents and warrants that its use of the services is in compliance with an acceptable use, and specifically represents and warrants that when using the services:
It does not cause any disruption or hinder in the services provided to third parties, the KPN Network or any other network or device
It does not infringe a person’s personal life
It does not infringe any applicable laws or regulations
It does not infringe any third party intellectual property rights
These Terms and Conditions are governed by the laws of The Netherlands. The Agreement excludes application of the United Nations Convention on Contracts for the International Sale of Goods 1980. Any disputes between Parties arising from or related to these Terms and Conditions shall be exclusively submitted to a court of law with jurisdiction in Amsterdam.
Version: 31-5-2021
The device types that are available in your project. .
Your Device and its Network information is known in the system but not yet registered to the network. If you want you can activate the network registration on the .
Link to the overview of your Devices. .
Link to your Destinations overview. .
- Shows you details of your customer environment in KPN Things.
Your Profile - Your personal page for your user account. From here you can change your password for example.
Downlinks can be sent using the Portal web interface. This is explained in the getting started. Sending downlinks through API calls will be available later!
* LoRaWAN uses the license free 868 ICM-band regulated by Agentschap Telecom. Additional information can be found on .
Destination type
Description
Azure Event Hub
Send data from your Devices to an Azure Event Hub in SenML format.
Azure IoT Hub
Let KPN Things manage your Devices and send telemetry data in your Azure IoT Hub.
Cumulocity environment
Let KPN Things manage your Devices, send measurements and location updates to your Cumulocity environment.
HTTPS endpoint
Send data from your Devices to an HTTPS endpoint in SenML format with a method for origin verification.
MQTT broker
Let KPN Things connect to your MQTT broker and publish data from your Device to the topics you want.
Status
Description
🟢 Active
The Destination is operational and will forward incoming data.
⚫ Deactivated
The Destination is (temporarily) deactivated and will not send data to the configured endpoint.
⚫ Not yet linked
Your Destination is not connected to a Flow, so no data will be exchanged with the configured endpoint.
