How fake-device works ❓

A virtual PT30 device for manual QA — LOCAL / DEV & STAGING only (a prod-guard refuses production hosts).

What it does

One virtual device feeds two Ezlogz channels from one shared state, so GPS, ignition, odometer and duty-status stay consistent:

• Fleet map — Geometris telemetry (GPS / odometer) → cloud last_data.
• Logbook / HOS — mobile duty / engine / scanner statuses → dashboard, then HOS recalculation.

Steps

1. Manager sign in (the gate) — unlocks the panel and authorizes recalc.
2. Driver sign in (top-right) — the driver whose logbook you fill (carrier 8 only). Each browser is its own session.
3. Pick a device in the sidebar to connect it (Scanner ON + telemetry).
4. Run a scenario (pre-violation / violation) or use the manual controls: duty status, ignition, speed, and Pick / Warp / Drive on the map.
5. Check the result in the driver logbook (link below) and on the fleet map.