Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

How to troubleshoot offline sensors in Triton Cloud

If one or more of your Triton sensors are showing as "Offline" in Triton Cloud, this guide will help you identify the cause and get them back online. The most common culprit is a firewall or network issue — not a faulty sensor. For a visual step-by-step walkthrough with screenshots, follow the Scribe guide linked below.

→ Step-by-step Scribe guide with screenshots

How do the sensors connect to Triton Cloud?

Triton sensors connect to your network via a CAT6 Ethernet cable and receive both data and power through PoE (Power over Ethernet). All detection — vaping, aggression, gunshots, etc. — happens locally on the device itself. When an event is detected, the sensor sends an MQTT alert to Triton Cloud. Every 10 minutes, the sensor also sends a heartbeat to report environmental data like sound level and air quality. If 3 successive heartbeats are missed, the device will appear as offline in the cloud.

Important: If a device is showing as offline in Triton Cloud, you cannot make changes to it through the cloud — including rebooting it or changing its IP address. Any commands sent through Triton Cloud require the device to be online and connected. If the sensor is offline, you'll need to troubleshoot it locally (via the network, the physical cable, or the sensor's local web interface for Triton ULTRA).

What should I check first?

1. Check the network cable. Make sure the Ethernet cable is securely connected at both ends and not damaged. Since the sensor relies on PoE, a bad cable or switch port can cut both power and connectivity.

2. Ping the device. If you know the sensor's IP address, try pinging it from Command Prompt or Terminal:

  • If it responds to ping but shows offline in Triton Cloud — the sensor is healthy and connected to your network, but something (usually a firewall) is blocking its communication with Triton's cloud servers.
  • If it doesn't respond to ping — the sensor may be powered off, have a bad cable, or may have lost its IP address.

3. Find the IP via MAC address. If you don't know the sensor's IP, look up its MAC address in your network or firewall interface. The MAC address is listed as the Device ID in Triton Cloud.

What is the most common cause of offline sensors?

Firewall blocking. Even if only one sensor is offline, firewall issues are the most common cause — especially if sensors are using DHCP and have lost or changed their IP addresses after a reboot or lease expiration.

Note: A recent change by Cisco Meraki switches has been blocking Triton sensor traffic because it is being flagged as "tobacco." If you're using Meraki, check your content filtering settings.

For full details on which ports and domains need to be open, see our Firewall Configuration Guide: Triton Cloud Firewall Guide / Troubleshooting

How do I prevent sensors from going offline?

Set a static IP. This is the most effective way to prevent connectivity issues caused by DHCP lease expiration or IP address changes. We recommend doing this proactively while the device is still online.

For Triton ULTRA: ULTRA sensors support local access via their IP address, even when they're offline in the cloud. You can configure a static IP directly through the sensor's local web interface. See the guide: How To Set A Static IP on A Triton ULTRA Sensor

For 3D Sense / Triton Pro: These devices are cloud-only, so the sensor must be online in Triton Cloud to make changes. If the device is currently offline, you'll need to resolve the network or firewall issue first before you can configure a static IP through the cloud. Once the device is back online:

  1. Go to Device Management in Triton Cloud.
  2. Click Actions → Edit on the device.
  3. Toggle Static IP Enabled.
  4. Enter the Static IP Address, Netmask, Gateway, and DNS Server (e.g., 8.8.8.8, backup 8.8.4.4).
  5. Click Save.
  6. Go to Controls and click Send Reboot Command to apply the settings.

See the guide: How To Set A Static IP on Triton Cloud

Quick Reference

Device shows offline in the cloud: The sensor likely lost its DHCP IP or a network change caused it to miss 3 successive heartbeats. Ping the device, check firewall access, and set a static IP.

Device responds to ping but still shows offline: The firewall is blocking MQTT traffic to the cloud. Reboot the device and open the required ports (see Firewall Guide).

Device doesn't respond to ping: The sensor may have lost its IP, have a bad cable, or isn't getting power. Check the cable, power, and switch port. Assign a static IP if possible.

Device frequently goes offline and back online: Dynamic IP via DHCP is causing periodic network interruptions. Assign a static IP to stabilize the connection.

Need help? Contact us at support@tritonsensors.com or call 800-305-1617.