Sensors connect to your network via a CAT6 cable.
All detection (vaping, aggression, etc.) happens on the edge (on the device).
When an event is detected, it sends an MQTT alert to Triton Cloud.
Every 10 minutes, the sensor sends a heartbeat to report data like sound level and air quality.
If 3 successive heartbeats are missed, the device will show as offline.
Check the Network Cable
Make sure the cable is securely connected and not damaged. The device needs both data and power (PoE). A bad cable or switch port can prevent it from working properly.
Ping the Device
If you know the device’s IP address, try pinging it using Command Prompt or Terminal.
If it responds to ping but is offline in Triton Cloud, it’s likely a firewall issue.
If it doesn’t respond, it may be powered off, lost its IP, or have a bad cable.
Find the IP via MAC Address
If you don’t know the IP, look up the MAC address (listed as Device ID in Triton Cloud) in your network or firewall interface to find the current IP.
Even if only one sensor is offline, firewall issues are still the most common cause — especially if sensors are using DHCP and lose their IPs after reboot.
*A recent change by Cisco Meraki switches has been blocking traffic because it is being flagged as "tobacco".
Firewall Configuration Guide:
Triton Cloud Firewall Guide / TroubleshootingSetting a static IP helps avoid issues with changing IP addresses or DHCP lease expiration.
ULTRA supports local access via IP, even when offline.
Guide:
How To Set A Static IP on A Triton ULTRA SensorCloud-only – device must be online in Triton Cloud to make changes.
Steps:
Go to Device Management
Click Actions → Edit
Toggle Static IP Enabled
Enter:
Static IP Address
Netmask
Gateway
DNS Server (example: 8.8.8.8, backup: 8.8.4.4)
Click Save
Go to Controls and click “Send Reboot Command” to apply the settings
How To Set A Static IP on Triton Cloud→ Device shows offline in cloud
Cause: Lost DHCP IP or a network change caused it to miss 3 successive heartbeats
Fix: Ping the device, check firewall access, and set a static IP
→ Device responds to ping but still shows offline
Cause: Firewall is blocking MQTT traffic to the cloud
Fix: Reboot the device and pen required ports (see Firewall Guide)
→ Device doesn’t respond to ping
Cause: Device lost IP, has a bad cable, or isn’t getting power
Fix: Check cable, power, and switch port; assign static IP if possible
→ Device frequently goes offline and back online
Cause: Dynamic IP via DHCP causes periodic network interruptions
Fix: Assign a static IP to the device to stabilize connection