Nature of issues

There are several issues that have rissen in previous projects.
Issues have been rissen 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.

However a case has been encountered (Collins aerospace) with a hub certificate mismatch on the server side due to an outdated firmware version.
This issue has been resolved.

Should you encounter a similar issue, please contact Simon de Jager (Unlicensed).

The switch to The Things Networks will eliminate the chance of encountering these issues

Ethernet LED
The ethernet LED shows the connectivity status between the Hub and the Platform
Off: No network à Check if the ethernet cable is plugged in on both ends. Blue port for the Hub.
Orange: Connection not established à Check if the correct ports are opened. For Hubs connected to 4G check for sufficient throughput and instalment of 4G antennas
Green: Connected 

LoRa LED
The LoRa LED shows the readiness of receiving messages from the sensors. The hub will not accept messages if it is not connected to the platform
Off: Not ready à Check connection to platform
Green: Ready 

WI-FI LED
The hubs are preconfigured not to send out any wifi signals. The light may turn on during initial boot but will turn itself off after configuration is loaded. 

Power LED
Off à Powered off
Flashing Green à Boot mode
Flashing Orange/Green à Reset mode
Green à Powered on 

•       Can I reset the hub?
Yes, Press the reset button located between the power and blue ethernet until the power LED start flashing orange/green (approx. 20 seconds)
The hub will reset back to the original MCS configuration, this can take up to 20 minutes. 

•       Can I run my own configuration?
No, the hubs are configured with the MCS configuration.
Trying to reconfigure the hub with the tabs app will lead to malfunctioning of the hardware 

•       How can I test network throughput?
Connect your laptop to the connection under test
Go to a speed test website, e.g. https://www.speedtest.net/
Run the test 

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.

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 placement 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 occ sensor)
   The rhye health monitor can help you with this check