Feature Requests

Enable the close supported features on Frunks with aftermarket closers.

It would be useful if this integration could provide some control over the polling intervals it uses. At times when a vehicle is asleep a very long polling intervals is useful, alternatively when the vehicle is charging from excess solar a short polling intervals is useful.

The Tesla custom component allows a Service call to use defined endpoints and returns the response. This can be very useful for both POST and GET commands, setting tariffs and the like. It would be useful to add this functionality to Teslemetry. service: tesla_custom.api data: command: SITE_DATA parameters: path_vars: vehicle_id: "XXXXXXXXX" site_id: "YYYYYYYY" response: solar_power: 2857 energy_left: 1342.2631578947367 total_pack_energy: 40777 percentage_charged: 3.2917163055024568 backup_capable: true battery_power: -1490 load_power: 1367 grid_status: Active grid_services_active: false grid_power: 0 grid_services_power: 0 generator_power: 0 island_status: on_grid storm_mode_active: false timestamp: "2024-02-04T06:45:55

The current fleet API returns charger power as an kW integer which is too course for many applications. It would be useful to provide a calculated charger entity; phases volts amps = Watts Note the FleetAPI returns 1 for single phase and 2 for three phase.