Configuration
To help the community, please let people know your inverter brand and charger API you got working with SolarCharger.
Home location must be defined in HA in order for HA to detect Tesla is at home. Settings > System > General > Edit location
Assuming your system has following entities, eg.
- sensor.line_voltage
- sensor.number_of_active_lines
Settings > Devices & services > Helpers > Create helper > Template > Template a sensor >
Name: Charger effective voltage
State template: {{ states('sensor.line_voltage') | float * states('sensor.number_of_active_lines') | int }}
Unit of measurement: V
Device class: Voltage
State class: Measurement
See note from @andrut1291 for 3-phase detection using Tesla Fleet API hidden entity "binary_sensor.charger_has_multiple_phases". And also this discussion.
To charge at maximum current between specific times, template a time-based minimum current sensor and use it to override the "Charger min current" entity in your charger, ie.
Settings > Devices & services > SolarCharger > Settings (cog wheel) > Select your charger > Override "Charger min current" with template sensor > Submit
For example, if using alandtse's integration to charge at maximum current between 23:00 and 01:00, template the sensor with those times.
Settings > Devices & services > Helpers > Create helper > Template > Template a sensor >
Name: Tesla23m3 time-based min current
State template:
{% set t = now().strftime('%H:%M') %}
{% if '23:00' <= t < '24:00' %}
{{ states('number.solarcharger_tesla_custom_tesla23m3_charger_max_current') }}
{% elif '00:00' <= t < '01:00' %}
{{ states('number.solarcharger_tesla_custom_tesla23m3_charger_max_current') }}
{% else %}
{{ states('number.solarcharger_tesla_custom_tesla23m3_charger_min_current') }}
{% endif %}
Unit of measurement: A
Device class: Current
State class: Measurement
The user is responsible for turning on SolarCharger if the required trigger is turned off. If all triggers are turned off (ie. Plugin trigger, Sun trigger, Schedule charge), user can now program their own automation to start and stop charge without interference from SolarCharger trying to start or stop the charging process.
Starting 1/July/2026 for households with smart meters in NSW and South East Queensland, the proposed free period is from 11am to 2pm. See Reference.
Settings > Devices & services > SolarCharger > Settings (cog wheel) > Global defaults > Monday charge limit default ... > Submit
Press the "Reset charge limit and time" button to apply the defaults when required.
- If "Schedule charge" is toggled off, charge limit will be set according to the Tesla app.
- If "Schedule charge" is toggled on and charge car based on weather is disabled, charge limit will be set according to the limit configured for the day.
- If "Schedule charge" is toggled on and charge car based on weather is enabled, charge limit will be adjusted to the highest limit set within the rainy forecast period taking into account the car charge limit on bad weather setting.
- Automatically adjust to a higher charge limit today if today has no charge completion time and next 3 days have higher charge limit. The day before the highest charge limit day will be set to 5% below the highest charge limit, otherwise it will be set to (N*10)% below the highest charge limit where N is the number of days before the highest charge limit day. The objective is to reduce charge limit difference between days to make it easier to achieve charge limit goals.
- If charge car based on weather is enabled, daily car charge limit and weather provider settings must be configured.
To determine battery maximum charge speed in charge level percentage rise per hour, see Calibrate max charge speed
Please try turning on the "Poll charger update" switch and test again to see if it makes a difference.
The following is most likely not required. See discussion.
I am not using Tesla Fleet API, so I am not sure what configuration is required for Tesla Fleet API to work with SolarCharger. I suspect charging status might not be up-to-date during the charging process. See vehicle sleep for polling and cost. Happy for any user feedback for improvement.
Create the button, eg.
- entity: input_button.[YourEvName]_tesla_fleet_api_update_ha
Create automation for the button, eg.
alias: [YourEvName] Tesla Fleet API update HA
description: Tesla Fleet API update HA on button press.
triggers:
- trigger: state
entity_id:
- input_button.[YourEvName]_tesla_fleet_api_update_ha
conditions: []
actions:
- action: homeassistant.update_entity
data:
entity_id:
- sensor.[YourEvName]_charging
mode: single
Set the power allocation weight for each device. Power is allocated according to the weight. The default weight is 1.
To delete the integration:
Settings > Devices and services > Integration tab > Solar Charger > 3-dots next to cog wheel > Delete
To re-add the integration:
Settings > Devices and services > Integration tab > Add integration > Search for "SolarCharger"
Redo any config customisation that you need.
Settings > Devices & services > SolarCharger > 3-dots next to cog wheel > Reconfigure
A corresponding change is required in SolarCharger, eg. if the MQTT switch entity is,
- switch.tesla_ble_[vin]_charger
There is an option to change the "tesla_ble_[vin]" part, and replace with the new name.
Settings > Devices & services > SolarCharger > Settings (cog wheel) > Select your device >
- Scroll down to near bottom and you should see red boxes indicating problem with invalid entities.
- Scroll to and set "Charger name" > Submit
Once submitted, check again to make sure there are no red boxes.
Settings > Devices & services > SolarCharger > Settings (cog wheel) > Select your device >
- Scroll down to near bottom to see if there are red boxes indicating problem with invalid entities.
- If there are red boxes, see this if you have renamed your charger.
- If there are no red boxes but boxes showing entities from incorrect integration, see this.
Please use esphome-tesla-ble v2026.2.1 or above, and then enable following hidden sensor,
sensor.[name]_charge_port_latch_state
