KotahiNet is shifting to a new band plan from 1 June 2017. This page provides the current- soon to be obsolete- band plan.

Band Plan

KotahiNet’s band plan is below. More information about why it was chosen and the benefits is in a blog post.

Channel Frequency (MHz) Bandwidth (kHz) Sp Factor/Data Rate
0 865.0 125 12-7/0-5
1 865.2 125 12-7/0-5
2 865.4 125 12-7/0-5
3 866.2 125 12-7/0-5
4 866.4 125 12-7/0-5
5 866.6 125 12-7/0-5
6 866.8 125 12-7/0-5
7 867.0 125 12-7/0-5
8 865.6 250 7/6
  • RX2 window: 867.2 MHz, DR0
  • Max power: 36 dBm
  • Coding rate: 4/5
  • Duty cycle: 100% (no duty cycle)
KotahiNet's band in relation to EU frequencies

KotahiNet’s band in relation to EU frequencies


At a minimum, there needs to be a MCU, LoRa 868 modem, antenna and power source. Typically there will also be a number of sensors or controllers plus a range of optional extras such as GPS, accelerometers, solar charging, etc.

To run the LoRaWAN network stack (software), there are two choices- either onboard the LoRa modem or by the MCU. Further information about LoRa modems and code to configure some of them is in the Developers section. This also has three quick start options to help understand what’s required and get going immediately.

Joining/Using the Network

There is no cost to test the network. Also check out the free connection offer. On an on-going basis, there is no cost to connect a few sensors or other end devices. Beyond the initial term free offer and community usage free offer, the cost is $1 per month per connected object subject to downward and upward negotiation based on quantity and location.

There are two ways for end devices to join KotahiNet’s network in line with the LoRaWAN specifications.

The first is OTAA (Over The Air Activation). In this case, the customer needs to send the Device EUI, App EUI, and App Key to KotahiNet for enrolling the device. KotahiNet can also generate one or more of these parameters for the customer to configure on their device.

The other option is ABP (Activation By Personalisation). To use ABP join, KotahiNet will provide the customer with Device Address, Network Session Key, and Application Session Key to configure on the device.

Data can be sent as confirmed (preferable) or unconfirmed transmission. As the network is bi-directional, data can also be sent the other way- to the device via KotahiNet.

Data Destination

The customer needs to choose where data from the device needs to be delivered. KotahiNet does not store data received from the device. The payload is in hexadecimal and can be end-to-end encrypted.

To send data to the customer’s chosen destination, there are two options.

The first is any secure communication protocol. WebSockets is preferred for efficiency. Other protocols are TLS Sockets, MQTT and HTTPS Push.

The second option is to popular cloud services. Pre-integration is available for Amazon AWS IoT, Azure IoT Hub, IBM Bluemix IoT Foundation, PubNub, Cayenne (myDevices), and

To make testing easy, data integration can be skipped in this phase by using a custom, free web page provided by KotahiNet using WebSocket. This web page is automatically populated with the customer’s hexadecimal data received by KotahiNet’s network and also includes diagnostic information like RSSI, SNR, spreading factor, frequency, etc.


Also see Network, IoT Networks, Use Cases, and Technology.