Skip to main content

Device No Longer Returning Meters and Supplies (Stale Devices)

A device has stopped uploading meter reads and supply levels while the install may still be online. Ordered troubleshooting from cheapest check to deepest, plus how to stop it recurring.

Written by Joshua Kern

A device has stopped returning meters and supply levels. It may show as stale in Web Admin, or you may notice a gap in its meter history.

An install being online and a device reporting are two separate things. A perfectly healthy install can have stale devices behind it, so do not assume the agent is at fault.

A device is generally considered stale when it has not returned meter data for longer than its expected reporting interval, typically 24 to 48 hours.


​

Common Causes

  • The device's IP address changed and the install can no longer reach it at the old address. This is the most common cause on DHCP networks.

  • The install is offline.

  • The device is powered off, in a deep energy-save mode, or has been physically moved.

  • The device was replaced and is no longer in use.

  • Device tracking was disabled.

  • SNMP was disabled or reconfigured on the device, which firmware updates sometimes do silently.

  • The device's SNMP version or community string no longer matches what Print Tracker is using.

  • The device's SNMP timeout needs raising to 3000 ms.

  • SNMP port 161 traffic between the install host and the device is blocked.

  • A network change created a new segment or VLAN the install cannot reach.

  • A security software update on the install host began blocking SNMP.

  • The device's IP is no longer inside the install's scan range.

  • The install was replaced, and the new install simply has not scanned for the device yet.

Step 1: Check Whether the Install Is Online

Go to Installs, then View installs, and check the last check-in time for the install that owns this device. If the install itself is offline, fix that first and the devices will usually follow. See DCA Offline or Checking In Late.

If several devices behind one install all went stale at the same moment, suspect the install or the network, not the devices.


​

Step 2: Try the Cheap Fixes First

Work in this order. Each step costs less effort than the one after it, and the first two resolve many cases without further investigation.

If the install is online and Web Admin shows the correct IP for the device, submit an on-demand meter upload. Go to Devices, then View devices, and click Upload meters. If the data comes back, the device was simply missed rather than unreachable.

If the install is online but the IP looks wrong or unknown, run an on-demand scan instead. Go to Devices, then View devices, and click Scan for devices. Scan the device's IP if you know it, otherwise scan the network segments. See Discovering and Managing Devices.


​

Step 3: Run a Network Topology Scan

If the meter upload and scan both fail, the topology scan tells you where the break actually is.

  1. Go to Installs, then View installs, and expand the affected install.

  2. Open Network Topology.

  3. Enter the device's last known or suspected current IP address and run the scan.

The results show whether the install got a PING response, SNMP, a detected embedded web server, and SNMP confirming the device is a printer.

Result

What it means and what to do

PING pass, SNMP pass

The device is reachable and answering, so connectivity is not the problem. Look instead at how this model is being read, or at the billing meter selection. See Billing Meter Format Mismatch and Device Identified as "printmib", then contact support.

PING pass, SNMP fail

The device is on the network but SNMP is disabled or misconfigured. Go to step 5.

PING fail, SNMP fail

The device is unreachable from the install host. The IP has probably changed, or the network path is blocked. Go to step 4.


​

Step 4: Find the Device's Current IP Address

If PING fails, find out where the device actually is:

  • Print a configuration or network page from the device's control panel.

  • Check Network Settings on the device's control panel directly.

  • Check the active DHCP lease table on the router or DHCP server, matching on the device's MAC address.

For the full procedure and how to stop it happening again, see Device IP Address Changed.


​

Step 5: Verify SNMP on the Device

Open the device's embedded web server by entering its IP in a browser from a machine on the same network, then confirm:

  • SNMP is enabled.

  • For v1 or v2c, the community string matches Print Tracker's configuration, commonly public.

  • For v3, the credentials match. See SNMP v3 Configuration and Troubleshooting.

  • The SNMP port is 161.

Firmware updates sometimes reset SNMP settings. If a device went stale shortly after being serviced or updated, check this before anything else.

Also check the device's own SNMP timeout in Print Tracker. Raising it to 3000 ms resolves devices that are simply slow to answer rather than unreachable.


​

Step 6: Confirm the IP Is in the Scan Range

  1. Go to Installs, then View installs, expand the install, and open Settings.

  2. Expand Network discovery and check IP addresses to scan.

  3. Add the device's current IP or subnet if it is missing, then save.

The install applies this on its next scheduled scan. To act now, run an on-demand scan from Devices, then View devices, then Scan for devices.


​

Step 7: IP Reservation

IP changes are the single largest source of stale devices on DHCP networks, and the fix is a one-time conversation with the customer's IT team. Ask them to either:

  • Create a DHCP reservation against the device's MAC address, so it keeps using DHCP but always receives the same address. This is the preferred option because it needs no change on the device.

  • Assign a static IP on the device itself, chosen from outside the DHCP pool to avoid conflicts.

Where customers frequently add devices or re-address networks, scanning whole subnets in CIDR notation rather than individual IPs is more resilient. See Device IP Address Changed for the tradeoffs.


​

Contacting Support

If the device passes both PING and SNMP in the topology scan but still uploads no meters, the problem is in how Print Tracker reads that particular model rather than in connectivity, and support needs to look at it. Provide the device make, model, serial number, and current IP address, the install name, the entity, and the topology scan results.

Did this answer your question?