C8 August 2025

This release notes document describes the details of version C8:

Note

The terms "partner" or "partnership" refers to a collaborative relationship and does not imply a legal partnership or joint venture.

Note

Some features are subject to cellular network availability

SURFSIGHT PORTAL C8 2025

This Release Notes document describes the following details for version C8 of the SURFSIGHT Portal:

Auxilliary Camera Billing

NC-3195

This new feature prevents customers from accessing cloud-based services for auxiliary cameras without a paid subscription. The system will automatically disable cloud services like media uploads, live view, and alarms for auxiliary cameras on devices where the partner has chosen to disable auxiliary camera billing. This ensures Lytx is not providing services for free while still allowing customers to use their purchased cameras locally. Support teams will have clear visibility into the billing status of auxiliary cameras, simplifying troubleshooting and communication with customers.

Surfsight Map Viewer Role

KING-1152

This feature introduces a new, restricted user role in the Surfsight portal for partners. The User - Map viewer role provides access exclusively to the Maps tab, allowing users to view real-time vehicle locations and trip history without any access to event-related data or media. This new user type addresses the need for third-party entities, such as courier allocators, to monitor vehicle location without compromising the privacy or security of event footage and other sensitive information. The change requires no UI modifications; it is a backend adjustment that restricts access to all other portal functions and APIs for this user type.

Data Usage Report

KING-968

This feature introduces a new Data Usage Report, providing partners with a detailed breakdown of bandwidth consumption by device. Previously, partners lacked visibility into how data was being used. The new report, located under the renamed Reports section (formerly Health), provides a comprehensive breakdown of data usage from live videos, video events, uploaded recordings, and streamed recordings. This granular insight will enable partners to better manage their data consumption. A a new UI design will present this information clearly with filterable columns for device name and IMEI.

data_usage_C8.png

AI-14 Device Alarms

KING-130

This implementation provides a system for monitoring device health, including alerts for issues like disconnected cameras, SD card failures, and frequent device resets. By giving fleet managers and technical account managers these tools, we are empowering them to identify and resolve issues, which significantly boosts device reliability and performance.

Known issues

The following table lists the current known issues:

Issue ID

Problem

KB issue

At kb.surfsight.net some tables are poorly formatted and may cause difficulty in reading them. We're currently working on overhauling our knowledge base and planning this fix as part of the changes. In the interim, partner resellers can refer to these PDFs in case they need a different format for better legibility.

SUR-3605

Live video may sometimes flash continuously while streaming.

We are monitoring this issue and evaluating possible solutions.

SUR-5044

Locked dashcams' event settings are not set to off by default. They continue to send video to the cloud using data from the mobile network for any events configured with video attached.

Work-around: Before locking a dashcam, change all of its event settings to off.

SUR-6123

Customers can set the minimum speed for MVAI events creation between 0 and 180 kmh. However, if you set speed lower than 5 kmh, the events will not be created. (Due to hardware limitations, we are investigating possible solutions.)

SUR-9168

Applying Filters Causes Errors in Health UI Alarms Tab: When you apply filters in the Health UI Alarms tab, changing the severity filter results in a 500 Internal Server Error. Additionally, switching to the Alarms Beta tab after applying filters triggers a 400 Bad Request.

Was this article helpful?
0 out of 0 found this helpful