fleet-telemetry icon indicating copy to clipboard operation
fleet-telemetry copied to clipboard

Changes on 2024.26.3.x vehicles?

Open Urkman opened this issue 1 year ago • 8 comments

I'm experiencing data changes on 2024.26.3.x vehicles like this:

Location comes as: "(49.851094 N, 6.894920 E)"

And everything else is formatted like this: „\"81.906\"“ und nicht mehr „81.906“

For vehicles with 2024.20.9 everything is fine...

Urkman avatar Jul 30 '24 14:07 Urkman

Here is a log entry for a VIN I know it's on 2024.26.3.1

time="2024-07-30T15:26:52Z" level=info msg="logger_json_unmarshal VIN map[receivedat:1722353212000 timestamp:0 txid: txtype:V version:0 vin: VIN] {"data":[{"key":"Location", "value":{"stringValue":"\"(49.850634 N, 6.894050 E)\""}}, {"key":"FastChargerPresent", "value":{"stringValue":"\"false\""}}, {"key":"ChargeState", "value":{"stringValue":"\"Idle\""}}, {"key":"Gear", "value":{"stringValue":"\"R\""}}], "createdAt":"2024-07-30T15:26:52.017841265Z", "vin":"VIN"}\n"

Urkman avatar Jul 30 '24 15:07 Urkman

@patrickdemers6 Can you take a look?

Urkman avatar Jul 30 '24 15:07 Urkman

Ohh, location is now a string value?

bassmaster187 avatar Jul 30 '24 16:07 bassmaster187

And there is a change, how the data is send from the Tesla. When I ask for some data, it seems that I get all the data once and then only changes...

This is a major change :(

[2024-07-30 20:30:13] ["aCChargingPower", "chargeState", "ratedRange", "soc", "energyRemaining", "timeToFullCharge"]
[2024-07-30 20:30:13] ratedRange: "243.727",soc: "73.211",energyRemaining: "54.500",chargeState: "Enable",acchargingPower: "11.200",timeToFullCharge: "0.517"
[2024-07-30 20:30:43] energyRemaining: "54.620",acchargingPower: "11.100"
[2024-07-30 20:30:58] ratedRange: "244.273",soc: "73.375"
[2024-07-30 20:31:16] acchargingPower: "11.200"
[2024-07-30 20:31:23] energyRemaining: "54.760"
[2024-07-30 20:31:38] soc: "73.355"
[2024-07-30 20:31:40] ratedRange: "244.909"
[2024-07-30 20:31:47] acchargingPower: "11.100"
[2024-07-30 20:31:54] energyRemaining: "54.760"
[2024-07-30 20:32:10] soc: "73.566"
[2024-07-30 20:32:11] timeToFullCharge: "0.483"
[2024-07-30 20:32:19] acchargingPower: "11.100"
[2024-07-30 20:32:20] ratedRange: "245.455"
[2024-07-30 20:32:26] energyRemaining: "54.880"
[2024-07-30 20:32:42] soc: "73.730"
[2024-07-30 20:32:51] acchargingPower: "11.200"
[2024-07-30 20:32:58] energyRemaining: "55.000"
[2024-07-30 20:33:03] ratedRange: "246.091"
[2024-07-30 20:33:14] soc: "73.921"
[2024-07-30 20:33:23] acchargingPower: "11.100"
[2024-07-30 20:33:30] energyRemaining: "55.120"

Urkman avatar Jul 30 '24 18:07 Urkman

It will be very hard to maintain a bunch ob parsers, logic etc for different firmware versions if tesla will make brakeing changes from time to time...

bassmaster187 avatar Jul 30 '24 23:07 bassmaster187

I also have a user with this exact firmware and getting this different data structure. @patrickdemers6 is this a permanent change or a bug in the vehicle firmware?

Bre77 avatar Aug 07 '24 11:08 Bre77

Now that we have 2024.26.6 there are some changes back to older data format. But there is one huge problem.

Sending a new Config is not working most of the time. When I send a new config it is successful and checking if the config on the car is fine is also successful. But it keeps sending the old data for ever :( @patrickdemers6 can you please take a look at this. This will stop my App completely from woking...

Urkman avatar Aug 09 '24 07:08 Urkman

The change in data format was unintentional and has been resolved beginning with firmware version 2024.26.4.

@Urkman let me follow up in the other issue you keep pinging me in.

patrickdemers6 avatar Aug 24 '24 01:08 patrickdemers6