Using fleet-telemetry instead of polling vehicle-data API

[RichieB2B]

I just managed to configure the Tesla fleet-telemetry server to publish the data from my Model Y to my local MQTT server. This makes it very easy to start using this data instead of polling the vehicle-data API endpoint. Using fleet-telemetry is cheaper than using the API and the prefered way Tesla want apps like TWCManager to request this data.

Right now I'm requesting these fields:

        "fields": {
            "Soc": {
                "interval_seconds": 60
            },
            "ACChargingPower": {
                "interval_seconds": 60
            },
            "BatteryLevel": {
                "interval_seconds": 60
            },
            "ChargeAmps": {
                "interval_seconds": 60
            },
            "ChargeCurrentRequest": {
                "interval_seconds": 60
            },
            "ChargeCurrentRequestMax": {
                "interval_seconds": 60
            },
            "ChargeEnableRequest": {
                "interval_seconds": 60
            },
            "ChargeLimitSoc": {
                "interval_seconds": 60
            },
            "ChargerPhases": {
                "interval_seconds": 60
            },
            "ChargerVoltage": {
                "interval_seconds": 60
            },
            "DetailedChargeState": {
                "interval_seconds": 60
            },
            "Gear": {
                "interval_seconds": 60
            },
            "Location": {
                "interval_seconds": 60
            }
        }

Here is a full list of the available data. Are there any more feeds I should be requesting?

I'll do a write up about my configuration later. Since fleet-telemetry is not available for pre-2021 vehicles TWCManager should be able to support a hybrid solution: use the API for some vehicles and fleet-telemetry for others.

[MiRoCZ]

@RichieB2B Hello Richie, that's a great news ! I'm ready to help with testing on my fleet (TMY 2023, TM3 2021, TM3 2019). Looking forward to your configuration details.

[MiRoCZ]

Hello Richie @RichieB2B , this feeds seems to me also interesting for futher EMS automation:

EstBatteryRange	Charging	real	charge_state.est_battery_range	The estimated range of the vehicle given its current state of charge. Takes driving conditions into account.

EstimatedHoursToChargeTermination	Charging	real		The number of hours until reaching the desired state of charge. Desired state of charge is defined by ChargeLimitSoc.

DestinationLocation	Location	Location	drive_state.active_route_latitudedrive_state.active_route_longitude	The coordinates of the current navigation route's destination. If no navigation destination is set, Invalid will be returned.

MinutesToArrival	Location	real	drive_state.active_route_minutes_to_arrival	The minutes until arriving at the navigation destination. If no navigation destination is set, Invalid will be returned.

[RichieB2B]

The code I am using is now available at PR #617 with some documentation as well.