TeslaSolarCharger

TeslaSolarCharger is a service to set one or multiple Teslas' charging current using the datalogger TeslaMate.

How to install
Often used optional settings
How to use
- Charge Modes
Generate logfiles
Privacy notes

How to install

You can either install the software in a Docker container or download the binaries and deploy it on any server. In June 2024, Tesla implemented rate limits to their API, so there is a BLE (Bluetooth Low Energy, implemented since Bluetooth Version 4.0) capable device needed near the car. You can find details on how to set up BLE here.

Docker compose

The easiest way to use TeslaSolarCharger is with Docker.

Depending on your system, you have to install Docker first. To do this on a RaspberryPi (should be the same on standard Linux systems), you need to execute the following commands in your Terminal window:

Install Docker
```
curl -sSL https://get.docker.com | sh
```
Add permissions to the pi user. If you have another username, update the command accordingly
```
sudo usermod -aG docker pi
```
Reboot your Raspberry Pi
Test the Docker installation
```
docker run hello-world
```
If any issues occur, try to identify them using this more detailed instruction.

If you are using a Windows host, install the Software from here. Windows 11 is highly recommended. Select Linux Containers in the installation process.

Setting up TeslaMate including TeslaSolarCharger

To set up TeslaSolarCharger, you must create a docker-compose.yml (name is important!) file in a new directory. Note: During the setup, some additional data folders to persist data will be created in that folder, so it is recommended to use a new directory for your docker-compose.yml.

docker-compose.yml content

The needed content of your docker-compose.yml depends on your inverter. By default, TeslaSolarCharger can consume JSON/XML REST APIs. To get the software running on SMA or SolarEdge, you can use specific plugins which create the needed JSON API. You can use the software with any ModbusTCP-capable inverter also.

Content without using a plugin

Below you can see the content for your docker-compose.yml if you are not using any plugin. Note: I recommend changing as few things as possible on this file as this will increase the effort to set everything up but feel free to change the database password, encryption key, and Timezone. Important: If you change the password or the encryption key, you need to use the same password and encryption key at all points in your docker-compose.yml

version: '3.3'

services:
  teslamate:
    image: teslamate/teslamate:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret ##You can change your password here
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
      - ENCRYPTION_KEY=supersecret ##You can change your encryption key here
      - TZ=Europe/Berlin ##You can change your Timezone here
    ports:
      - 4000:4000
    volumes:
      - ./import:/opt/app/import
    cap_drop:
      - all

  database:
    image: postgres:15
    restart: always
    environment:
      - POSTGRES_USER=teslamate
      - POSTGRES_PASSWORD=secret ##You can change your password here
      - POSTGRES_DB=teslamate
    volumes:
      - teslamate-db:/var/lib/postgresql/data

  grafana:
    image: teslamate/grafana:latest
    restart: always
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret ##You can change your password here
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
    ports:
      - 3100:3000
    volumes:
      - teslamate-grafana-data:/var/lib/grafana

  mosquitto:
    image: eclipse-mosquitto:2
    restart: always
    command: mosquitto -c /mosquitto-no-auth.conf
    #ports:
    #  - 1883:1883
    volumes:
      - mosquitto-conf:/mosquitto/config
      - mosquitto-data:/mosquitto/data

  teslamateapi:
    image: tobiasehlert/teslamateapi:latest
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
    restart: always
    depends_on:
      - database
    environment:
      - DATABASE_USER=teslamate
      - DATABASE_PASS=secret ##You can change your password here
      - DATABASE_NAME=teslamate
      - DATABASE_HOST=database
      - MQTT_HOST=mosquitto
      - TZ=Europe/Berlin ##You can change your Timezone here
      - ENABLE_COMMANDS=true
      - COMMANDS_ALL=true
      - API_TOKEN_DISABLE=true
      - ENCRYPTION_KEY=supersecret ##You can change your encryption key here
    #ports:
    #  - 8080:8080

  teslasolarcharger:
    image: pkuehnel/teslasolarcharger:latest
    container_name: teslasolarcharger
    logging:
        driver: "json-file"
        options:
            max-file: "10"
            max-size: "100m"
    restart: always
    depends_on:
      - teslamateapi
    environment:
#      - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs
      - TZ=Europe/Berlin ##You can change your Timezone here
    ports:
      - 7190:80
    volumes:
      - teslasolarcharger-configs:/app/configs

volumes:
  teslamate-db:
  teslamate-grafana-data:
  mosquitto-conf:
  mosquitto-data:
  teslasolarcharger-configs:

Content using SMA plugin

The SMA plugin is used to access your EnergyMeter (or Sunny Home Manager 2.0) values. To use the plugin, add these lines to the bottom of your docker-compose.yml.

  smaplugin:
    image: pkuehnel/teslasolarchargersmaplugin:latest
    container_name: teslasolarcharger_smaplugin
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
    restart: always
    network_mode: host
    environment:
      - ASPNETCORE_URLS=http://+:7192

You can also copy the complete content from here:

Complete file using SMA plugin

```yaml version: '3.3' services: teslamate: image: teslamate/teslamate:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - ENCRYPTION_KEY=supersecret ##You can change your encryption key here - TZ=Europe/Berlin ##You can change your Timezone here ports: - 4000:4000 volumes: - ./import:/opt/app/import cap_drop: - all database: image: postgres:15 restart: always environment: - POSTGRES_USER=teslamate - POSTGRES_PASSWORD=secret ##You can change your password here - POSTGRES_DB=teslamate volumes: - teslamate-db:/var/lib/postgresql/data grafana: image: teslamate/grafana:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database ports: - 3100:3000 volumes: - teslamate-grafana-data:/var/lib/grafana mosquitto: image: eclipse-mosquitto:2 restart: always command: mosquitto -c /mosquitto-no-auth.conf #ports: # - 1883:1883 volumes: - mosquitto-conf:/mosquitto/config - mosquitto-data:/mosquitto/data teslamateapi: image: tobiasehlert/teslamateapi:latest logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always depends_on: - database environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - TZ=Europe/Berlin ##You can change your Timezone here - ENABLE_COMMANDS=true - COMMANDS_ALL=true - API_TOKEN_DISABLE=true - ENCRYPTION_KEY=supersecret ##You can change your encryption key here #ports: # - 8080:8080 teslasolarcharger: image: pkuehnel/teslasolarcharger:latest container_name: teslasolarcharger logging: driver: "json-file" options: max-file: "10" max-size: "100m" restart: always depends_on: - teslamateapi environment: # - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs - TZ=Europe/Berlin ##You can change your Timezone here ports: - 7190:80 volumes: - teslasolarcharger-configs:/app/configs smaplugin: image: pkuehnel/teslasolarchargersmaplugin:latest container_name: teslasolarcharger_smaplugin logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always network_mode: host environment: - ASPNETCORE_URLS=http://+:7192 volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: teslasolarcharger-configs: ```

Content using SolarEdge plugin

The SolarEdge Plugin uses the cloud API, which is limited to 300 which is reset after 15 minutes. When the limit is reached the solaredge API does not gather any new values. This results in TSC displaying 0 grid and home battery power until 15 minutes are over.

To use the plugin, just add these lines to the bottom of your docker-compose.yml. Note: You have to change your site ID and your API key in the CloudUrl environment variable

  solaredgeplugin:
    image: pkuehnel/teslasolarchargersolaredgeplugin:latest
    container_name: teslasolarcharger_solaredgeplugin
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
    restart: always
    environment:
      - CloudUrl=https://monitoringapi.solaredge.com/site/1561056/currentPowerFlow.json?api_key=asdfasdfasdfasdfasdfasdf& ##Change your site ID and API Key here
    ports:
      - 7193:80

You can also copy the complete content from here:

Complete file using SolarEdge plugin

```yaml version: '3.3' services: teslamate: image: teslamate/teslamate:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - ENCRYPTION_KEY=supersecret ##You can change your encryption key here - TZ=Europe/Berlin ##You can change your Timezone here ports: - 4000:4000 volumes: - ./import:/opt/app/import cap_drop: - all database: image: postgres:15 restart: always environment: - POSTGRES_USER=teslamate - POSTGRES_PASSWORD=secret ##You can change your password here - POSTGRES_DB=teslamate volumes: - teslamate-db:/var/lib/postgresql/data grafana: image: teslamate/grafana:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database ports: - 3100:3000 volumes: - teslamate-grafana-data:/var/lib/grafana mosquitto: image: eclipse-mosquitto:2 restart: always command: mosquitto -c /mosquitto-no-auth.conf #ports: # - 1883:1883 volumes: - mosquitto-conf:/mosquitto/config - mosquitto-data:/mosquitto/data teslamateapi: image: tobiasehlert/teslamateapi:latest logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always depends_on: - database environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - TZ=Europe/Berlin ##You can change your Timezone here - ENABLE_COMMANDS=true - COMMANDS_ALL=true - API_TOKEN_DISABLE=true - ENCRYPTION_KEY=supersecret ##You can change your encryption key here #ports: # - 8080:8080 teslasolarcharger: image: pkuehnel/teslasolarcharger:latest container_name: teslasolarcharger logging: driver: "json-file" options: max-file: "10" max-size: "100m" restart: always depends_on: - teslamateapi environment: # - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs - TZ=Europe/Berlin ##You can change your Timezone here ports: - 7190:80 volumes: - teslasolarcharger-configs:/app/configs solaredgeplugin: image: pkuehnel/teslasolarchargersolaredgeplugin:latest container_name: teslasolarcharger_solaredgeplugin logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always environment: - CloudUrl=https://monitoringapi.solaredge.com/site/1561056/currentPowerFlow.json?api_key=asdfasdfasdfasdfasdfasdf& ##Change your site ID and API Key here ports: - 7193:80 volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: teslasolarcharger-configs: ```

Content using Modbus plugin

You can also use the Modbus plugin. This is a general plugin, so don't be surprised if it does not work as expected right after starting up. Feel free to share your configurations here so I can add templates for future users.

To use the plugin, just add these lines to the bottom of your docker-compose.yml. Note: As some inverters struggle with too many requests within a specific time, you can change the RequestBlockMilliseconds environment variable.

  modbusplugin:
    image: pkuehnel/teslasolarchargermodbusplugin:latest
    container_name: teslasolarcharger_modbusplugin
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
    restart: always
    environment:
      - RequestBlockMilliseconds=0
    ports:
      - 7191:80

You can also copy the complete content from here:

Complete file using Modbus plugin

```yaml version: '3.3' services: teslamate: image: teslamate/teslamate:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - ENCRYPTION_KEY=supersecret ##You can change your encryption key here - TZ=Europe/Berlin ##You can change your Timezone here ports: - 4000:4000 volumes: - ./import:/opt/app/import cap_drop: - all database: image: postgres:15 restart: always environment: - POSTGRES_USER=teslamate - POSTGRES_PASSWORD=secret ##You can change your password here - POSTGRES_DB=teslamate volumes: - teslamate-db:/var/lib/postgresql/data grafana: image: teslamate/grafana:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database ports: - 3100:3000 volumes: - teslamate-grafana-data:/var/lib/grafana mosquitto: image: eclipse-mosquitto:2 restart: always command: mosquitto -c /mosquitto-no-auth.conf #ports: # - 1883:1883 volumes: - mosquitto-conf:/mosquitto/config - mosquitto-data:/mosquitto/data teslamateapi: image: tobiasehlert/teslamateapi:latest logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always depends_on: - database environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - TZ=Europe/Berlin ##You can change your Timezone here - ENABLE_COMMANDS=true - COMMANDS_ALL=true - API_TOKEN_DISABLE=true - ENCRYPTION_KEY=supersecret ##You can change your encryption key here #ports: # - 8080:8080 teslasolarcharger: image: pkuehnel/teslasolarcharger:latest container_name: teslasolarcharger logging: driver: "json-file" options: max-file: "10" max-size: "100m" restart: always depends_on: - teslamateapi environment: # - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs - TZ=Europe/Berlin ##You can change your Timezone here ports: - 7190:80 volumes: - teslasolarcharger-configs:/app/configs modbusplugin: image: pkuehnel/teslasolarchargermodbusplugin:latest container_name: teslasolarcharger_modbusplugin logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always environment: - RequestBlockMilliseconds=0 ports: - 7191:80 volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: teslasolarcharger-configs: ```

Content using Solax plugin

To use the Solax plugin, just add these lines to the bottom of your docker-compose.yml. Note: You have to specify your solar system's IP address and password.

  solaxplugin:
    image: pkuehnel/teslasolarchargersolaxplugin:latest
    container_name: teslasolarcharger_solaxplugin
    logging:
        driver: "json-file"
        options:
            max-file: "5"
            max-size: "10m"
    restart: always
    environment:
      - SolarSystemBaseUrl=http://192.168.1.50 ##Change IP Address to your solar system
      - SolarSystemPassword=AD5TSVGR51 ##Change this to the password of your solar system (wifi dongle serial number)
    ports:
      - 7194:80

You can also copy the complete content from here:

Complete file using Solax plugin

```yaml version: '3.3' services: teslamate: image: teslamate/teslamate:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - ENCRYPTION_KEY=supersecret ##You can change your encryption key here - TZ=Europe/Berlin ##You can change your Timezone here ports: - 4000:4000 volumes: - ./import:/opt/app/import cap_drop: - all database: image: postgres:15 restart: always environment: - POSTGRES_USER=teslamate - POSTGRES_PASSWORD=secret ##You can change your password here - POSTGRES_DB=teslamate volumes: - teslamate-db:/var/lib/postgresql/data grafana: image: teslamate/grafana:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database ports: - 3100:3000 volumes: - teslamate-grafana-data:/var/lib/grafana mosquitto: image: eclipse-mosquitto:2 restart: always command: mosquitto -c /mosquitto-no-auth.conf #ports: # - 1883:1883 volumes: - mosquitto-conf:/mosquitto/config - mosquitto-data:/mosquitto/data teslamateapi: image: tobiasehlert/teslamateapi:latest logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always depends_on: - database environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - TZ=Europe/Berlin ##You can change your Timezone here - ENABLE_COMMANDS=true - COMMANDS_ALL=true - API_TOKEN_DISABLE=true - ENCRYPTION_KEY=supersecret ##You can change your encryption key here #ports: # - 8080:8080 teslasolarcharger: image: pkuehnel/teslasolarcharger:latest container_name: teslasolarcharger logging: driver: "json-file" options: max-file: "10" max-size: "100m" restart: always depends_on: - teslamateapi environment: # - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs - TZ=Europe/Berlin ##You can change your Timezone here ports: - 7190:80 volumes: - teslasolarcharger-configs:/app/configs solaxplugin: image: pkuehnel/teslasolarchargersolaxplugin:latest container_name: teslasolarcharger_solaxplugin logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always environment: - SolarSystemBaseUrl=http://192.168.1.50 ##Change IP Address to your solar system - SolarSystemPassword=AD5TSVGR51 ##Change this to the password of your solar system (wifi dongle serial number) ports: - 7194:80 volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: teslasolarcharger-configs: ```

First startup of the application

Move to your above created directory with your docker-compose.yml.
Start all containers using the command docker compose up -d.
Use a third-party app to create a new Tesla Token [Android] [iOS]
Open your browser, go to http://your-ip-address:4000 and paste your token and refresh token into the form.
Go to Geo-Fences and add a Geo-Fence called Home at the location you want TeslaSolarCharger to be active.
Open http://your-ip-address:7190
Go to Base Configuration (if you are on a mobile device, it is behind the menu button).

Setting Up Urls to get grid power

To let the TeslaSolarCharger know how much power there is to charge the car, you need to add a value in Grid Power Url.

Using vendor specific plugins

Note: These values will be filled in automatically in a future release. Maybe it is already working, and I just forgot to remove this section ;-) Depending on your used plugins, you have to paste one of the following URLs to the Grid Power Url field:

SMA Plugin: http://<IP of your Docker host>:7192/api/CurrentPower/GetPower
Note: If you have more than one EnergyMeter/Home Manager 2.0 in your network, you need to add the serial number of the correct device. A grid URL would look like this then: http://<IP of your Docker host>:7192/api/CurrentPower/GetPower?serialNumber=3001231234
SolarEdge Plugin:
- Grid Power, InverterPower, HomeBatterySoc, Home Battery Power Url: http://solaredgeplugin/api/CurrentValues/GetCurrentPvValues
- Set Result types to json and use the following json patterns:
- Grid Power: $.gridPower
- Inverter Power: $.inverterPower
- Home Battery SoC: $.homeBatterySoc
- Home Battery Power: $.homeBatteryPower
Solax Plugin:
- Grid Power, InverterPower, HomeBatterySoc, Home Battery Power Url: http://solaxplugin/api/CurrentValues/GetCurrentPvValues
- Set Result types to json and use the following json patterns:
- Grid Power: $.gridPower
- Inverter Power: $.inverterPower
- Home Battery SoC: $.homeBatterySoc
- Home Battery Power: $.homeBatteryPower
- The result should look like this:

Using the Modbus plugin

Warning: As this plugin keeps an open connection to your inverter, it is highly recommended not to kill this container but always shut it down gracefully. To use the Modbus plugin, you must create the URL string yourself. The URL looks like this:

http://modbusplugin/api/Modbus/GetInt32Value?unitIdentifier=3&startingAddress=<modbusregisterAddress>&quantity=<NumberOFModbusRegistersToRead>&ipAddress=<IPAdressOfModbusDevice>&port=502&factor=<conversionFactor>&connectDelaySeconds=1&timeoutSeconds=10

An example URL with all values filled could look like this:

http://modbusplugin/api/Modbus/GetInt32Value?unitIdentifier=3&startingAddress=30775&quantity=2&ipAddress=192.168.1.28&port=502&factor=1&connectDelaySeconds=1&timeoutSeconds=10

You can test the result of the URL by pasting it into your browser and replacing modbusplugin with ipOfYourDockerHost:7191, e.g.:

http://192.168.1.50:7191/api/Modbus/GetInt32Value?unitIdentifier=3&startingAddress=30775&quantity=2&ipAddress=192.168.1.28&port=502&factor=1&connectDelaySeconds=1&timeoutSeconds=10

What the values mean:

unitIdentifier: Internal ID of your inverter (in most cases, 3)
startingAddress: Register address of the value you want to extract. You will find this value in the documentation of your inverter.
quantity: Number of registers to read from (for integer values should be 2)
ipAddress: IP Address of your inverter
port: Modbus TCP Port of your inverter (default: 502)
factor: Factor to multiply the resulting value with. The result should be Watt, so if your inverter returns Watt, you can leave 1. If your inverter returns 0.1W, you have to use 10.
connectDelaySeconds: Delay before communication the first time (you should use 1)
timeoutSeconds: Timeout until returning an error if the inverter is not responding (you should use 10)

For more convenience, you can go to http://your-ip-address:7191/swagger. There you can try your values with a user interface.

Using no plugin

If you have your own API or your energymeter directly has a REST API, you can also use these to get the grid power. Just insert the Grid Power Url Url; if there is a plain integer value, it should work. If your API returns JSON or XML results, you must add the exact path to that specific value.

JSON Path

If you have the following JSON result:

{
  "request": {
    "method": "get",
    "key": "asdf"
  },
  "code": 0,
  "type": "call",
  "data": {
    "value": 14
  }
}

You can use $.data.value as Grid Power Json Pattern.

XML Path

If your energy monitoring device or inverter has no JSON, but an XML API, use the following instructions: Given an API endpoint http://192.168.xxx.xxx/measurements.xml which returns the following XML:

<?xml version="1.0" encoding="UTF-8"?>
<Device Name="PIKO 4.6-2 MP plus" Type="Inverter" Platform="Net16" HmiPlatform="HMI17" NominalPower="4600" UserPowerLimit="nan" CountryPowerLimit="nan" Serial="XXXXXXXXXXXXXXXXXXXX" OEMSerial="XXXXXXXX" BusAddress="1" NetBiosName="XXXXXXXXXXXXXXX" WebPortal="PIKO Solar Portal" ManufacturerURL="kostal-solar-electric.com" IpAddress="192.168.XXX.XXX" DateTime="2022-06-08T19:33:25" MilliSeconds="806">
  <Measurements>
    <Measurement Value="231.3" Unit="V" Type="AC_Voltage"/>
    <Measurement Value="1.132" Unit="A" Type="AC_Current"/>
    <Measurement Value="256.1" Unit="W" Type="AC_Power"/>
    <Measurement Value="264.3" Unit="W" Type="AC_Power_fast"/>
    <Measurement Value="49.992" Unit="Hz" Type="AC_Frequency"/>
    <Measurement Value="474.2" Unit="V" Type="DC_Voltage"/>
    <Measurement Value="0.594" Unit="A" Type="DC_Current"/>
    <Measurement Value="473.5" Unit="V" Type="LINK_Voltage"/>
    <Measurement Value="18.7" Unit="W" Type="GridPower"/>
    <Measurement Value="0.0" Unit="W" Type="GridConsumedPower"/>
    <Measurement Value="18.7" Unit="W" Type="GridInjectedPower"/>
    <Measurement Value="237.3" Unit="W" Type="OwnConsumedPower"/>
    <Measurement Value="100.0" Unit="%" Type="Derating"/>
  </Measurements>
</Device>

Grid Power: Assuming the Measurement node with Type GridPower is the power your house feeds to the grid, you need the following values in your Base configuration:

- CurrentPowerToGridUrl=http://192.168.xxx.xxx/measurements.xml
- CurrentPowerToGridXmlPattern=Device/Measurements/Measurement
- CurrentPowerToGridXmlAttributeHeaderName=Type
- CurrentPowerToGridXmlAttributeHeaderValue=GridPower
- CurrentPowerToGridXmlAttributeValueName=Value

Inverter Power: Assuming the Measurement node with Type AC_Power is the power your inverter is currently feeding, you can use the following values in your Base configuration:

- CurrentInverterPowerUrl=http://192.168.xxx.xxx/measurements.xml
- CurrentInverterPowerXmlPattern=Device/Measurements/Measurement
- CurrentInverterPowerAttributeHeaderName=Type
- CurrentInverterPowerAttributeHeaderValue=AC_Power
- CurrentInverterPowerAttributeValueName=Value

Note: These values are not needed. They are just used to show additional information.

Correction Factors

The correction factor is used to multiply the input value so that the results correspond with what TeslaSolarCharger expects.

Input	Expected Value
Inverter Power	A measurement of solar power generated as a positive number in Watts (W)
Grid Power	A measurement of grid power export/ import in Watts (W). A export to the grid should be positive and an import from the grid should be negative.
Home Battery Power	A measurement of home battery power charge/ discharge in Watts (W). If the battery is charging, this should be positive and if it is discharging this should be negative.
Home Battery SoC	A measurement of the percentage charge of your home battery from 0-100%

You can use the correction factors to scale/ correct these values as appropriate. For example:

Grid Power input expresses a positive integer as an import and a negative as an export: Select negative for the operator and 1 for the correction factor (this multiplies by -1).
Inverter Power is expressed as kW instead of W: Select positive for the operator and 1000 for the correction factor (this multiplies by 1000).
Home Battery expresses its state of charge as an absolute value in kWh: Select positive for the operator and a correction factor of 1/(Full Charge Capacity) e.g. if the battery has a full charge capacity of 100kWh the correction factor is 1/100 or 0.01

Install and setup BLE API

To go around Teslas API limitations, you can use Bluetooth (BLE) to control your car. You can do this either by using the same device as your TSC is running on, or by using a separate device. Note: The device needs to be placed near the car.

Confirmed working hardware:

Raspberry Pi Zero 2W (only capable when used as separate device)
Raspberry Pi 3 Model B
Raspberry Pi 4 Model B
Raspberry Pi 5

Install BLE API on the same device as TSC

To set up the BLE API on the same device as your TSC is running on, you need to add the following lines to your docker-compose.yml:

services:
#here are all the other services like TeslaMate, TSC, etc.
  bleapi:
    image: ghcr.io/pkuehnel/teslasolarchargerbleapi:latest
    container_name: TeslaSolarChargerBleApi
    privileged: true
    restart: unless-stopped
    network_mode: host
    environment:
      - ASPNETCORE_URLS=http://+:7210
    volumes:
      - tscbleapi:/externalFiles
      - /var/run/dbus:/var/run/dbus

volumes:
  #here are all the other volumes like teslamate-db, teslamate-grafana-data, etc.
  tscbleapi:

You can also copy the complete content from here:

Complete file including BLE API

```yaml version: '3.3' services: teslamate: image: teslamate/teslamate:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - ENCRYPTION_KEY=supersecret ##You can change your encryption key here - TZ=Europe/Berlin ##You can change your Timezone here ports: - 4000:4000 volumes: - ./import:/opt/app/import cap_drop: - all database: image: postgres:15 restart: always environment: - POSTGRES_USER=teslamate - POSTGRES_PASSWORD=secret ##You can change your password here - POSTGRES_DB=teslamate volumes: - teslamate-db:/var/lib/postgresql/data grafana: image: teslamate/grafana:latest restart: always environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database ports: - 3100:3000 volumes: - teslamate-grafana-data:/var/lib/grafana mosquitto: image: eclipse-mosquitto:2 restart: always command: mosquitto -c /mosquitto-no-auth.conf #ports: # - 1883:1883 volumes: - mosquitto-conf:/mosquitto/config - mosquitto-data:/mosquitto/data teslamateapi: image: tobiasehlert/teslamateapi:latest logging: driver: "json-file" options: max-file: "5" max-size: "10m" restart: always depends_on: - database environment: - DATABASE_USER=teslamate - DATABASE_PASS=secret ##You can change your password here - DATABASE_NAME=teslamate - DATABASE_HOST=database - MQTT_HOST=mosquitto - TZ=Europe/Berlin ##You can change your Timezone here - ENABLE_COMMANDS=true - COMMANDS_ALL=true - API_TOKEN_DISABLE=true - ENCRYPTION_KEY=supersecret ##You can change your encryption key here #ports: # - 8080:8080 teslasolarcharger: image: pkuehnel/teslasolarcharger:latest container_name: teslasolarcharger logging: driver: "json-file" options: max-file: "10" max-size: "100m" restart: always depends_on: - teslamateapi environment: # - Serilog__MinimumLevel__Default=Verbose #uncomment this line and recreate container with docker compose up -d for more detailed logs - TZ=Europe/Berlin ##You can change your Timezone here ports: - 7190:80 volumes: - teslasolarcharger-configs:/app/configs bleapi: image: ghcr.io/pkuehnel/teslasolarchargerbleapi:latest container_name: TeslaSolarChargerBleApi privileged: true restart: unless-stopped network_mode: host environment: - ASPNETCORE_URLS=http://+:7210 volumes: - tscbleapi:/externalFiles - /var/run/dbus:/var/run/dbus volumes: teslamate-db: teslamate-grafana-data: mosquitto-conf: mosquitto-data: teslasolarcharger-configs: tscbleapi: ```

Install BLE API on a separate device

To set up a separate device for the BLE API, you need to install Docker on the device, like described here. Thereafter, you can use the following docker-compose.yml and start the container with docker compose up -d:

services:
  bleapi:
    image: ghcr.io/pkuehnel/teslasolarchargerbleapi:latest
    container_name: TeslaSolarChargerBleApi
    privileged: true
    restart: unless-stopped
    network_mode: host
    environment:
      - ASPNETCORE_URLS=http://+:7210
    volumes:
      - tscbleapi:/externalFiles
      - /var/run/dbus:/var/run/dbus

volumes:
  tscbleapi:

Setup BLE (same device and separate device)

After starting the BLE API, you need to add the BLE API Base URL to your TeslaSolarCharger configuration. The URL is http://<IP of device with BLE API running>:7210/

Now you can pair each car by going to the Car Settings enable "Use BLE", click Save and then click on Pair Car. Note: It could take up to three tries to pair the car. After you get a message that pairing succeeded, you can test the API by clicking on the Set to 7A. Note: The car needs to be awake during the pairing and test process.

Often used optional settings

When you are at this point, your car connected to any charging cable in your set home area should start charging based on solar power. But there are a few additional settings that are maybe helpful for your environment:

Power Buffer

If you set PowerBuffer to a value different from 0, the system uses the value as an offset. E.g., If you set 1000, the car's current is reduced as long as less than 1000 Watt power goes to the grid.

Home Battery

To configure your home battery, you need to add the following settings:

URL for getting the state of charge
URL for getting current charging/discharging power
Home Battery Minimum SoC
Home Battery Charging Power

After setting everything up, your overview page should look like this:

Note: If your battery is discharging, the power should be displayed in red. If the battery is charging, the power should be displayed in green. If this is the other way around, you must update the Correction Factor below your HomeBatteryPower Url setting and invert it to a negative number, e.g. -1.0.

Telegram integration

In this section you learn how to create the Telegram Bot Key and where you get the Telegram ChannelID from:

Create a bot by chatting with BotFather

Botfather

Ask BotFather to reate a new bot with the /newbot command and follow the instructions

newbot

Copy the Bot token as Telegram Bot Key to your TSC

BotToken

To get a chat ID, you have to chat with the userinfobot

userinfobot

Ask the bot for your UserID with the command /start

UserIDVonBot

Copy the user ID as Telegram Channel ID to your TSC

How to use

After setting everything up, you can use the software via http://your-ip-address:7190.

Charge Modes

Currently, there are four different charge modes available:

PV only: Only solar energy is used to charge. You can set a SOC level that should be reached at the specified date and time (if charge every day is enabled, the car charges to that SoC every day, not only once). If solar power is insufficient to reach the set soc level in time, the car starts charging at full speed. Note: To let this work, specify usable kWh in the car settings section.
Maximum Power: The car charges with the maximum available power
Min SoC + PV: If plugged in, the car starts charging with maximum power until the set Min SoC is reached. After that, only PV Power is used to charge the car.
Spot Price + PV: You can set a Min Soc, which should be reached at a specific date and time (if charge every day is enabled, the car charges to that SoC every day, not only once). The charge times are then planned to charge at the cheapest possible time. This is especially useful if you have hourly electricity prices like with Tibber or aWATTar. Note: The car will still charge based on Solar energy if available, and you need to enable Use Spot Price in the Charge Prices settings for correct charge price calculation.
TSC Disabled: TSC leaves this car as is and does not update the charging speed etc.

Generate logfiles

To generate logfiles, you must write each container's logs to a separate logfile. Note: To create a more detailed logfile, you must add - Serilog__MinimumLevel__Default=Verbose as environment variable. The commands if you used the docker-compose.yml files from above:
For the main TeslaSolarCharger container:

docker logs teslasolarcharger > teslasolarcharger.log

For the SmaPlugin:

docker logs teslasolarcharger_smaplugin > teslasolarcharger_smaplugin.log

For the SolaredgePlugin:

docker logs teslasolarcharger_solaredgeplugin > teslasolarcharger_solaredgeplugin.log

For the ModbusPlugin:

docker logs teslasolarcharger_modbusplugin > teslasolarcharger_modbusplugin.log

If you get an error like Error: No such container: you can look up the containernames with

docker ps

Privacy notes

As the new Tesla Fleet API requires a domain and external Token creation from version 2.23.0 onwards, TSC transfers some data to the owner of this repository. By using this software, you accept the transfer of this data. As this is open source, you can see which data is transferred. For now (4th July 2024), the following data is transferred:

Your access code is used to get the access token from Tesla (Note: the token itself is only stored locally in your TSC installation. It is only transferred via my server, but the token only exists in memory on the server itself. It is not stored in a database or log file)
Your installation ID (GUID) is at the bottom of the page. Do not post this GUID in public forums, as it is used to deliver the Tesla access token to your installation. Note: There is only a five-minute time window between requesting and providing the token using the installation ID. After these 5 minutes, all requests are blocked.)
Your installed version.
Error and warning logs
Your VIN and if using the Fleet API the data for each request (e.g. change-charging-amp to 7A)
A statistic of your Fleet API and BLE API usage (e.g. changed car amps 58 times including Timestamps of the request)
Your configuration regarding using BLE API, the configured Fleet API Refresh Interval, if getting Data from TeslaMate is enabled

pkuehnel / TeslaSolarCharger

readme

TeslaSolarCharger

Table of Contents

How to install

Docker compose

Setting up TeslaMate including TeslaSolarCharger

docker-compose.yml content

Content without using a plugin

Content using SMA plugin

Content using SolarEdge plugin

Content using Modbus plugin

Content using Solax plugin

First startup of the application

Setting Up Urls to get grid power

Using vendor specific plugins

Using the Modbus plugin

Using no plugin

JSON Path

XML Path

Correction Factors

Install and setup BLE API

Install BLE API on the same device as TSC

Install BLE API on a separate device

Setup BLE (same device and separate device)

Often used optional settings

Power Buffer

Home Battery

Telegram integration

How to use

Charge Modes

Generate logfiles

Privacy notes