The latest firmware update, 3.14, for the AI-12 dashcam, is now Generally Available (GA).  

 What’s included: 

• Yawn Detection

• Auxiliary Camera Connection/Disconnection Alerts

• Enhanced the Telemetry API

•  Standby Window Extension to Improve Data Capture

• Removed Red Lines from the MV+AI icons

• Improved Smoking Event Accuracy

• Customizable MV+AI Event Triggers

• Factory Reset Reminders for AI-12 Cameras

 Availability:  

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

Read more about 3.14 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

The latest firmware update, 3.13, for the AI-12 dashcam is now Generally Available (GA).  

 What’s included: 

• Power loss file protection

• Increase privacy with watermarks

• 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.13 have been updated to the new 3.13 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

• We will be changing the GPS data webhook "ID" field type from numeric to alphanumeric. 

After the change, the GPS coordinate data “ID” parameter type will be expressed in alphanumeric format. If your service does not accept letters in the GPS data webhook "ID" field type, please make the necessary adjustments. 

• The patch update device webhooks will be changed to full patch behavior. 

 You will be able to update webhooks settings without deleting the current settings. When making a new API call from PATCH/organizations/{orgId}/webhook-settings, the call will no longer override the entire object in the configuration.  
 
With this change, the new call will be combined with the existing object. The configuration will allow up to 3 URLs. If the combined configuration contains more than 3 unique URLs, it will return an error. 

•  API GET device event enhancements 

In order to prevent an excessive load on the database, we will be enforcing the start and end query string parameters on the GET /devices/{imei}/events endpoint to      include up to 31 days of activity. This will result in a significant reduction in the number of 500 error codes. 

If more than 31 days of activity are requested, you will receive a return status code 400 “bad request”. 

•  API POST organization events enhancements  

In order to prevent an excessive load on the database, we will be enforcing the start and end query string parameters on the POST /organizations/{orgId}/events endpoint to include up to 31 days of activity. This will result in a significant reduction in the number of 500 error codes. 
 

• POST /organizations/{orgId})/events will be set to Mandatory.   

• The begin and end query string parameters must be set to a maximum of a 31- day time period.  

If more than 31 days of activity are requested, you will receive a return status code 400 “bad request”. 

These changes will be implemented in the release scheduled for December 1, 2024. 

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

Thank you for your understanding and continued support. 

The latest firmware update, 3.12.206, for the AI-12 dash cam is rolling out.

 What’s included:

• New NOM label in the Certification screen

• An issue that caused repeated rebooting of the device was resolved in this update.

• Enhanced Wi-Fi security when connecting auxiliary cameras via hotspot

The limited-release phase of the rollout started on June 3rd and will be gradually carried out throughout the next few weeks. The rollout is beginning 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.206 as GA to all connected devices by the end of June or early July.

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

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

Read more about 3.12.206 firmware update 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. Due to a more stringent validation process, the viewer role, which can be assigned to users in the Partner Portal, will only have access to limited functions across all platforms.  

   • Requests to update, edit, create, or delete information under accessType: viewer, will not be allowed, and will return a 403 error.  

   Please note that API endpoints that require a partner token are not affected by these changes. 

   Furthermore, changes made by a user with viewer access are recorded in the audit log for review. 

2. The events accOff and accOn are available as text only, without snapshot or video. This is configured as dataType parameter none. However, previously the dataType parameter could be configured as a media event: snapshot or video.  

   • Due to a more stringent validation process, these events will not accept configurations as snapshot or video.  

   • For devices that have this event configured as a media event, the configuration will be changed to text only. 

   This change impacts the PUT /devices/event-config, PUT /devices/{imei}/event-config, and POST /organizations/{orgId}/event-settings API calls. 

   This only affects integrations associated with the AI-12 dashcam. 

These changes will be implemented in the release scheduled for August 25. 

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. 

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. 

Resolution notes:

We suspect the issue reported is related to Geotab local plugin’s or/and our cloud’s cache. We’ve invalidated our cache at AWS CloudFront. Our recommendation is to use the browser’s incognito mode with Geotab's plugin, so we will eliminate the local cache too.

Thank you for your patience.

This notice was delivered to <Partners>

 What’s new:

• Driver ID

• Passenger unbelted event

• Wake up the camera via the event trigger button

• Wi-Fi connection Icon

• Product and security enhancements, and much more!

 This firmware version allows you to add new value propositions to your customers with the same device you already offer.

Availability:

The controlled release for the 3.12 firmware version has been successfully completed. Going forward, all devices with a version older than 3.12 will be automatically upgraded as they come online.

Read more about 3.12 firmware version features, enhancements and bug fixes in the knowledge base or Developer Portal changelog. In addition, a product webinar recording about 3.12 firmware version is available in the Partner Webinar section of the Surfsight Product Learning Center.

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