Some things that affect the maximum range of your sensors include, how many walls are between the gateway and the sensor, the thickness of the walls, the number of floors between the gateway and the sensor (for multiple story buildings), how much radio frequency is active in the building, etc.

You will have better connectivity success by keeping in mind our tips for deploying hardware:

Don’t mix LoRa networks.

If you are using a Public LoRaWAN network provider, or you are using our default Azure network, use one or the other. Ensure that at your facility you have every gateway configured and connected to use the same network. You can use different networks at different facilities, but we never recommend a mixture.

This includes custom gateway hardware that we may have helped you to configure to work on the platform. All gateways which are deployed at the location should all use the same configuration and network.

Always verify sensors are transmitting and have good coverage before calling the install complete.

After deploying Gateways and Sensors into a facility, it pays to ensure that everything is working as expected. By allowing data to flow in and using the dashboard app to verify sensors are transmitting fully as expected, you can reduce any future troubles.

This is an important step that we recommend everyone do after a deployment. Please see our dedicated article that goes through how to verify sensor transmission using the app.

Deploy multiple Gateways.

There are several advantages to deploying multiple gateways in your facility.

• Redundancy - Sensors will attempt to connect with any nearby gateway. If one gateway drops offline for any reason, there is a better chance that nearby sensors will continue transmitting if they can reach an additional gateway as backup.

• Improved Signal Strength - If a sensor’s signal strength (RSSI) drops too low, it may have difficulty reliably transmitting readings. The closer a sensor is to a gateway the better, yielding more certainty of capturing every data point and a stronger resistance to any intermittent interference.

In our testing of indoor facilities, it is safe to place your sensors in a range of up to 1,000 feet.

Deploy Gateways up high or on different floors.

If your facility has multiple floors, we recommend deploying a gateway at the top level and then on every other floor if possible. If you have a facility with substructure, we recommend deploying gateways on those levels as well.

Deploy both Ethernet and Cellular Gateways

Where possible, try to use at least one hardwired Internet gateway to rule out any temporary or interference that may result from having a 100% cellular connection (i.e. maintain redundancy in connection type). In addition, we recommend having UPS / battery backup to protect both Internet and Gateway connections in the case of power outages.

For facilities with substructures, we do not recommend using Cellular on those levels - deploy an Ethernet connected gateway.

For facilities with below ground parking structures, we recommend deploying an Ethernet gateway on those levels as a cellular-based connection is usually unreliable.

Deploy Gateways at opposite ends of the facility / opposite wings.

If your facility has wings where line of sight to nearby gateways is difficult (i.e. it would pass through several walls, including possibly to the exterior and then back to the interior) we recommend deploying a Gateway at both ends of the facility. This way sensors at either end will be able to easily communicate to their gateway and sensors in the middle will be able to use whichever gateway they choose is better.

Overlap Gateways where there are a large concentration of sensors.

If you will be deploying lots of sensors in a single area, we recommend ensuring that have two overlapping gateways to ensure: A) Backup in case of a failure in one of the gateways (redundancy) and B) to ensure adequate throughput should a burst of data occur (this is especially true in cases where your sensors support Local Backup and may start data a burst of recovery data in the event of prolonged outages).