-
Notifications
You must be signed in to change notification settings - Fork 3
Design
By design, there are only 3 triggers that can start this automation,
- On sunrise at specified elevation.
- When you plug in the charger.
- Next charge time trigger set by this automation to meet tomorrow's charge end time if set.
This will then switch on the charger once to begin the charging process. On sunset at specified elevation, or when it reaches the desired charge limit, it will then switch off the charger once to end the charging process.
To determine if the automation is running or not, you might want to add this to your dashboard to show the automation running instance count.
This automation should be controlled on the HA side only. The Tesla side of things can have its own config, eg. schedule charging, etc, and may have different objectives. It is best to keep the 2 sides separate.
If it helps, here is a link on how to set up a button on HA to manually start the automation if required.
Use grid electricity by setting the charger minimum current above zero. Do not confuse power offset with charger minimum current setting. Power offset sets the maximum power from secondary power source (grid/battery) that can be used to charge car but is shared among all appliances of which the car charger has the lowest priority.
"Charger minimum current" and "Power offset" can be number helpers or template sensors that can be used to control charger power consumption according to time-of-use tariff, free charging period, etc.
By selecting a specific API, eg. "Tesla Fleet API", you are telling the Blueprint to use Tesla Fleet API entity names. Therefore whatever API entity names you entered in the Blueprint will be ignored.
For example, for the "Charger on/off switch" below, the Tesla Fleet API entity name is automatically set to "switch.[CarName_]charge". You cannot override the entity name unless you select "User custom API".
Charger on/off switch
Switch to turn charger on or off. Config is automatically defined for the selected API unless it is marked as Not defined.
Tesla Custom: switch.[CarName_]charger
Tesla Fleet: switch.[CarName_]charge
Tesla BLE: switch.tesla_ble_[vin]_charger
OCPP: switch.[ChargerName]_charge_control
User custom: Not defined
To verify whether the API is working with this Blueprint, I suggest to try first with your Tesla UMC mobile charger.
HA Tessie and Tesla Fleet APIs seemed to be using the same entity names. So if you are using Tessie integration, you should be able to select "Tesla Fleet API" as the charge control API in the Blueprint. See this discussion for more info.
If you select "User custom API" as your charge control API, you can program your own API return codes for the connect trigger states, connected states and charging states supported by your EV or charger specific API.