This release notes document describes the details of version E10 in the following platforms:
This Release Notes document describes the following details for version E10 of the Surfsight® Portal:
The following table lists the items that we fixed for this release:
|
Issue ID |
Problem |
Resolution |
|---|---|---|
|
SUR-5126 |
Some dashcams were unresponsive, and appeared online in the list of devices even when disconnected. A disconnected dashcam appeared online in the list of devices. |
Surfsight® force disconnects unresponsive dashcams in order to properly update their status. All users are now see the correct status of their dashcam. |
This Release Notes document describes the following details for version E10 of the Partner Portal:
E10 also includes the following enhancement:
In order to keep our platform consistent and coherent, we have made the following changes to better align our terminology:
|
Area |
Old text |
New text |
|---|---|---|
|
Devices Health |
Devices Health |
Device Health |
|
Devices Alarms |
Devices Alarms |
Device Alarms |
|
Organizations |
Number of cameras |
Number of devices |
|
Organizations |
Camera Retention Minutes |
Device Retention Minutes |
|
Dashboard, Devices Alarms |
SD Card is not mounted, the dashcam is not recording video |
SD Card is not mounted, the dashcam is not recording video |
|
Dashboard, Devices Alarms |
Hardware failure: unable to start camera imager and record video |
Hardware failure: unable to start dashcam imager and record video |
|
Dashboard, Devices Alarms |
Dashcam reset due to app freeze |
Dashcam reset due to app freeze |
|
Dashboard, Devices Alarms |
Dashcamconstantly resetting |
Dashcam constantly resetting. |
|
Dashboard, Devices Alarms |
Driver dashcam recording failure |
Driver dashcam recording failure |
|
Dashboard, Devices Alarms |
Driver dashcamrecording when it should not be |
Driver Dashcam recording when it should not be |
|
Dashboard, Devices Alarms |
SD card may be fragmented or corrupt. Dashcam is not recording video |
SD card may be fragmented or corrupt. Dashcam is not recording video. |
The following table lists the items that we fixed for this release
|
Issue ID |
Problem |
Resolution |
|---|---|---|
|
SUR-4445 |
When deleting a reseller partner, part of their data remained n in the database. When a second reseller partner tried to add sub-partners and users from the deleted reseller partner, they received a pop-up error message saying: User is already registered. |
There are no longer leftovers of deleted reseller partners in the database. Existing reseller partners can add sub-partners and users from now-deleted reseller partners. |
The following table lists the documents that were updated with the E10 release:
|
Document title |
Description of change |
Knowledge base URL |
|---|---|---|
|
All documentation for:
|
Changing terminology to "Device health" and "Device alarms", and updating all relevant screenshots. |
|
This Release Notes document describes the following details for version E10 of the Surfsight® API:
This new release includes the following new features:
SUR-4941
As part of the newly released driver service, the GET /drivers/org={org} call enables reseller partners and organization administrators to easily retrieve a specific driver using the organization ID.
Users with multi-partner tokens can also use this to find drivers in different organizations.
E10 also includes the following enhancement:
The following table lists the items that we fixed for this release:
|
Issue ID |
Problem |
Resolution |
|---|---|---|
|
SUR-4830 |
Reseller partners and organization administrators did not receive Possible fatigue events, as these were not being transmitted via webhook. |
Users subscribed to event notifications via webhook now receive all event notifications, including Possible fatigue. |
|
SUR-5153 |
The GET /devices/\{IMEI}/device-config call did not include driverPosition in the response ("value: left" or "value: right"). |
The GET /devices/\{IMEI}/device-config call now returns all of the appropriate values, including driverPosition. |
|
SUR-5162 |
The GET /organizations/{orgId}/devices call sometimes returned a disconnected dashcam as "status": "online". |
All users are now see the correct status of their dashcam. |
The following table lists the documents that were updated and or added to the Developer Portal:
|
Document title |
Description of change |
URL |
|---|---|---|
|
API reference => Drivers => Get drivers |
New call: retrieve a list of drivers by organization ID |
https://developer.surfsight.net/openapi/surfsight/operation/getDrivers/ |
|
API reference => Devices => Get data usage |
New parameter (billingDateOfMonth) |
https://developer.surfsight.net/openapi/surfsight/operation/getDeviceDataUsage/ |