Helium Network Overview and Basics
Tools to Determine Pre-existing Helium Network Coverage
Mapper and Cargo
After verifying that there are Helium Hotspots near the deployment site, you can gain additional insights using and cargo.helium.com. Whereas Helium Explorer shows Hotspot-to-Hotspot proof of coverage, both Mapper and Cargo show RF coverage from actual and past LoRaWAN network endpoints that have successfully sent data from that area to local Hotspots.
It’s easy to acquire your own Mapper or Cargo compatible GPS LoRaWAN network endpoint to personally verify Helium Network coverage anywhere.
The decentralized nature of the Helium network has enabled rapid network coverage expansion; however, care must be taken to verify that sufficient and reliable coverage exists for IoT solution deployments. In densely covered areas, the high redundancy of Helium coverage helps mitigate issues of offline Hotspots or RF propagation gaps. For many IoT use cases, such as citywide e-bike tracking, the existing Helium coverage is likely to be sufficient.
For IoT use cases that need to guarantee higher network service level agreements (SLAs), or that need to extend Helium network coverage, there are multiple options. Some of these options include:
- Deploying new Helium Hotspots to desired sites as part of the deployment of the IoT solution. These Hotspots can guarantee coverage at the sites, including deep indoor locations like basements and inside refrigeration equipment. Since these units are owned by the IoT solution providers, the solution providers can monitor them and ensure that the units don’t go offline. This allows the solution provider to offer SLAs within their network coverage footprint.
- Exploring hybrid deployments with commercial LoRaWAN operators that have packet purchasing roaming integrations with the Helium network. This option allows network coverage across the combined Helium and commercial LoRaWAN network footprint.