Migrating existing LoRaWAN network to Helium or joining Helium for new deployment is accessing to the world largest LoRaWAN network and enable your devices to be deployed in the large covered zone. By doing this you extends the community network and as a counter part getting benefit on future data transfer and immediately get an access to the low cost ecosystem (data transfer, network server, high redundancy network…)
In a previous post I explained how to configure a RAK Wisgate as a Helium Data-Only hotspot. In a such situation your LoRaWAN gateway becomes a hotspot relaying the Helium traffic and getting some little rewards for the data transfer. The more important is to extend the coverage. This way of doing is good but I’ve got some issues on the field: The data transfer from the hotspot to the blockchain (even if just the state channels) is high and the software, currently in alpha, is not totally stable. When deploying a gateway is isolated area to provide new coverage, honestly, these two issues are blocking points.
The second important consideration is the existing gateways, already deployed on the field: they are currently used for private networks. They have been deployed some years ago and are not in the compatibility list of Helium hardware. Even if they are, deploying a new software on them, remotely can be a problem.
For these different reasons, I’ve been investigating a different approach by creating centrally hosted hotspots connected to different LoRaWAN gateways through the legacy Semtech protocol. This is what we are going to detail on this blog-post.
Continue reading →Like this:
Like Loading...
