Jay Banyer

FYI I tried to use this new field, however when I attempt to reference this field in a vehicle configuration (POST /api/1/vehicles/fleet_telemetry_config) I receive the following error: ``` { response:...

Thanks @Bre77. I've made some contributions to your Google sheet. I've looked and tested fairly carefully and I can not find any fields for the [actual] charging amps or voltage....

@agbpatro any chance you could comment on this one? Thanks.

I'm also interested in this question. Our use case requires knowing all the different charging states. Currently we use `charge_state.charging_state` in the Fleet API vehicle data.

@agbpatro are you able to comment on this? It's very important for our use case (chargehq.net). Thanks.

@agbpatro thanks, just reiterating @stx's comment that this issue is preventing us from moving to fleet telemetry. I did email [email protected] about it on 18th March but haven't had a...

Is there any way to detect that this problem has occurred, ie that the vehicle has rejected the config because it has too many apps configured? Will this situation fix...

@Bre77 I'm referring to when the third-party backend system (eg my system) is down for a while. During the time that it's down, vehicles will send field changes, and the...

@patrickdemers6 thanks for your reply. I think it would be best if the application was in control, since it is best placed to know that a resync is required. An...

In addition: when `prefer_typed` is true in the telemetry config, the data looks like this: ``` "key":"ScheduledChargingStartTime", "value":{ "longValue":"1736756100" } ``` The time zone appears completely wrong here. Unix time...