Tesla API & Existing Home Assistant Integration

[jkerekes99]

Hi, as with most people I have just updated to 0.133 with the Tesla Changes.
I have a Tesla Wall Connector and Model 3.

I already have the car integrated to Home Assistant using the Tesla HTTP Proxy Addin and I already have the Wall Connector integrated to Home Assistant.

Rather than creating a new Fleet API app for EVCC (and Telsamate proxy for the Wall Connector), can I use the entities already available in Home Assistant?
Is there a documented way to do this?

Thanks in advance.

[mucki12]

You mean something like a custom charger based on the entities of the Tesla Fleet Integration from HA?

A very interesting idea. Maybe if you transfer the entities via MQTT?

[jkerekes99]

Yes correct, but not just the charger, but the vehicle as well.
My thinking is, that I already have all the Tesla stuff integrated with HA, so why have EVCC connect separately (as it will mean another proxy etc).

Just looking to see if anyone has achieved this and what the config might look like?

[jkerekes99]

I am already using entities out of HA for my inverter (as per below).

However I don't know what entities are required for chargers and vehicles (if anyone knows?)

`meters:

• name: Sungrow.grid
  type: custom
  power:
  source: http
  uri: http://192.168.8.2:8123/api/states/sensor.grid_import_and_export
  method: GET
  headers:
  - Authorization: Bearer ###redacted###
  insecure: true
  jq: .state|tonumber
  timeout: 2s

• name: Sungrow.pv
  type: custom
  power:
  source: http
  uri: http://192.168.8.2:8123/api/states/sensor.pv_inverter_active_generation
  method: GET
  headers:
  - Authorization: Bearer ###redacted###
  insecure: true
  jq: .state|tonumber
  timeout: 2s`

[krilupo]

Same idea came to my mind - I am also interested in this. Especially since every poll/query costs money. Although everybody has the $10 credit but I can see from the last couple of days switching to the new API that the $10 might be tight.
So, possibly this can also reduce the number of queries since the data is already in HA.

[jkerekes99]

yep, my thoughts exactly.

If anyone knows what entities EVCC needs / is expecting and how we can add them into the config (either via HTTP/API or MQTT)?

[larknafets]

This is taken from an older readme from Tesla BLE Http Proxy. It may helps you. You need to change all GET methods to MQTT. But I'm not sure how you want to make the POST commands work or if they are needed.

evcc documentation for custom vehicle and charger may also help.

vehicles:
  - name: tesla
    type: custom
    title: Your Tesla
    icon: car
    capacity: 60
    chargeenable:
      source: http
      uri: "http://IP:8080/api/1/vehicles/VIN/command/{{if .chargeenable}}charge_start{{else}}charge_stop{{end}}"
      method: POST
      body: ""
    maxcurrent: # set charger max current (A)
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/command/set_charging_amps
      method: POST
      body: '{"charging_amps": "{{.maxcurrent}}"}'
    wakeup: # vehicle wake up command
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/command/wake_up
      method: POST
      body: ""
    soc:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.response.charge_state.battery_level
      timeout: 30s 
    limitsoc:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.response.charge_state.charge_limit_soc
      timeout: 30s
    range:
      source: http
      uri: http://IP:8080/api/1/vehicles/VIN/vehicle_data?endpoints=charge_state
      method: GET
      jq: .response.response.charge_state.battery_range
      scale: 1.60934
      timeout: 30s

Source:
wimaha/TeslaBleHttpProxy@e7829c4#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L122-L125

[jkerekes99]

Thanks for this.
I am using HTTP not MQTT, so should be fine.
The POST commands will be different (wonder if anyone knows?)

What about the Tesla Wall Connector? What entities are required?

[jkerekes99]

I think I got all the GET queries correct:

wakeup: # vehicle wake up command
  source: http
  uri: http://192.168.8.2:8123/api/states/button.josh_s_model_3_wake_up
  method: POST
  body: ""
  headers:
    - Authorization: Bearer redacted
  insecure: true
soc:
  source: http
  uri: http://192.168.8.2:8123/api/states/sensor.josh_s_model_3_battery
  method: GET
  headers:
    - Authorization: Bearer redacted
  insecure: true
  jq: .state|tonumber
  timeout: 2s
limitsoc:
  source: http
  uri: http://192.168.8.2:8123/api/states/number.josh_s_model_3_charge_limit
  method: GET
  headers:
    - Authorization: Bearer redacted
  insecure: true
  jq: .state|tonumber
  timeout: 2s
range:
  source: http
  uri: http://192.168.8.2:8123/api/states/sensor.josh_s_model_3_range
  method: GET
  headers:
    - Authorization: Bearer redacted
  insecure: true
  timeout: 2s

The POSTs I am not sure what the correct syntax is?

Entities available:

chargeenable:

maxcurrent:

[jkerekes99]

Tesla Wall Connector entities: