Nature of issues

There are several issues that have risen in previous projects.
Issues have risen of the following natures:

1. Hub connectivity
2. Sensor connectivity
3. Inaccurate data

Hub connectivity

In most cases Hub connectivity issues are due to a wrong firewall configuration of the firewall: make sure to check this List of IP addresses for outgoing traffic

Sensor connectivity

We encountered multiple cases where the sensors didn't connect to the hub.

All these cases were caused by installing the sensors before the hub.

Solution is to remove the battery, wait for the capacitors to be drained (several hours, preferably over night), and insert a fresh battery.

In some cases the battery still provides enough power. We do recommend to always change the battery, as we can not tell how far the battery has drained.

This page describes more steps to follow concerning sensor connectivity: Sensor connectivity guide

Inaccurate data

Inaccurate data can have several causes. Therefor a few checks can always be made.

1. Do the sensor id's and location comply with deployment?
2. Are the sensors linked to the correct floor/building?
3. Are the sensors places optimally according to the Motion Tabs (Tracknet) install guide? 
   A downward facing orientation is always preferred for desks where possible
4. How are the sensors placed?
   Pictures help:
   1. What does a desk look like?
   2. What is the orientation of the sensor?
   3. Are the desks placed in corridors? If so how wide is a corridor?
   4. What are the dimensions of a desk? Height, width, depth?
5. Are all sensors placed the same?
6. For horizontal facing desk sensors, has the sensitivity been reduced? 
7. For vertical facing desk sensors the sensitivity shouldn't be reduced 
8. Does each location have the correct number of sensors linked to it? (e.g. 1 desk = 1 motion sensor)
   The Studio health monitor can help you with this check