The latest firmware update, 3.12.108, for the AI-12 dash cam is now Generally Available (GA).  

 What’s included: 

• Auxiliary camera connectivity and recording enhancements 

• Improved recording stability of the dash cam during high-impact events 

• General fixes and improvements 

 Availability:  

This update is rolling out automatically to all connected devices. Most devices which were previously updated to the limited release version 3.12.105 have been updated to the new 3.12.108 version. 

Read more about 3.12.108 firmware version enhancements and bug fixes in the knowledge base  or  the Developer Portal changelog.  

 For more information, please contact your Partner Success Manager or Technical Account Manager.

Sincerely, 

Lytx Surfsight Team 

This notice was delivered to Lytx partners.

For more information, speak with us here

1.       A JWT token is now required for both setting purge days and updating purge days in the PATCH /organizations/orgID API call. This is available only to users with partner-level permissions.

2.       The same PIN number cannot be assigned to both a driver and an admin PIN in an organization. Until now trying to configure the same PIN number was rejected and a 200 code was returned. Now, if the same PIN number is assigned to both a driver and an admin PIN, the operation fails, and an error code is returned. This applies whether the request to assign the same number is made in one or multiple API calls using the following API endpoints:

• PUT /devices/{imei}/device-config

• PUT /devices/device-config

• POST /organizations/{orgId}/device-settings

These changes will be implemented in the release scheduled for May 26. 

We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

 1.       The DELETE/organization/{orgId} API call will change to DELETE/organizations/{orgId} to be consistent with other Organizations endpoints.

 2.       The event type activated is invalid and will no longer be accepted in the following API calls: PUT/devices/{imei}/event-config, PUT/devices/event-config, POST/organizations/{orgId}/event-settings, and POST/organizations/{orgId}/events. Using the event type activated will return an error message. The correct event type to use is deviceActivation.

These changes will be implemented in the release scheduled for March 3, 2024. 

We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

1. Certain events can only accept none for the data type using the dataType parameter. Previously, attempting to set up these events with a snapshot or video type didn't trigger an error. However, moving forward, an incorrect dataType will trigger an error with a 400 code and the following message: "dataType should be equal to one of the allowed values." These changes impact the following events within the PUT /devices/event-config, PUT /devices/{imei}/event-config, and POST /organizations/{orgId}/event-settings API calls:

   • accOff

   • accOn

   • geoFence

   • speedLimit

   • standbyEnter

   • standbyExit

2. Previously, when a GET request was made to /devices/{imei}/cameras while the dash cam was offline, it resulted in an error with a 500 code along with an internal server error message. However, moving forward, if the dash cam is offline, a 417 error code will be returned, accompanied by a message indicating that the device is currently offline.

These updates to the Surfsight API aim to enhance error clarity and specificity, enabling you to swiftly identify and rectify issues, thus streamlining your integration process.

These changes will be implemented in the release scheduled for November 12. 

We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

 
WHAT’S NEXT? 

JUL-SEP: The limited-release phase of the rollout started on July 11^th  and will be gradually carried out throughout the next few weeks. The rollout begins with devices connected to the US cloud. 

As we progress with the rollout, we will upgrade larger batches of devices. Devices will be randomly picked, including devices connected to the EU cloud. We expect to push 3.12 as GA to all devices by the end of September. 

 All devices are configured to turn off any new features so as to not alter the experience of the end-user.  

JUL 26^th : A product release webinar and training will be held dedicated to the firmware's features and enhancements (register here).  

The timing and pace of the rollout are approximate and subject to change according to the deployment performance. 

We value transparency and will notify you as the rollout progresses. 

More information about the 3.12 firmware version can be found in the knowledge base or Developer Portal changelog. 

Sincerely, 

Lytx Surfsight Team 

This notice was delivered to Lytx partners.

For more information, speak with us here.

For more information, please contact your Partner Success Manager.

Sincerely,

Surfsight Product Group

The following parameters were previously optional and will now be required in the PUT /devices/{imei}/event-config, POST /organizations/{orgId}/event-settings, and PUT devices/event-config API calls: 

• speedLimit, when configuring speedLimit events 

• drivingDuration, when configuring possibleFatigue events 

• headwayAlertDayThreshold, headwayAlertNightThreshold, and headwayAlertTime, when configuring tailgating events 

• LaneWeavingTimes and laneWeavingDurationSeconds, when configuring laneWeaving events 

These changes will be implemented in the release scheduled for May 28^th. 

We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

1. The password parameter in the recordingEncryption object returned in our GET /organizations/{orgId}/default-settings API call will be removed. Integration partners who use the password value in their code will be affected. 

2. The period for which mobile provider data is returned in the GET /devices/{imei}/data-usage API call will be the current month instead of the last thirty days. The twilioFleet response object will be renamed mobileProvider. Additionally, some data that is currently included in the response object will be removed. The following parameters will still be included in the response: 

   • uniqueName

   • dataLimit

   • dataUsage.period

   • dataUsage.dataUpload

   • dataUsage.dataDownload

   • dataUsage.dataTotal

3. When a user attempts to create a virtual event with the POST /devices/{imei}/virtual-event API call for a dashcam to which they don’t have access, a 404 not found error will be returned regardless of the dashcam status. 

These changes will be implemented in the release scheduled for April 2^nd. 

We understand that these changes may cause some disruption to your workflow, and we apologize for any inconvenience. If you have any questions or concerns, please reach out to your Technical Account Manager. 

Thank you for your understanding and continued support. 

• an event media reusable component, which enables playing video or showing snapshots of an event from a specific device

Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.

This notice was delivered to Lytx partners.

For more information, speak with us here.

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

• We increased the maximum value of the headwayAlertTime in the tailgating feature.

Read all about this release’s new features, enhancements, and the bugs we fixed in the Developer portal changelog.

This notice was delivered to Lytx partners.

For more information, speak with us here.