Week of Feb 3 – 9, 2026
Report engine overhaul with PDF/Excel for all types, asset photo gallery, IoT-to-Mobility platform bridge, real-time public tracking via WebSocket, and security hardening.
A major report engine overhaul, asset photo capture, the IoT-to-Mobility bridge for bidirectional sync, real-time WebSocket streaming on public tracking links, and a platform-wide security audit.
Report Engine Overhaul
All report types available in PDF & Excel
Every report type (trail, trip, driver behaviour, mileage, sensor, fuel, alarms, OBD, beacon) now has a PDF and Excel export handler with proper formatting and aggregation summaries.
Temperature source auto-detection
Temperature reports now automatically detect whether a vehicle uses an analog temperature sensor or a Bluetooth beacon sensor, and pull data from the correct source. No manual configuration needed.
Improved column ordering
Report columns are now ordered by relevance with sensible default visibility. Less common columns are hidden by default but available via column settings.
Large report performance
Reports spanning long date ranges now use cursor-based batching to avoid timeouts. Previously, large reports could fail silently — they now process reliably regardless of size.
Asset Photos
Photo capture and gallery
Take photos of assets directly from the mobile app or upload from your device. Photos are stored per asset and displayed in a gallery on the asset detail panel.
QR scanner integration
The QR code scanner now supports a complete workflow: scan a tracker barcode, find or create the device, and immediately capture photos of the asset it's installed on.
Yipii Mobility Bridge
One-click IoT account linking
Link your IoT tracking account to a Yipii Mobility organisation with a single click. Assets, trackers, SIMs, and users sync bidirectionally between both platforms.
Bidirectional asset sync
Changes to assets in either platform propagate to the other. Create an asset in Mobility and it appears in IoT tracking; update a tracker assignment in IoT and it reflects in Mobility.
Telemetry sync pipeline
Live telemetry data (odometer readings, connectivity status) flows from IoT tracking into Mobility for fleet management reporting, maintenance scheduling, and compliance tracking.
Real-Time Public Tracking
WebSocket streaming on shared links
Shared tracking links now receive live location updates via a dedicated AVL socket bridge. Viewers see vehicles move in real time with sub-second latency — no polling, no page refresh.
Scalable broadcast architecture
The public tracking broadcast system was rebuilt for scale. Active viewer tracking uses Redis with TTL-based liveness checks, and the AVL bridge only connects when viewers are present.
Enhanced mobile experience
The public tracking mobile drawer now shows full location details, vehicle status, speed, and last-updated time alongside the map.
Security Hardening
Platform-wide audit
Completed a comprehensive security audit across all services covering authentication, environment variable handling, exposed endpoints, and data privacy.
Key fixes
- Debug mode disabled in all production environments — prevents environment variable exposure through error pages
- Horizon dashboard secured — now requires authentication, was previously publicly accessible
- Swagger docs secured — API documentation endpoints now require authentication
- Environment files removed from git — secrets managed exclusively via deployment platform
- Email verification hardened — closed an arbitrary email change vulnerability
Driver & Trip Analytics (AVL)
Driver behaviour scoring
Real-time scoring for braking, acceleration, cornering, speed patterns, and overall eco-driving. Each trip now carries a detailed breakdown visible in the trip history.
Speed consistency analysis
New metric measuring how smoothly a driver maintains speed, replacing the previous road quality metric with a more meaningful and actionable score.
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?