Discussions

The `StartDate` and `EndDate` fields of drives returned by endpoints, such as [Get List of Trips with Details](https://docs.damoov.com/reference/get-list-of-trips), have a date, time, and time zone (e.g., 2024-08-01T20:35:42-05:00). However, the [Daily Statistics](https://docs.damoov.com/reference/indicators-daily-statistics) and [Daily Safety Score](https://docs.damoov.com/reference/indicators-daily-safe-score) endpoints expect their `StartDate` and `EndDate` parameters to be local dates and their responses have `ReportDate` and `CalcDate` fields that return local dates (e.g., 2024-08-01T00:00:00) with a midnight time. How do these "daily" endpoints decide which drives are included in each day given drives include time zones, but days do not. Does the internal logic assume all times are UTC? Or do they drop the drives' time zones when decided to which day they belong? For example, consider a drive that started (or ended) at 2024-08-01T20:35:42-05:00. Is the drive part of 2024-08-01 or 2024-08-02? Note: 2024-08-01T20:35:42-05:00 in the CDT time zone is 2024-08-02T01:35:42Z in UTC.

The `https://api.telematicssdk.com/processeddata/v1/Tracks/update_track` endpoint appears to be unique in that it does require an **authorization** header according to the [API documentation](https://docs.damoov.com/reference/update-transportation-type). Is this correct and intentional, i.e., this endpoint does not require the administrator's access token?

I had a few questions regarding mobile data and drives using Damoov's software running on an iOS device: - How long is data stored locally if there's no Internet during the drive? Is there a maximum amount of drives that will be cached locally? - Does this cache get periodically cleared once drives are uploaded? - Is there an option to only upload data on WiFi? This would mean the drive would stay cached on the phone locally until connected to WiFi. - How much data is used on average for drive tracking? - For instance, are there any metrics that give a rough estimate of megabytes of data per drive per mile?

Please confirm whether the accumulated safety score for a specified time period only considers trips whose transport type is detected as, or corrected as, OriginalDriver. In other words, the accumulated safety score does not consider drives captured on the user's phone when the Damoov driver detection algorithm predicted the phone's user was a passenger or the user corrected the Damoov driver detection algorithm's prediction via a SDK method or an API call.

In the **Troubleshooting** section of the **TELEMATICS INTEGRATION** topic, there is the following note in the \[Wrong Type of Transport Detected](<https://docs.damoov.com/docs/datatool-troubleshooting#iii-wrong-type-of-transport-was-detected>) subsection. > This AI model is self-educated, the larger the volume of marked trips (with transportation type), the more accurate model is. We highly recommend adding the feature of changing transport type to your app. Four options are given to change the transport type. 1. Ask the user to change it in the developer's app. 2. Change it via the API. 3. Change it via the DataHub. 4. Create a support ticket. I would like to change it via the API. Where is the documentation for this endpoint?

"Events": [ { "Id": "", "Type": "Acceleration", "Date": "2023-10-09T08:22:10+01:00", "Lat": 38.74998, "Long": -9.10616, "Value": 3.353325366973877 } ],

Please share free or demo account limitation.

Hello, we have an ELM327 OBD device and connected it to the car. In the demo app, we granted all permissions like Bluetooth. When we want to connect to our car OBD device, after scanning and finding the device name in the list, the connection gets an error. In the Logcat with logs, we can see the phone is connected to the OBD device, but after a second, it is disconnected, and we get the DEVICE_INITIALIZE_FAILED error in the callback.

Hello, we have an ELM327 OBD device and connected it to the car. In the demo app, we granted all permissions like Bluetooth. When we want to connect to our car OBD device, after scanning and finding the device name in the list, the connection gets an error. In the Logcat with logs, we can see the phone is connected to the OBD device, but after a second, it is disconnected, and we get the DEVICE_INITIALIZE_FAILED error in the callback.

Hello. How do you account for, and normalize (assuming you do that), the variance in GPS and other sensors across the smartphone devices, such as iPhone, Samsung, Google Pixel, HTC, Lenovo, Sony, etc? To what degree have you observed the variance across the devices?