Device not reporting data

Your DataLogger is installed but the portal shows no new telematics — the vehicle appears offline or shows “UNOBSERVED” in the Diagnostics feed.

Why this happens

The device lost its connection to the diagnostic port (cable worked loose, vehicle vibration).
The vehicle’s ignition has been off long enough that the device entered a low-power sleep mode — this is normal and data resumes on next engine start.
The device is powered but cannot reach the BitBrew cellular network (tunnel, underground garage, or weak signal area).
A software or provisioning issue is preventing the device from sending data upstream to Servinix.

Check the portal Diagnostics page. Go to Fleet > Diagnostics and find the asset. If the status column reads “UNOBSERVED” and DTC Code shows “None Detected,” the device has not sent a heartbeat recently — this does not always mean hardware failure.
Start the vehicle and wait 5 minutes. The DataLogger wakes on ignition power. Drive a short distance to confirm cellular connectivity is not a location issue.
Inspect the physical connection. With the ignition off, firmly re-seat the device in its diagnostic port. If a cable is used, check both ends — the cable-to-device connection and the cable-to-port connection. Tug gently to confirm neither end is loose.
Check LED behavior. On power-up, LEDs should illuminate briefly. Note: “LEDs may extinguish after a period of time. This is NORMAL” (DataLogger Installation Guide v3.3). Dark LEDs alone do not confirm a fault — confirm the vehicle was running when you checked.
Refresh the Diagnostics page after 10–15 minutes of driving. The Battery Voltage Trend should show a reading above baseline (14.2 V peak is typical while the alternator is running).

If the device still shows no data after an ignition cycle and physical re-seat:

Note the asset ID (VIN or device serial number), the last-seen timestamp from the Diagnostics feed, and any DTC codes shown.
Contact Servinix support with this information. Support can query the BitBrew telemetry pipeline to determine whether packets are being received but not displayed, or whether the device has gone silent entirely.
If the device is confirmed non-functional, support will initiate a replacement through the RMA process.