Handling Device Disconnect Events

Bouncie devices generate Device Disconnect events when power to the device is removed — typically due to an unplug or tamper incident. These events notify developers that the device has lost external power, either intentionally or unexpectedly.

Why Multiple Disconnect Events Occur

• Immediate Disconnect (Real-Time Notification): The latest generation of Bouncie devices can transmit an immediate disconnect notification when power is removed, provided that network conditions allow. This enables real-time awareness of unplug or tamper events.

• Deferred Disconnect (Post-Reconnection Notification): When network connectivity is unavailable at the moment of power loss, the device records the disconnect locally. Once power is restored and the device reconnects to the network, it transmits the stored disconnect event.

Because of this dual-reporting mechanism, developers may observe two Device Disconnect events for a single unplug or tamper incident:

• One generated immediately when power is lost (if conditions allow)
• One generated after power restoration and reconnection

Best Practices

• Treat multiple disconnect events as notifications of the same underlying unplug or tamper event and handle them gracefully within your application.

{
  "imei": "123456789012345",
  "vin": "1HGBIQOJXMN109186",
  "disconnect": {
    "timestamp": "2026-01-01T08:30:00.000Z",
    "timeZone": "America/Chicago",
    "latitude": 32.7767432,
    "longitude": -96.7970123
  }
}