What are the on-site requirements for a BlueZoo sensor?

BlueZoo hardware sensors require power and backhaul to the internet.  BlueZoo software-only sensors (e.g. on the BrightSign player) use the processor / memory and backhaul of the BrightSign player.

The performance of the sensor requires correct placement of the sensor’s Wi-Fi antenna that is used for sensing (which is sometimes the same antenna as used for backhaul).

The Black Panther family of sensors were introduced by BlueZoo early in 2022 and this information presupposes Black Panther sensors, though most details apply to all BlueZoo sensors.  At bottom see information specific to earlier families of sensors (White Rhino, Arctic Fox, Yellow Mongoose, White Stork, and AR150-series).

Power

BlueZoo sensors without cellular backhaul require less than 2W power.  Sensors with cellular backhaul (e.g. White Rhino) require up to 10W of power due to the variable load imposed by cellular modems.  

Placement

BlueZoo sensors require a 2.4GHz antenna which can be internal or external to the sensor.  This sensing antenna can be *omnidirectional*, as is the antenna internal to BlueZoo sensors, or *directional*.

The accuracy of the BlueZoo measurement relies, in part, on the optimum placement of the antenna.  Please see the separate article about BlueZoo sensing antennas.

Backhaul

Several ports must be accessible through the internet.  Several options are available for IP address assignment.  Here’s the full list:

1. Internet access should be stable 24 hours per day.  Minimum bandwidth required is 500 kb / second.  The sensor sends bursts of packets every 15 to 30 seconds.
   
   
2. DHCP is the recommended solution for assigning an IP address to a BlueZoo sensor, though starting with firmware v4.0.6, Black Panther sensors can be assigned a static-IP address using the sensor web portal.  Otherwise, DHCP is required.
   
   
3. The following IP ports need to be open:

• TCP Ports 80, 443
  
  
• UDP Port 123 (for NTP clock synchronization; port is preferred but not required for the Black Panther sensors)
  
  

4. If connecting via ethernet backhaul, a proxy server and static IP address for the sensor can be configured using the web portal of the sensor.
   
   
5. If connecting via Wi-Fi backhaul:

• Channel used must be in the 2.4 GHz range (not 5 or 6 GHz).
  
  
• The access point can require a password, but may not use a proxy or captive portal.  For example, if your building's Wi-Fi access point requires that guests agree to terms and conditions before accessing the network, this access point cannot serve BlueZoo sensors.
  
  
• If the network uses port-based Network Access Control to restrict use of IEEE 802 access points (or ports) to secure communication between devices, authentication can be based on the static MAC address of the backhaul link (which may not be the same as the sensing Wi-Fi MAC).
  
  
• Crowded or unstable Wi-Fi environments can result in the sensor going offline, interrupting data collection.  Should the Wi-Fi at your location be unstable or insufficient, consider using an optional cellular modem with your Black Panther sensor.  The BlueZoo sensor should not be deployed on public Wi-Fi networks.

Details for legacy sensors:

1. Legacy BlueZoo sensors are White Rhino, Arctic Fox, Yellow Mongoose, White Stork, and AR150 series sensors.
   
   
2. White Rhinos can be configured to send system diagnostic logs via UDP Port 5514 (outgoing traffic only).  This port should be left open for delivery of these diagnostic logs.

Please get in touch with us for any questions or should you experience any network-related connectivity issues at your location.