What’s included this time around? What’s new? Check it out!

New Features and Enhancements

Enhanced Event Media Upload Retry Mechanism for AI-12 Devices

Surfsight Cloud has upgraded the media upload retry mechanism for AI-12 devices to incorporate real-time device status feedback, helping to prevent unnecessary retry attempts and support upload reliability.

Users can now:

• Experience improved reliability and higher success rates for both standard and virtual event video uploads.

• Reduce the likelihood of interrupted or dropped in-progress video uploads caused by premature time-based retry triggers.

• Benefit from smarter upload retry handling that triggers only upon explicit device failure reports or extended timeouts when media is not received.

Scope:

• Applies to AI-12 devices for standard and virtual event media uploads.

• Cloud platform and backend upload-handling logic only. No changes to device hardware, firmware, or customer configuration required.

Consolidated Dashboard and Management for Super Partner Role

Surfsight Cloud now provides Super Partner administrators with a centralized portal experience to monitor and manage their entire group of child Partners, Sub-partners, and customer organizations from a single entry point.

Super Partner administrators can now:

• Access a single, consolidated dashboard displaying all child Partners, Sub-partners, organizations, and devices across the group in a unified view.

• Navigate directly into any individual country Partner portal within the same session without requiring separate logins or credentials.

• Create and manage Sub-partners and organizations directly within their account hierarchy.

• Manage independent billing profiles across HQ and country Partner accounts to support direct invoicing requirements.

Scope:

• Applies to Super Partner accounts in the Surfsight Cloud Partner Portal.

• Web application only. No changes to device hardware, firmware, or mobile apps.

Fixes

Live View session records missing in audit logs for organization devices

This release fixes an issue where live streaming and Live View session records were missing from audit log query results (GET /v1.1/audit-logs).

When querying audit logs by organization ID or partner ID, session records initiated by partner-level users on organization devices were excluded because filters only matched the acting user rather than the affected device or entity.

With this update:

• Audit log filters evaluate both the acting party and the affected entity.

• Live streaming and Live View session records are included when retrieving audit logs for an organization.

Dashcam offline status changes not sent via device status webhooks

This release fixes an issue where device status change webhooks (systemMessages - deviceStatus) were not always delivered when devices went offline.

When an AI-12 device disconnected and went offline, the corresponding "Device status changed to offline" webhook notification was occasionally not generated or sent, which could cause integrated partner platforms relying on webhooks to continue displaying devices as online.

With this update:

• Status change webhook notifications are triggered and delivered when a device transitions to offline.

• Partner platforms and integrations can keep device status synchronized.

Event media availability webhook not sent when media becomes ready

This release fixes an issue where follow-up event webhooks with mediaAvailable=true were not always delivered when event media became available.

After the initial event webhook was sent, subsequent webhook notifications indicating that associated media was ready were not consistently triggered, which could prevent integrated partner platforms from knowing when media was ready for retrieval.

With this update:

• Follow-up webhook notifications with mediaAvailable=true are delivered once event media becomes available.

• Partner platforms and automated workflows can detect media availability and initiate retrieval.

Missing event video despite recordings being available for event timeframe

This release fixes an issue where event videos were occasionally missing even though video recordings were present for the exact time the event occurred.

When an event occurred, the event video was occasionally unavailable for viewing or retrieval despite the continuous recording being present and available on the device for that same timestamp.

With this update:

• Event videos are generated and made available when recordings exist for the event timestamp.

• Users can access and review event videos alongside corresponding recorded footage.

Breaking Changes

The following breaking changes were announced on September 27, 2026, and will be implemented on or after January 1, 2027.

Sub-Reseller Organization Visibility Controls

What's changing

Lytx is introducing a new organization visibility flag for every organization in the Surfsight platform:

• This flag controls what a contributing partner—one whose device is present in an organization they do not own—can see within that organization.

• On the effective date (after a 90-day notice period), existing organizations containing third-party or partner devices will automatically be updated to Managed fleet, while all new organizations will default to Owner only.

As part of this change:

• The flag introduces three visibility levels:

  • Owner only: The organization is hidden from contributing partners and is visible only to its owner.

  • Managed fleet: Contributing partners can only view and manage devices for which they have authorized visibility within the organization and have no access to other partners' devices, organization settings, or user accounts.

  • Managed fleet with full access: Contributing partners maintain full access to all devices, organization settings, and user accounts.

• Organizations containing only their own devices experience no change and remain set to Owner only.

• Impact on APIs: This change affects all V2 API endpoints (not only GET /organizations). All V2 API endpoints will return filtered results based on the organization's visibility flag value.

• Partners whose integrations or workflows rely on full organization visibility should review their setup and contact their Technical Account Manager (TAM) during the 90-day notice window.

Why it Matters

Previously, contributing partners could view entire customer organizations where their devices were deployed. Implementing this visibility flag across all V2 APIs improves privacy, data isolation, and access governance by ensuring contributing partners only see devices for which they have authorized visibility.

Health API enhancement: Inclusion of Alarm-V2 response fields

What's changing

We've updated the Health API (POST /healthReport) to return comprehensive alarm details alongside device health metrics:

• The response payload for alarm data has been expanded to align directly with the Alarms-V2 API response.

• Partners no longer need to make secondary API requests to fetch detailed alarm information for a device.

As part of this change:

• The POST /healthReport endpoint now includes the additional alarm fields previously only available via the Alarms-V2 API.

• Internal-only fields (such as alarmStatusHistory, isSimulated, and metaData) remain unexposed.

• The Alarms-V2 API endpoints themselves remain unchanged.

• Partners consuming the Health API can ingest the enriched alarm payload directly from a single response.

Why it Matters

Previously, the Health API provided only minimal alarm details (code, details), requiring partners to make separate calls to Alarms-V2 to retrieve full alarm context. Consolidating these fields into the Health API reduces redundant API calls, ensures data consistency across endpoints, and streamlines integration for partners.

Read about new features:

In the Knowledge Base

This notice was delivered to Lytx partners. The terms "partner" or "partnership" refers to a collaborative relationship and does not imply a legal partnership or joint venture.

For more information, speak with us here.