How to fix issues with Ops Execution Temperature Monitoring sensors and gateways

Temperature monitoring sensors and gateways can occasionally experience connectivity issues, offline status, or inaccurate readings.

Before beginning any troubleshooting, ensure you have identified which manufacturer's equipment you're using. This article provides manufacturer-specific troubleshooting steps for all Ops Execution supported temperature monitoring devices. Most issues can be resolved by following the appropriate steps for your specific sensor model and gateway type.

Monnit sensors and gateways

Troubleshooting steps for offline Monnit sensors

If your Monnit sensors are appearing as offline, follow these steps in order:

1. Keep it within 10-15 feet from the gateway. This eliminates the possibility of signal interference. Let it sit for 15-20 minutes, then check if it comes back online.
2. Press the gateway utility button. Give the utility button on the gateway a quick press. Do not hold it down - just a quick press is all that's needed. Holding it down will perform a reset, which you want to avoid.
3. For Ambient Standard Sensors, take the batteries out of the sensor and then place them back in. This resets the sensor's connection to the gateway.
4. Perform a power cycle. Power the sensor off for at least 60 seconds.

Warning: If you have Monnit sensors with industrial sealed housings, do not try to replace batteries. These sensors are sealed units and attempting to open them will damage the device.

How to fix Monnit gateway problems

• Monnit Gateways need your Locations to have a ZIP code to properly communicate. Ensure the locations you will place the sensors in have ZIP codes added.
• Unplug the gateway for 30 seconds, then plug it back in. When powering the gateway, it will perform a self-test to confirm that its hardware is operational. The LED’s will perform a sequence which many describe as a “waterfall display”. When this sequence completes, the gateway will have successfully performed the self-test. At this point, the gateway will attempt to retrieve an IP address via DHCP from the local Ethernet network. If the “waterfall display” does not complete, the LED’s will display a solid sequence.
• Verify the Ethernet cable is securely connected to both the gateway and your network port
• Check that the gateway's LED lights are functioning
• Ensure the gateway has proper network connectivity and can reach the internet. Confirm the network allows for traffic to the Internet over outbound TCP port 3000 (inbound port is not specified), and that the DNS server on the network can resolve sensorsgateway.com.

Radiobridge sensors

Radiobridge sensor

Troubleshooting steps for Radiobridge ambient sensors

1. Check battery tab. Carefully open the back cover and ensure the battery tab has been completely removed.
2. Replace batteries. Swap batteries with a known working sensor or install new CR123 batteries.
3. Test signal strength. After replacing the batteries, move the sensor closer to the gateway to allow it to reconnect and rule out signal interference issues. Leave the sensor there for 15-20 minutes to see if it connects.

Troubleshooting steps for Radiobridge probe sensors

If your probe sensor is displaying temperatures of -49°F, 2501°F, or 7000°F, this indicates a probe connection issue.

1. Check probe connection: Carefully remove the probe attachment and reinstall it, ensuring the polarity is correct at the yellow connector.
2. Test with different probe: If possible, test the sensor with a different probe to determine if the issue is with the probe or the sensor body.
3. Replace batteries: If readings are still incorrect, try swapping batteries with a known working sensor or install new CR123 batteries.

Ezurio sensors and gateways

Ezurio Model 2 sensors, formerly LAIRD, offer both LoRaWAN and BLE connectivity options. These sensors feature user-accessible battery compartments and reset buttons for troubleshooting.

Ezurio Sentrius RS1xx Sensor

Troubleshooting steps for Ezurio sensors

Use the following troubleshooting steps for both Ezurio ambient and probe sensors.

1. Remove and reinsert batteries: Take the batteries out of the sensor and then place them back in. See if there are any signs of water/hardware damage.
2. Reset the sensor: If the sensor is still offline, press and hold the Bluetooth button for 5 seconds to reset the sensor.
3. Replace batteries: Swap batteries from a known working sensor or install new batteries.
4. Test signal strength. After replacing the batteries, move the sensor closer to the gateway to allow it to reconnect and rule out signal interference issues. Leave the sensor there for 15-20 minutes to see if it connects.

Troubleshooting steps for Ezurio LoRaWAN gateway

Use the following troubleshooting steps for Ezurio LoRaWAN gateways.

• Unplug the gateway for 30 seconds, then plug it back in
• Verify the Ethernet cable is securely connected to its port
• Check the gateway's LED status indicators to confirm proper operation
• Ensure the gateway has a clear line of sight to sensors when possible

MachineQ sensors and gateways

MachineQ provides LoRaWAN-based temperature monitoring with the MQflex sensor series. These sensors are designed for long-range communication and extended battery life.

Troubleshooting steps for MachineQ MQflex Sensors

Warning: MachineQ sensors use specialized 3.6V lithium thionyl chloride batteries (not standard alkaline AA batteries). Do not discard batteries during troubleshooting.

The button press recovery is the quickest recovery method and should be attempted first.

1. Hold the button on the device for 5 seconds until the LED blinks.
2. Wait 60 seconds and observe the LED status.
3. If you see two green blinks, that means the sensor successfully rejoined.
4. If anything else happens, continue troubleshooting.

If the button press does not restore communication, perform a full battery reset.

1. Using a flat-head screwdriver, open the battery door and remove the battery.
2. With battery removed, hold the button for 5 seconds.
3. Reinsert the battery, ensuring proper polarity.
4. Replace the battery door securely.
5. Hold the button again for 5 seconds until the LED blinks.

Note: If you see slow orange blinking (~2 minutes), the battery is going through a depassivation cycle. This is normal for lithium thionyl chloride batteries and the device will automatically reboot and rejoin after completion. Wait for two green blinks.

MachineQ sensor status indicators

Troubleshooting steps for MachineQ gateways

Always start with a power cycle when troubleshooting gateway connectivity issues.

1. Unplug the power cable from the gateway
2. Wait 30 seconds
3. Plug the power cable back in and wait 5-10 minutes for the gateway to complete its boot sequence
4. Check the status LED indicators and verify sensor status in Ops Execution
5. If you are still having connectivity issues after the power cycle perform the appropriate troubleshooting steps based on the connection type

If the MachineQ gateway has an ethernet connection:

1. Make sure their is network activity. Check that the activity indicator on the network switch is illuminated
2. Check the network cables. Verify the network cable is securely plugged into both the gateway and network switch
3. Ensure the network port provides DHCP-assigned IP addresses. To verify DHCP is available on your network, connect another device (such as a laptop) to the same network port and confirm it receives an IP address automatically.
4. Replace the network equipment. If issues persist, try a different ethernet cable or network port (faulty cable terminations are a common cause of connectivity issues)

If the MachineQ gateway has a wireless or Cellular Backhaul connection:

1. Check the status LED. Verify the status LED on the gateway matches the proper status for wireless connectivity
2. Re-install the SIM card and perform another power cycle. If the gateway is not communicating, remove power, remove and re-install the SIM card, then restore power
3. Check the signal strength. Ensure the gateway has adequate cellular signal strength in its location

MachineQ gateway status indicators

General gateway troubleshooting steps for all manufacturers

These steps apply to all gateway models regardless of manufacturer:

1. Power cycle: Unplug the gateway for 30 seconds, then plug it back in.
2. Check physical connections: Ensure the Ethernet cable is securely connected to both the gateway and your network port.
3. Verify network connectivity: Confirm the gateway has a working internet connection and can communicate with Crunchtime servers.
4. Check LED status: Refer to your gateway's manual to interpret the LED status indicators and ensure normal operation.
5. Test with different port: If possible, try connecting the gateway to a different network port to rule out port-specific issues.

Get help from Crunchtime Support for sensor or gateway problems

If you've followed all the troubleshooting steps for your specific device and the problem persists, please contact Crunchtime Support and provide the following information:

• Sensor or gateway model and manufacturer
• Serial number or device ID
• Specific error message or symptoms
• Troubleshooting steps you've already attempted