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

New Features and Enhancements

GPS Cloud Control and Privacy Enhancements

We’re improving how our platform uses GPS so that devices remain location‑aware while continuing to respect privacy and configuration choices.​

  • Devices stay location-aware, privacy stays intact. Devices will always know their location to support features like Dynamic Adjust, but when GPS tracking is disabled, no GPS data will be stored on media/events or returned through APIs.​

  • Stronger GPS privacy controls. When GPS tracking is off, GPS-dependent events won't be created, location and speed data won't be stored or shared externally, and API endpoints will respect your privacy configuration.

Fixes

Organization Device Settings Now Apply to All Devices

This release fixes an issue where the Organization Device Settings API POST /organization/device-settings only updated the first 1,500 devices in an organization. For organizations with more than 1,500 devices, some devices were not receiving the configured default settings.​

 With this update:​

  • Organization default device settings are now applied to all devices in the organization and performance has been validated at scale.​

  • This change supports consistent, organization‑wide device configuration for large fleets using the API.

Organization Default Event Settings API Updating Only 1500 Devices

This release fixes an issue affecting organizations with large device fleets, where default device event settings were only being applied to the first 1,500 devices.​

Now, when you use the following APIs to set organization default event settings, those settings are applied to all devices in the organization, regardless of how many devices you have:​

  • POST Organization Event Settings​

  • PATCH Organization Event Settings​

This behavior is now consistent for:​

  • Organizations with 1,500 or fewer devices​

  • Organizations with more than 1,500 devices (including very large fleets, e.g., 50,000 devices)

Using these APIs to manage default event settings at the organization level now applies those settings to every device in the organization.​

Autocalibration and Recalibration Work After Manual Calibration

We’ve fixed an issue where a device could no longer be auto calibrated after it had been manually calibrated.​

Previously, if you:​

  • Auto calibrated the device​

  • (Optionally) auto recalibrated the device​

  • Manually calibrated the device​

  • Tried to auto recalibrate again​

the device could be left in a state where:​

  • adas_calibrated = false​

  • adas_ready_to_calibrate = true​

and auto recalibration would not complete successfully.​

 With this fix, auto calibration and auto recalibration behave as expected even after manual calibration. Devices can now be calibrated successfully using any of the supported calibration flows and device diagnostics will now correctly reflect the calibrated state after these flows.

Alarm Simulator Returns Alarms IDS for Older AI-14 Alarms

This release fixes an issue where the alarm simulator API could return an HTTP 304 Not Modified status instead of the expected alarm details for some older alarms on AI-14 devices.​

Previously, when calling POST addSimulatedAlarm the API sometimes responded with 304 Not Modified for older alarms instead of the alarm ID as expected.​

With this fix, the alarm simulator now responds correctly with the requested alarm ID instead of 304 Not Modifiedso you can reliably trigger and validate simulated alarms for AI-14 devices.​​

Recalibration API Returns the imei Field

We’ve fixed an inconsistency in the Re‑calibration API response where the field name did not match the API contract.​

Previously, the rejected list in the response could include a mix of:​

  • an undocumented field: deviceIMEI​

  • the documented field: imei​

With this fix, the re‑calibration API now consistently returns the documented imei field in its response payload across both accepted and rejected entries.​

Read about new features:

In the Knowledge Base

This notice was delivered to Lytx partners.

For more information, speak with us here.