Brett Adams

@jbanyer FYI we have observed three states from Streaming that map to polled values: "Idle": "stopped", #streaming "QualifyLineConfig": "starting", #streaming "Enable": "charging", #streaming https://github.com/Teslemetry/hass-teslemetry/blob/eb3e886e8222010d2e131c5092e5dd94f0444a18/custom_components/teslemetry/sensor.py#L49

> This is promising. It looks like the binary signals are not working and are either Unknown or Unavailable. There are currently also no actions available through the fleet api...

Native energy dashboard sensors (using the history API) are coming to Teslemetry in 2024.10 and should come to Tessie and Tesla Fleet in 2024.11

> > Native energy dashboard sensors (using the history API) are coming to Teslemetry in 2024.10 and should come to Tessie and Tesla Fleet in 2024.11 > > @Bre77 did...

Yeah I'll add to this, I'm the code owner of Tessie, Teslemetry, and as of 2024.8 Tesla Fleet, and I expected I'd need to write this in python in Home...

Previously when a second application configured telemetry the first was removed. Now you can have multiple, because my vehicle has both Tessie and Teslemetry working simultaneously. So I'm not sure...

@eddy-r the information provided by Tesla is power, not energy. Changing the device_class will make it show up in the energy dashboard, but the information will be incorrect. You need...

> Isn't it possible to set this up programmatically so that users don't each have to go hunting for how to do those steps? It sure is, but as far...

> Hey - so total novice first time user of HA which I primarily purchased for energy tracking to start with. I have the Tesla Fleet connected and obviously ran...

Documentation was updated with high level information, however we are working on adding actual history data for the energy dashboard now.