Jay Banyer

@ThomasAlxDmy any chance of a comment here? This is preventing us from using `prefer_typed`, and thus the new `minimum_delta` config option. Thanks!

@patrickdemers6 any chance of a comment here? This is preventing us from using `prefer_typed`, and thus the new `minimum_delta` config option. Thanks!

@patrickdemers6 thanks for your reply. I can work around the bug until it is fixed, by interpreting the epoch time as `America/Los_Angeles` time zone. Can you please update this ticket...

@patrickdemers6 any update here? Is the prefer_typed value (eg `"longValue":"1736756100"`) still in LA timezone for all vehicles?

@patrickdemers6 I reviewed #359 and made one comment about daylight savings. To confirm, with #359: - timestamps should be interpreted as UTC, and the result will actually be in the...

> Ok this actually isn't going to work at all since we need the vehicle's timezone. Working on a firmware fix. I don't understand this comment. As reported in #251,...

FWIW, in our case, for `ScheduledChargingStartTime`, what we actually want is to to determine if the vehicle is currently in the 6 hour window that follows the scheduled start time....

@stx the way we use the `ScheduledChargingStartTime` field is perhaps not what you'd expect. As I tried to explain above, we actually only want the local time-of-day of the schedule...

We've seen this on two vehicles. Both are Cybertrucks running software `2025.32.3.1 7b42491174e5`. Could it be the vehicle discharging into the home?

Possibly related: these Cybertrucks are now also publishing an unknown value for CarType. Here is the record published as JSON by fleet-telemetry: ``` { "data":[ { "key":"Soc", "value":{ "doubleValue":31.517228937398517 }...