This article contains frequently asked questions about our motion detection sensors.
Where to place the sensor?
Can it be placed in the ceiling?
What area does the sensor cover?
The sensor covers approx. 90-degree angle. The placement is dependent upon the size of the room, but generally we recommend the following:
Sensor data sheet can be found here.
|How far can the gateway be from sensor?
The placement of the gateway depends on how may floors it should cover and the building material.
Our sensors and gateways are based on the LoRaWan standard (https://en.wikipedia.org/wiki/LoRa and the theoretical range is 10+ km in perfect conditions. However, indoor range is dependent upon a number of factors like building material, number of floors, walls, surroundings etc.
Based on our best practices, we will help you finding the optimal configuration.
Multiple gateways per installation is supported for redunancy purposes.
How long does the battery last?
How are batteries being replaced?
The life time of the battery depends heavily on signal strenght - the weaker the signal is, the more power is being used by the sensor.
If sensors and gateways are configured and placed according to our recommendations, the theoretical battery life time is estimated to be between 5 and 10 years. However, to be on the safe side, you should expect a battery life time of 3+ years.
You can also test our hardware vendor's battery life calculator.
The sensor runs on two batteries that can easily be replaced. The battery specifications are:
|The gateway does not send data||
Make sure that the gateway is reachable. In the sensor administration page, go to Status and toggle ping on:
Regardless whether it responds to ping request, the customer's network might have firewall rules preventing sensor data to be transferred. Try to connect the gateway to a 4G router or a non-local network to see if that helps.
|Sensor data is not received||
Sensor will need to be provisioned in order to start sending data. If a sensor doesn't send data, please follow these troubleshooting steps: