LoRaWAN is not suitable for every use-case, so it is important that you understand the limitations. Here's a quick overview:
The LoRaWAN yes list:
The LoRaWAN no list:
We want you to create products that are as efficient as possible. This will get the most out of your battery, and doesn't require you to buy many gateways. If you follow these recommendations, you'll definitely build an amazing product!
min|avg|maxevery 5 minutes, or you could only transmit when you sensor value changed more than a certain threshold or have it triggered by motion or another event.
SF7BW125is usually a good place to start, as it consumes the least power and airtime. If you need more range, you can slowly increase until you have enough. You can also enable adaptive data rate (ADR), the network will then be able to automatically optimize your data rate.
We want to be able to handle as many Nodes as possible per Gateway. But as full-duplex radios are not widely available yet, a Gateway is not able to receive transmissions from Nodes while it is transmitting. This means that if a gateway is transmitting 10% of the time, it's not able to receive anything for that 10% of the time. This is even worse when you realize that a gateway can receive at 8 channels simultaneously. Except when it's transmitting. So while an idle gateway can receive transmissions from 8 devices, those 8 devices are worthless when the gateway is transmitting.
We want to build a network that offers high reliability. If your device transmits, the gateway should receive it. In order to keep the gateway availability as high as we can, we ask you to follow these recommendations.
Last edited by htdvisser, 2017-05-02 04:56:56