Week of Feb 17 – 23, 2026

Yipster AI fleet assistant, OBD-II diagnostics with DTC alerts, connectivity monitoring, odometer polling, alert templates, and Sentry error tracking.

The Yipster AI fleet assistant, live OBD-II diagnostics with automatic DTC alerts, a new connectivity monitoring system, and Sentry error tracking across all services.

Yipster AI Fleet Assistant

Conversational fleet management

Ask questions about your fleet in plain language. Yipster understands your assets, trips, alerts, fuel entries, and odometer history — and answers with real-time data from your account.

Example questions:

"Which vehicles are currently moving?"
"Show me today's trips for van ABC-123"
"What alerts fired this week?"
"Is asset XYZ frozen or stuck?"

Live fleet awareness

Yipster reads live vehicle positions, engine status, speed, and sensor data from the tracking map. Ask about your fleet and get answers based on what's happening right now — not just historical data.

Docs search

Yipster can search the documentation portal to answer how-to questions about the platform, API usage, and feature configuration.

Diagnostic tools

Yipster can detect frozen or stuck assets (trackers reporting the same position repeatedly) and trigger device resets directly from the chat — no need to navigate to the device page.

Available on both platforms

The AI assistant is available in the IoT Dashboard and the Mobility admin panel, with platform-specific tools for each.

OBD-II Diagnostics

Live fault code detection (Dashboard)

Vehicles reporting OBD-II diagnostic trouble codes (DTCs) now show visual indicators directly in the tracking interface:

Asset card — Orange wrench icon replaces the status icon when fault codes are present
Status bar — DTC count badge alongside speed, fuel, and temperature
Detail panel — Full diagnostics section listing each fault code with category badge and human-readable description

Built-in code database

Over 700 standard OBD-II codes (P0xxx, P2xxx, B0xxx, C0xxx, U0xxx) are translated to plain English descriptions automatically. Covers powertrain, body, chassis, and network communication faults.

The tracking engine now extracts and processes OBD-II diagnostic trouble codes from vehicle telemetry. When a connected vehicle reports fault codes via its OBD port, the data is parsed, stored, and made available in real-time location updates.

DTC alert type

A new DTC_DETECTED alert type allows the AVL server to trigger alerts when diagnostic trouble codes are detected. The alert payload includes the fault code list and count, enabling automated notifications for vehicle health issues.

Connectivity Monitoring (AVL)

Online/offline tracking

New connectivity gate tracks when trackers come online and go offline. This provides accurate uptime data per device and enables the TRACKER_HEALTH alert type to fire based on actual connectivity state rather than GPS signal alone.

Scheduled odometer polling

Odometer readings are now polled on a 2-hour interval for all active trackers. This ensures accurate mileage data even for vehicles that are stationary or in areas with poor GPS reception.

Critical Alert System (AVL)

Account-wide critical alerts

A new critical alert routing system for security-sensitive events (power cut, tampering, device removal). When the AVL detects these events, notifications are routed to all verified account users — no pre-configured alert rule required.

New Hardware Support

Teltonika device registry

Added support for latest Teltonika tracker models including updated hardware identifiers and protocol handlers. The FOTA system recognises these new devices for firmware management.

FOTA device ID support

Trackers can now be looked up and pre-registered using their FOTA device ID, streamlining the onboarding process for new devices.

Sentry Error Tracking

Real-time error monitoring

Sentry is now integrated across all services (frontend, IoT backend, report service). Errors are captured with full context — stack traces, user info, request data — and grouped automatically for faster debugging.

Performance monitoring

Key transaction traces are collected to identify slow endpoints and rendering bottlenecks, with alerts for performance regressions.

AVL Performance

Endpoint caching

The tracker data endpoint used by the dashboard now employs batch loading and response caching. Accounts with large fleets (500+ trackers) see significantly faster load times.

Odometer race condition fix

Resolved a race condition where concurrent odometer updates could produce inconsistent readings. Updates are now serialised per tracker to ensure accuracy.

Reduced database overhead

Throttled high-frequency writes (last login timestamps, activity logging for bulk operations) to reduce database load during peak hours without losing audit data.

Questions?

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

Was this page helpful?