3.9.209 August 2021

SUR-3244

Power disconnect events appeared for some dashcams instead of power off events when the dashcam was shut down.

Only power off events occur when the dashcam is shut down.

SUR-3303

Events returned in the GET /events API call were showing the incorrect camera ID for video of the event.

Events returned in the GET /events API call now show the correct camera ID for video of the event.

SUR-3310

In some dashcams, the driver unbelted event was triggered multiple times during one trip and the driver was receiving alerts too frequently.

There is now a maximum of one driver unbelted event per trip and the driver only receives alerts for that event.

SUR-3311

When the same PIN was set for both the driver and the admin with the PUT /devices/device-config API call, the driver lost access to the dashcam screen.

When the same PIN is set for both the driver and the admin with the PUT /devices/device-config API call, the request is not accepted and both the driver and admin keep their previous PINs.

SUR-3312

When a virtual event with a snapshot media type was created using the POST /devices/{imei}/virtual-event API call, the time of the snapshot was incorrect.

When a virtual event with a snapshot media type is created using the POST /devices/{imei}/virtual-event API call, the time of the snapshot is correct.

SUR-3314

Some dashcams did not reset their data usage at the beginning of every month and instead continued to accumulate data usage from month to month.

All dashcams reset their data usage at the beginning of every month.

SUR-3316

After a factory reset of the dashcam, the billing day of the month was incorrect.

After a factory reset of the dashcam, the billing day of the month is now correct - the first day of the month.

SUR-3318

Retention times configured with the PUT /devices/{imei}/retention-config were not consistently followed.

Retention times configured with the PUT /devices/{imei}/retention-config are now consistently followed.

SUR-3332

When the tamper-proof case was removed from the dashcam, the dashcam would restart. This took up to a minute and prevented a tamper event from being created during that time.

The dashcam stays on and creates a tamper event when the tamper-proof case is removed.

SUR-3334

If an event with a snapshot media type was created while there was no network access, the event only showed a snapshot from the in-cab lens once network access returned.

If an event with a snapshot media type is created while there is no network access, the event shows snapshots from all relevant cameras once network access returns.

SUR-3341

Sometimes, for auxiliary cameras that were connected to a dashcam by way of WiFi, if you reformatted the auxiliary camera SD card after the camera had already been activated and started recording, the camera recordings no longer appeared in the Surfsight Portal.

For auxiliary cameras connected to a dashcam by way of WiFi, if you reformat the auxiliary camera SD card after the camera has already been activated and started recording, the camera recordings continue to appear in the Surfsight Portal.

SUR-3368

Some auxiliary cameras had the incorrect time during recordings.

Auxiliary cameras now have the correct time during recordings.

SUR-3385

Some dashcams had inconsistent recordings of trips.

Dashcams now have consistent recordings of trips.

SUR-3397

If a virtual event with video was created using the POST /devices/{imei}/virtual-event API call but there was no recording for the time of the event, a recording for a time close to the event was used instead.

If a virtual event with video is created using the POST /devices/{imei}/virtual-event API call but there is no recording for the time of the event, the event is created without a video.

SUR-3456

For some dashcams, the accelerometer sensitivity level was too high, causing unnecessary events to be triggered.

The accelerometer sensitivity is now set to the correct level.