Troubleshooting - Stat Temp v2

This guide is designed to help you resolve any issues you may encounter with your device. Whether you are experiencing problems with the ESP BLE Prov app or facing connectivity issues after successfully pairing the monitor, this guide is here to help.

Connect to Wi-Fi:

For directions to connect your monitor to Wi-Fi, click here.

Firewall Requirements:

1. Does the web connection require users to enter information on any kind of captive portal/login page? This can block our devices from successfully authenticating. This will require IT involvement. 
2. Our Wi-Fi devices only support 2.4GHz networks. These devices will not connect to 5GHz networks. If bandsteering is enabled on your network, you may need to disable it.
3. Confirm these ports are open:
   1. TCP Port 8883 outbound (MQTT over SSL), destination address: iot.stattemp.io, IP addresses 54.173.251.106 and 3.221.75.93
   2. Port 123 (NTP), host: pool.ntp.org

Reset WiFi:

Sensor Troubleshooting

Missed Check-In:

A missed check-in notification is triggered when the sensor fails to record data for two consecutive check-in intervals. This may occur due to various factors, including hardware malfunctions preventing the device from taking readings, network connectivity issues that hinder communication between the sensor and the network, or server issues causing delays in data delivery. If you feel you are getting too many missed check-in notifications you can try these tips:

Server Delay Issues:

The frequency of sensor readings is determined by the environment policy, allowing for intervals ranging from 1 to 30 minutes. When the environment policy mandates a 3-minute reading interval, delays in reporting to the cloud can occur. In such instances, the readings are not missed but rather postponed. If this delay occurs frequently, we recommend adjusting the environment policy to increase the time between readings. Stat Temp advises a 30-minute reading interval for sensors operating within normal temperature ranges.

My sensor is too Cold/Warm:

If you are using multiple devices to monitor the temperature in your fridge or freezer, you may get two different readings. Here are some reasons why a temperature difference may exist.

Microclimates that exist within fridges and freezers can account for a 10-degree +/- temperature difference based on the location of the sensor. If the sensor is positioned near the cold air fan or the exhaust fan, this can cause inaccurate readings.

Our sensors are programmed to take the temperature at specific times specified in the sensor's Environment Policy. When compared to a second thermometer, the time a temperature reading was taken may vary and therefore cause a discrepancy.

To determine if your sensor is malfunctioning and running out of range, it is suggested that you triangulate the temperatures by placing 1-2 more thermometers in the unit being monitored, and compare their readings to the sensor's. If all readings align closely, it indicates the sensor is likely functioning correctly. However, if there are significant discrepancies among the readings, it may indicate a malfunctioning sensor that needs calibration or replacement. Additionally, regularly calibrating your sensors and ensuring they are placed in optimal locations within the fridge or freezer can help minimize temperature variations and ensure accurate monitoring.

Sensor Accuracy:

Our sensors are very accurate, and the manufacturer claims all sensors that leave the factory are accurate to within ±0.1ºC. A certificate was sent with your sensor and a digital copy is available upon email request to StatTemp@gohcl.com.

While accuracy describes how close your sensor is to the actual temperature, it assumes the temperature is stable. In a constantly changing environment, like a refrigerator or freezer, the response time of the sensor is equally as important as the accuracy. Two calibrated sensors can read different temperatures depending on their response times.