Hi,
I am currently using telemetry to extract vehicle charging and driving information. Since I only need the telemetry field values at the exact start and end of charging/driving sessions, I want to avoid receiving continuous intermediate data. To achieve this, I have been testing dynamic updates to the telemetry config.
However, I've run into a few issues during testing:
- Inconsistent telemetry config sync and application
Sometimes, when I change the telemetry config, it syncs immediately and transmits the field values in a batch, which is exactly the behavior I want to leverage. But frequently during my tests, newly created telemetry configs fail to apply.
Is there a rate limit or restriction on how often telemetry config create can be called?
Specifically, even when I send delete telemetry config and then consecutively try to create a new config, the new config is occasionally ignored.
Additionally, there were cases where a new telemetry config got applied even when the sync status is false. Could you clarify why this happens?
- Alternative to vehicle_data for on-demand telemetry fields
The vehicle_data API is too "expensive" and forces me to fetch the entire payload, including data I don't need. I am looking for a more efficient way to fetch only my desired telemetry fields.
Is there a way to request a one-time, batch update/fetch for specific telemetry values? I don't mind if the process operates asynchronously.
Any guidance, clarifications, or workarounds would be greatly appreciated!
Hi,
I am currently using telemetry to extract vehicle charging and driving information. Since I only need the telemetry field values at the exact start and end of charging/driving sessions, I want to avoid receiving continuous intermediate data. To achieve this, I have been testing dynamic updates to the telemetry config.
However, I've run into a few issues during testing:
Sometimes, when I change the telemetry config, it syncs immediately and transmits the field values in a batch, which is exactly the behavior I want to leverage. But frequently during my tests, newly created telemetry configs fail to apply.
Is there a rate limit or restriction on how often telemetry config create can be called?
Specifically, even when I send delete telemetry config and then consecutively try to create a new config, the new config is occasionally ignored.
Additionally, there were cases where a new telemetry config got applied even when the sync status is false. Could you clarify why this happens?
The vehicle_data API is too "expensive" and forces me to fetch the entire payload, including data I don't need. I am looking for a more efficient way to fetch only my desired telemetry fields.
Is there a way to request a one-time, batch update/fetch for specific telemetry values? I don't mind if the process operates asynchronously.
Any guidance, clarifications, or workarounds would be greatly appreciated!