In order to communicate with the Indoor Tracking server, the BLE nodes need to be able to connect to a wireless or wired Internet connection with the following requirements:
- Accessible domain: its.accuware.com and its.stura.io
- Ports (opened outbound): 53/tcp (DNS), 80/tcp (HTTP), 443/tcp (HTTPS), 1883 and 8883
- Proxies: the BLE nodes can’t works with proxies. If there is a proxy inside the Wi-Fi network used by the BLE nodes it is necessary to ask to the IT department the company to add an exception to the proxy to allow the BLE nodes (identified by their MAC addresses) to connect without credentials to the domains listed above using the ports listed above.
In addition to the requirements above, these are the network requirements that must be met by the Wi-Fi network that must cover entirely the area in which the BLE nodes will be installed:
- Wi-Fi SSID: visible.
- Wi-Fi security: no password, WEP-Personal, WPA-Personal , WPA2-Personal, WPA-Enterprise
- Wi-Fi frequency: 2.4 GHz
- Wi-Fi standard:
- b/g/n for V1 and V2 nodes
- b/g/n/e/i for V3 nodes
- Wi-Fi bandwidth: 20 MHz
- Wi-Fi splash page/captive portals: there must NOT be a splash page/captive portal. If there is a splash page/captive portal then you should ask to the network administrator to add to a white list the MAC addresses of the BLE nodes.
About behavior of BLE nodes V3 with both Wi-Fi and Ethernet
Once a Wi-Fi connection is set into the BLE node V3:
Once a Wi-Fi connection is set into the BLE node V3:
- if only the Wi-Fi connection is available it uses that connection.
- if only an Ethernet connection is available it uses that connection.
- if both the connections are available it prefers the Ethernet connection.
- if a connection was available and is not available anymore it uses as a fallback the other connection.