Discussions
When capturing a Track, how is the StartDate and EndDate determined?
When capturing a Track, how is the StartDate and EndDate determined?
Posted by Matthew Davis 11 months ago
How to simulate rides for Android
Hi, I see we can emulate for IOS (https://docs.damoov.com/docs/ios-simulator)
Is there any chance to do this programmatically for android?
Posted by Luis Santiago 11 months ago
Use Flutter Wrapper
How do I use Flutter telematicsSDK available on Github to make my own Flutter application? Does it contain SDK?
Need some guidance over here. Thanks
Posted by Louis 12 months ago
Trip Requirements
https://docs.damoov.com/docs/tools-for-testing
Does a trip have to meet all three of these requirements? ie. > 60s, > 2km AND > 30km/h?
Additionally, are these values configurable? In some of our use cases it is likely that drivers will be travelling at speeds well below 30km/h for the duration of the trip.
Posted by Sam Helman 12 months ago
Flutter SDK - addFutureTrackTag method on iOS does not work
Hi,
I am trying to call the addFutureTrackTag method using the Flutter SDK, like this:
```
await TrackingApi().addFutureTrackTag(tag: tag, source: source);
```
This works perfectly in Android, but throws an error in iOS which crashes the app:
```
telematics_sdk/SwiftTelematicsSDKPlugin.swift:210: Fatal error: Unexpectedly found nil while unwrapping an Optional value
```
I noticed in the SwiftTelematicsSDKPlugin.swif (https://github.com/Mobile-Telematics/telematicsSDK-demoapp-flutter-/blob/main/ios/Classes/SwiftTelematicsSDKPlugin.swift) handle function, "addFutureTrackTag" is mapped to the addTrackTags method. Is this intentional? To me, it seems incorrect.
lines 63 and 63:
```
....
case "addFutureTrackTag":
addTrackTags(call, result)
....
```
I think this needs to be:
```
....
case "addFutureTrackTag":
addFutureTrackTag(call, result)
....
```
Posted by Sam Helman about 1 year ago
How to use Telematics SDK with Bluetooth OBD in React Native app?
I am going to get the mileage from the Bluetooth OBD(ELM 327) by using Telematics SDK in my react-native app.
So I installed the React Native demo app and it works well.
https://github.com/Mobile-Telematics/telematicsSDK-demoapp-react
But I want to use the Bluetooth OBD and I think there is no function to connect the Bluetooth OBD with SDK in this SDK(for React Native).
Q1. How to connect the Bluetooth OBD with this SDK in React Native app?
Q2. How to get the mileage from the SDK with Bluetooth OBD in React Native app?
Posted by Leonid Lewis about 1 year ago
API to deactive user (but not delete)
Hi, I am unable to find the API call in the documentation to deactivate a user (but not delete them). This is something you can do in the Hub.
Posted by Daniel Lajeunesse about 1 year ago
Trip not in progress
Hi!
after clone from https://github.com/Mobile-Telematics/TelematicsApp-Android, I encountered issue after following the integration video. It seems everything is set up correctly but it keep showing in the notifications Trip not in progress even Made a trip of about 5 km. another error is shown on logCat:
2022-02-14 19:56:56.494 3083-3083/com.devprime.okataxiapp D/DashboardFragment: observeRank: onSuccess r: 1
2022-02-14 19:56:56.577 3083-3083/com.devprime.okataxiapp D/DashboardFragment: setRank: rank Rank #1
2022-02-14 19:56:56.603 3083-3083/com.devprime.okataxiapp E/StorageException: StorageException has occurred.
Object does not exist at location.
Code: -13010 HttpResult: 404
2022-02-14 19:56:56.604 3083-3083/com.devprime.okataxiapp D/FIREBASE await: isSuccessful: false task: com.google.firebase.storage.StorageException: Object does not exist at location.
2022-02-14 19:56:56.604 3083-3083/com.devprime.okataxiapp D/getErrorCode: getErrorCode: FirebaseException Object does not exist at location.
please help
Posted by Nacir Ibraimo about 1 year ago
Trips started in quick succession get merged in the dashboard.
Hi,
I am encountering an issue with the flutter sdk. Trips that are taken in quick succession are sometimes merged in to a single trip.
We are using the manual tracking method.
In our app we click a button to start the trip, which triggers the following event:
```
on<StartShuttleEvent>((event, emit) async {
...
// ENABLE SDK AND BEGIN TELEMATICS TRACKING
TrackingApi trackingApi = TrackingApi();
trackingApi.setDeviceID(deviceId: deviceToken);
trackingApi.setEnableSdk(enable: true);
trackingApi.startTracking();
...
}
```
We click a button to end the trip, triggering the end trip event:
```
on<EndShuttleEvent>((event, emit) async {
// END TELEMATICS TRACKING
TrackingApi().stopTracking();
// DISABLE SDK
TrackingApi().setEnableSdk(
enable: false,
uploadBeforeDisabling: true,
);
...
}
```
If, after I end the first trip, I start the second trip within a short period, the second trip will be merged with the first. For example:
- The trip with trackId = 13538592 was considered one trip, when we expected it to be two.
- The trip with trackId = 13580467 was considered one trip, when we expected it to be three.
My first guess was that the first trip was not being uploaded before the second trip was being started which was causing the trips to be merged. I am not sure how the tracking is actually implemented though to verify.
I wondered if you could provide any input on why this might be happening?
Thank you.
Posted by Sam Helman about 1 year ago
Driving events
Hello i need to know the deference between Acceleration and speeding in the app please
Posted by Matthew Davis about 1 year ago