KPN LoRa Developer Portal

  • 22 september 2016
  • 30 reacties
  • 29543 keer bekeken

Reputatie 2
Badge +1

Getting started with the free KPN LoRa developer portal


The LoRa developer portal was built to enable developers free access to the KPN LoRa network. This portal allows testing with up to 10 devices for a period of 6 months.
The developer portal can be used for testing with Class A Activation-By-Personalisation (ABP) and Class A Over-The-Air-Activation (OTAA) devices. Note that on the KPN live network, only OTAA devices are allowed and it is thus recommended to start developing with OTAA right away.
All a developer has to provide is a forwarding address (endpoint) for the Application Server to get the device credentials (DevEUI, AppSKey and NwkSKey, in case of an ABP device). Upload these credentials to your LoRa device and you are good to go.

Differences between ThingPark and the Developer Portal


The aim of the KPN Lora Developer Portal is to enable users to quickly connect their LoRa device to the KPN Lora network. Where possible, the functionalities and concepts similar to those used in ThingPark (the portal for contracted customers) are applied for using the Developer Portal. This means that a device and Application Server working with the Developer Portal should also work with ThingPark. But there are a few differences:
  • The NwkSKey and AppSKey are generated by KPN (as a consequence, device-clientserver encryption is not possible).
  • Only device Class A is supported.
  • The same processes, elements and formats are used where possible, however there will remain some differences with full-scale implementation on the KPN LoRa network.
  • The Developer Portal is provided based on 'Best effort' support. This means no direct support and no uptime guarantees.
  • The Developer Portal is meant for testing purposes, no commercial exploitation is allowed
  • Fair use policy applies, limited downlink and uplink capacity (average 6 uplink/hour, 2 downlink/hour)
  • A limited duration of 6 months applies. After 6 months, accounts are automatically locked
  • An important difference between the developer portal and the KPN live environment is that the restriction on the ports that can be used is not implemented on the developer portal. In the live environment port 443 should be used for forwarding messages.

More technical information can be found in the documentation on the developer portal itself.

30 reacties

Reputatie 7
Badge +11
Hello Martijn, welcome to the LoRa Forum :)

However, these packets are not received at the given destination endpoint. (a node-red application server). I know this endpoint works because the same evening I also did some tests with the uplink test button in the developer portal, and those messages were successfully received in node-red.
Could you try and sent some (new) lora packets from the device to your application server? We already know your DevEui (from the image - thanks!). If you can let us know at what times the packets has been sent, we can try to look them up to see what's going wrong.
Hello Martijn, welcome to the LoRa Forum :)

However, these packets are not received at the given destination endpoint. (a node-red application server). I know this endpoint works because the same evening I also did some tests with the uplink test button in the developer portal, and those messages were successfully received in node-red.
Could you try and sent some (new) lora packets from the device to your application server? We already know your DevEui (from the image - thanks!). If you can let us know at what times the packets has been sent, we can try to look them up.


Well, I have a practical issue, the packets you see in my screenshots are transmitted during my car trip yesterday evening. The timestamps in the screenshot are correct.
From home I don't have enough signal to the closest KPN antenna...

Since you now have my DevEUI, is it an idea to do the same car trip this evening so you check the log tomorrow or don't you save any logging.. I can't do a car trip during the day...
Hi Tim,

I did a new test this evening.
You can see the packets in the screenshot. The screenshot also gives you the timestamp of the packets.


I also did an uplink test, and again ONLY this packet was received correctly and the packets from the screenshot not. I can even show you my proxy logging as a proof:
By reading the proxy logging I also discovered that my server time is one hour behind. I have to fix this.
So, please calculate +1 hour of the date/time you read below. (ps. Time= parameter from KPN is correct)

As you can see below I did two uplink test from the KPN dashboard to /kpnlora on the 16th of january; 13:24:27.295 and on 22:00:24.552.

nodered.searocket.io 213.154.238.21 - - [16/Jan/2017:12:24:27 +0000] "POST /kpnlora?LrnDevEui=0059AC00001811BD&LrnFPort=1&LrnInfos=null&AS_ID=XXXXXX&Time=2017-01-16T13:24:27.295+01:00&Token=XXX HTTP/1.1" 200 60 "-" "Jakarta Commons-HttpClient/3.1"

nodered.searocket.io 213.154.238.21 - - [16/Jan/2017:21:00:24 +0000] "POST /kpnlora?LrnDevEui=0059AC00001811BD&LrnFPort=1&LrnInfos=null&AS_ID=XXXXXX&Time=2017-01-16T22:00:24.552+01:00&Token=XXXXXX HTTP/1.1" 200 60 "-" "Jakarta Commons-HttpClient/3.1"

The screenshot from the KPN dashboard tells me that there were lora packets received on the 16th of january on; 20:55:01, 21:00:01, 21:05:02, 21:10:07, 21:15:07, 21:25:05, 21:30:01, 21:35:01, 21:40:02, 21:45:00

None of them showed up in my proxy logging.
  • Only device Class A is supported.



Is het nog steeds zo dat het Developer Portal alleen Class A ondersteund?
Reputatie 7
Badge +11

  • Only device Class A is supported.

Is het nog steeds zo dat het Developer Portal alleen Class A ondersteund?


Nee, voor zover ik weet ondersteunen we momenteel Class A & C. Zowel op de productie omgeving als op de developer portal.

Reageer