YipiiYipii Mobility Docs

Week of Mar 31 – Apr 2, 2026

Direct database integration, DTC code enrichment, PIN login, asset type and status improvements, expanded utilisation data, force sync removal.

A focused week on platform reliability and data quality — direct database integration replaces HTTP sync for faster data access, DTC diagnostics get a detailed enrichment layer, PIN login arrives for the admin dashboard, and asset data from the IoT platform is now surfaced correctly.


Direct Database Integration

Faster telemetry data

Odometer and fuel data is now pulled directly from the IoT database rather than through HTTP API calls. This means faster page loads on asset detail screens and more reliable data, as the system no longer depends on the IoT API being available for telemetry reads.

Sync layer removed

The legacy force-sync mechanism has been completely removed. The "Sync from IoT" button on asset detail pages and the underlying controller have been retired — all data now flows through the direct database connection, which is both faster and more reliable.


DTC Code Enrichment

Detailed diagnostic information

Diagnostic Trouble Code (DTC) logs now include enriched data from the DTC code database. When viewing a vehicle's diagnostics, you see the full code description, affected system, and severity — not just the raw code number.

Dedicated detail page

Each DTC log entry now has its own detail page accessible from the diagnostics table. Click through to see the full code breakdown, when it was detected, and which vehicle reported it.


PIN Login

PIN-based authentication

A new PIN login option is available for the admin dashboard. Users who have set up a device PIN in the IoT platform can now use it to log in to the Mobility dashboard without entering their full email and password. The PIN login link appears on the standard login page.


Asset Type and Status

Correct IoT source data

Vehicle types and statuses from the IoT platform are now properly surfaced in the Mobility asset list and detail views. The system reads the correct source fields, so your vehicle categories and custom statuses match what you see in the IoT dashboard.

Utilisation data expansion

The utilisation tab now includes fuel consumption, odometer readings, and traffic data pulled from trip history. This gives a more complete picture of how each vehicle in your fleet is being used.


Questions?

If you have questions about any of these changes or need help taking advantage of new features, contact us at support@yipii.com.

On this page