Solar Configurations

[pkuehnel]

Use this discussion to show your modbus configurations.

[giss69]

Huawei SUN2000 10ktl M1

http://modbusplugin/api/Modbus/GetValue?unitIdentifier=1&startingAddress=37113&quantity=2&ipAddress=inverterLocIP &port=502&factor=1&connectDelaySeconds=1&timeoutSeconds=10

[AlexanderTreptow]

Hey, where do I enter this link? Within the Tesla Solar Charger Base Configuration, I can only add a new Modbus TCP source, using the form. Can someone support with the correct values, please?

[LisaSimpson22]

After a SD-card problem (no backup) on my raspberry pi I had to rebuild after 14 month everything again ;-(
here for all Huaweians my modbus TCP config that works for Huawei Sun2000 3.68 KTL-L1 👍🏻

[VinciSC]

Kostal Plenticore+ 10 (w/ KSEM Kostal Smart Energy Meter & BYD HVS):

Grid Power Url :
http://modbusplugin/api/Modbus/GetFloatValue?unitIdentifier=71&startingAddress=252&quantity=2&ipAddress=inverterLocalIP&port=1502&connectDelaySeconds=1&timeoutSeconds=10

• uncheck Use Modbus Url Creation Tool as it generates URL for integer values but Kostal returns float
• set Correction Factor to -1.0
• replace InverterLocalIP with the according IP in your network (applies for all Url's given here)

HomeBatterySoc Url :
http://modbusplugin/api/Modbus/GetInt16Value?unitIdentifier=71&startingAddress=514&quantity=1&ipAddress=InverterLocalIP&port=1502&connectDelaySeconds=1&timeoutSeconds=10

• set Correction Factor to 1.0

HomeBatteryPower Url :
http://modbusplugin/api/Modbus/GetInt16Value?unitIdentifier=71&startingAddress=582&quantity=1&ipAddress=InverterLocalIP&port=1502&connectDelaySeconds=1&timeoutSeconds=10

• set Correction Factor to -1.0

Inverter Power Url :
http://modbusplugin/api/Modbus/GetFloatValue?unitIdentifier=71&startingAddress=1066&quantity=2&ipAddress=InverterLocalIP&port=1502&connectDelaySeconds=1&timeoutSeconds=10

• set Correction Factor to 1.0

[mrks1337]

Huawei SUN2000-5KTL-M1 Inverter & LUNA2000 Battery.

Grid Power:

• URL: http://modbusplugin/api/Modbus/GetInt32Value?unitIdentifier=1&startingAddress=37113&quantity=2&ipAddress=InverterLocIP&port=502&connectDelaySeconds=1&timeoutSeconds=10

HomeBatterySoc:

• URL: http://modbusplugin/api/Modbus/GetInt16Value?unitIdentifier=1&startingAddress=37004&quantity=1&ipAddress=InverterLocIP&port=502&connectDelaySeconds=1&timeoutSeconds=10
• Correction Factor: 0.1

HomeBatteryPower:

• URL: http://modbusplugin/api/Modbus/GetInt32Value?unitIdentifier=1&startingAddress=37001&quantity=2&ipAddress=InverterLocIP&port=502&connectDelaySeconds=1&timeoutSeconds=10

Inverter Power:

• URL: http://modbusplugin/api/Modbus/GetInt32Value?unitIdentifier=1&startingAddress=32064&quantity=2&ipAddress=InverterLocIP&port=502&connectDelaySeconds=1&timeoutSeconds=10

[pkuehnel]

At the bottom of this Screenshot TSC says. Car will start charging when the following conditions are met. What is displayed below that? Should be a list of reasons why the car is not charging.

[LisaSimpson22]

There ist only one bullet point mentioned:

• Enough solar power for at least 5 minutes

After waiting 5-7min. or more nothing happens…. Charging still don’t start 🤷‍♂️

[pkuehnel]

Then probably a bug. Set what your inverter produces as Grid Power and add another Rest Configuration. Enter the following as the URL: http://teslasolarcharger/api/Index/GetPvValues. Do not make any changes to the URL, like adding your IP or anything else—this exact URL works. Then set Node Pattern Type to JSON, Used For to Grid, Node Pattern to $.carCombinedChargingPowerAtHome, and Operator to Minus. This way, it takes your PV production as surplus but subtracts the charging speed of all cars.

Here's a screenshot:

[pkuehnel]

If that is the solution, open an issue that charging only based on inverter power is not working anymore.

[LisaSimpson22]

Many thanks 🙏 for your super workaround, immediately my model 3 waked up for charging with 1A before sunset and stopped with less then 230W PV only 😃👍🏻

I will open tomorrow an issue, thx again & regards

[venyosdh]

E3/DC S10E (should work with other E3/DC hardware too)

Add following to the existing docker-compose.yml (same as TeslaMate and TeslaSolarcharger is in, before "volumes:" - block, this also downloads and runs https://github.com/vchrisb/e3dc-rest because E3/DC modbus would need weird calculation of grid and Home Battery Power. Also activate Modbus in Smart Functions - Smart Home - Modbus in E3/DC.

  e3dc:
    image: vchrisb/e3dc-rest
    restart: unless-stopped
    environment:
      - E3DC_IP_ADDRESS=ipAddress ##IP Address of E3/DC found here: System -  Network
      - [email protected] ## Username of E3/DC portal
      - E3DC_PASSWORD=password ## Password of E3/DC portal
      - E3DC_KEY=rscppassword ## RSCP Password you can set (choose freely) in E3/DC: Personalization - User Profile
      - ADMIN_PASSWORD=password ## choose freely, used for access to https://github.com/vchrisb/e3dc-rest

Grid

Source: Rest
Result Type: JSON
Grid Power Url: http://e3dc:8080/api/poll
Add Header:
Key: Authorization
Value: convert your ADMIN_PASSWORD using e.g. https://www.blitter.se/utils/basic-authentication-header-generator/ , fill in "admin" as Username and your ADMIN_PASSWORD in Password and paste everything starting from "Basic" into value, including Basic

Grid Power Json Pattern: $.production.grid
Correction Factor: -1.0

HomeBatterySoc:

Same as Grid but

Home Battery SoC Json Pattern: $.stateOfCharge
Correction Factor 1.0

HomeBatteryPower:

Same as Grid but

Home Battery Power Json Pattern: $.consumption.battery
Correction Factor 1.0

Inverter Power:

Same as Grid but

Inverter Power Json Pattern: $.production.solar
Correction Factor 1.0

[GOLDIdeluxe]

Thank you very much! I have one addition, where i struggled: When converting the password, you have to fill in the user "admin" as well; otherwise it won't work.

[venyosdh]

Thank you, I edited that 👍 If you know what to do so Raspberry Pi and E3/DC do not change IP when restarting router please share that information, thank you!

[GOLDIdeluxe]

There are 2 solutions for the IP issue:

1. You can configure your routers DHCP to not change the IP for these two devices (depends on the router-model whether that works)
2. You disable DHCP for these two devices and configure them for static IP use. I recommend using an IP outside the DHCP range. On the Pi that works by editing the /etc/network/interfaces file (good tutorials can be found online). The config for the E3/DC is very easy and can be done via display. Just go to settings -> network. Disable DHCP, enter the IP you want to use, subnet mask is usually 255.255.255.0, gateway and dns-server is usually the IP of your router.

[pkuehnel]

@venyosdh I just updated your post as calling IP of raspi : 8080 does not work if you have no open port for the e3dc container. But as e3dc and teslasolarcharger are in the same docker-compose.yml teslasolarcharger can access e3dc over its service name, so no need to open a port.

[donatasnicequestion]

Goodwe Inverter using Home Assistant Integration as a provider

Home Assistant provides REST API to access a sensor values. Sensor values for Goodwe Inverter are provided by installing Goodwe Integration for Home Assistant. The "Source" REST of TSC can be used to get a values for Grid Power, Home Battery and Inverter.

Tested with Goodwe Hybrid Inverter GW8K-ET - should work also with a Goodwe models supported by Goodwe Integration

Prerequisites: Home Assistant is running, Goodwe Integration is configured, Tesla Solar Charger is running and a Car is configured in TSC.

TSC Base Configuration

The same values for all configurations

Source: REST
Headers
   Key: Authorization Value: Bearer <put a value of long living token to access the API of Home Assistant> 
Result Type: JSON
Json Pattern: $.state

Values specific to configuration of

Grid Power

Grid Power Url: http://<ip  of home assistant>:8123/api/states/sensor.active_power
Grid Power Correction Factor: 1,0

Home Battery

Home Battery SoC Url: http://<ip  of home assistant>:8123/api/states/sensor.battery_state_of_charge
Home Battery Power: http://<ip  of home assistant>:8123/api/states/sensor.battery_power
Home Battery Correction Factor: -1,0

Inverter

Inverter Power Url: http://<ip  of home assistant>:8123/api/states/sensor.pv_power
Inverter Correction Factor: 1,0

Once configured the TSC shows the values like this on an Overview screen:

The Value of Power Buffer -1000 W is an example - set it according to documentation of TSC and your needs.

[SebastianGode]

Growatt Inverters using Grott and HomeAssistant

Step 1: Install Grott

You will need to install Grott, preferably using Docker: This is an example docker-compose file. You can also add the service to the existing one of TeslaSolarCharger.

version: '3.3'
services:
    grott:
        network_mode: host
        image: ledidobe/grott:2.8.2
        container_name: grott
        restart: unless-stopped
        environment:
            - TZ=Europe/Amsterdam
            - gnomqtt=False
            - ginvtype=sph

Change the value for ginvtype accordingly. I have got an hybrid inverter of the SPH series.

Once Grott is running make sure that your ShineWifi module (the Wifi Stick which is plugged into the inverter) can access your server. Either by redirecting port 5279 to it or by simply having the server in your home network.

---

Step 2: Configure your ShineWifi Module

Now comes the hard part: You need to configure your ShineWifi module to send all the data to your server instead of the Growatt cloud. Don't worry, grott by default will redirect it again to the Growatt cloud, so you will still be able to use their website and app.

To configure your module you will need to factory reset it. To do this hold the button on it for 6-7s until all the 3 colored lights turn on. Then immediately let go of the button again. After that remove the ShineWifi adapter from your app. To do this click on the inverter in the middle of your energy overview and swipe left on your datalogger. Once that is done start to add a new datalogger again. As setup method use Hotspot mode. In the menu where it asks you to input your wifi credentials select advanced settings. There you need to change the target server from server.growatt.com to your local IP/DNS name where grott runs. Also change the data update interval down from 5 minutes to 1 minute. The adminstrator password you will need is growatt<Date>, so for example: growatt20231105 if you do this on the 5th November 2023. After you have changed the two settings go back, enter your wifi credentials and everything is working already.

You can get the current inverter statistics by listening to the energy/growatt MQTT topic on your MQTT server.
An example output would be this:

{
  "device": "<SerialNumber>",
  "time": "2023-11-04T15:29:02",
  "buffered": "no",
  "values": {
    "datalogserial": "<SerialNumber>",
    "pvserial": "<SerialNumber>",
    "pvstatus": 5,
    "pvpowerin": 13574,
    "pv1voltage": 4145,
    "pv1current": 17,
    "pv1watt": 7250,
    "pv2voltage": 3533,
    "pv2current": 17,
    "pv2watt": 6324,
    "pvpowerout": 0,
    "pvfrequentie": 5000,
    "pvgridvoltage": 4046,
    "pvgridcurrent": 6,
    "pvgridpower": 4453,
    "pvgridvoltage2": 4072,
    "pvgridcurrent2": 6,
    "pvgridpower2": 0,
    "pvgridvoltage3": 4064,
    "pvgridcurrent3": 6,
    "pvgridpower3": 0,
    "totworktime": 337054,
    "eactoday": 2,
    "pvenergytoday": 2,
    "eactotal": 312,
    "epvtotal": 402,
    "epv1today": 5,
    "epv1total": 210,
    "epv2today": 4,
    "epv2total": 192,
    "pvtemperature": 268,
    "pvipmtemperature": 282,
    "pvboosttemp": 284,
    "bat_dsp": 2177,
    "eacharge_today": 5,
    "eacharge_total": 24,
    "batterytype": 1,
    "uwsysworkmode": 5,
    "systemfaultword0": 0,
    "systemfaultword1": 0,
    "systemfaultword2": 0,
    "systemfaultword3": 0,
    "systemfaultword4": 0,
    "systemfaultword5": 0,
    "systemfaultword6": 0,
    "systemfaultword7": 0,
    "pdischarge1": 0,
    "p1charge1": 12200,
    "vbat": 2177,
    "SOC": 80,
    "pactouserr": 0,
    "pactousertot": 0,
    "pactogridr": 0,
    "pactogridtot": 0,
    "plocaloadr": 1300,
    "plocaloadtot": 1300,
    "spdspstatus": 5,
    "spbusvolt": 7154,
    "etouser_tod": 0,
    "etouser_tot": 4,
    "etogrid_tod": 1,
    "etogrid_tot": 184,
    "edischarge1_tod": 7,
    "edischarge1_tot": 43,
    "eharge1_tod": 9,
    "eharge1_tot": 79,
    "elocalload_tod": 9,
    "elocalload_tot": 190
  }
}

---

Step 3: Configure HomeAssistant for calculations

As you might see Growatt doesn't provide total values for Gridpower or Batterypower. Only separate ones: pactousertot and pactogridtot for the Gridpower as well as p1charge1 and pdischarge1 for the Batterypower.
We will now use HomeAssistant to subtract those values so that TeslaSolarCharger will get one value which is negative or positive.
To do this add the MQTT extension to HA and then configure it in a config file:

mqtt:
  sensor:
    - name: "Growatt Gridpower"
      unique_id: "growatt_grid_powertotal"
      state_topic: "energy/growatt"
      value_template: '{{ ((value_json["values"]["pactogridtot"] - value_json["values"]["pactousertot"]) * 0.1)| int }}'
      unit_of_measurement: "W"
      state_class: measurement
      device_class: power

    - name: "Growatt Batterypower"
      unique_id: "growatt_battery_powertotal"
      state_topic: "energy/growatt"
      value_template: '{{ ((value_json["values"]["p1charge1"] - value_json["values"]["pdischarge1"]) * 0.1)| int }}'
      unit_of_measurement: "W"
      state_class: measurement
      device_class: power

    - name: "Growatt Battery SoC"
      unique_id: "growatt_battery_soc"
      state_topic: "energy/growatt"
      value_template: '{{ value_json["values"]["SOC"] }}'

You can also add the Inverter power by using pvpowerin as value if you want or you can leave that away and query it directly with MQTT on TSC.
In your user settings in HomeAssistant obtain a long-lived access token which you will need to configure TSC later. Save it as it will be only shown once.

---

Step 4: Configure TeslaSolarCharger

Configuring TSC now is very simple.
For Gridpower select REST and use the URL http://<localIp:port>/api/states/sensor.growatt_gridpower. You will need to replace your local-IP of the HA installation. Add a header with the key Authorization and the value Bearer <yourToken>. Replace the token accordingly. Then select JSON as result type and use $.state as pattern.
You can use the exact same values for each field in Batterypower, SoC and co. Just change the URLs:

http://<localIp:port>/api/states/sensor.growatt_battery_soc
http://<localIp:port>/api/states/sensor.growatt_batterypower

[AMichaelSuess]

Solaredge Inverters using SolarEdge Modbus Multi-Plugin via Modbus TCP and HomeAssistant

Prerequisites

• you need to have Home Assistant installed and running (I have used Home Assistant OS on a Raspberry Pi 4 in the 4GB version)
• you need TSC installed and running (I have installed it on the same device using the Portainer HA Community Add-On)
• you need the SolarEdge Modbus Multi-Plugin installed using one of the methods described on the linked page (I have used HACS). There is an alternative plugin SolarEdge Modbus - which will probably also work, but which I have not tried, as the former one appeared more actively developed

Step 1: Enable Modbus on your inverter

You need your inverter to expose its data via Modbus. There is a very extensive documentation on how to do this in the configuration-page of the plugin. There is also an alternative that worked for me: I just contacted the Solaredge support via WhatsApp and asked them to enable Modbus TCP for my inverter - and share back the unit ID and port. After a short conversation, they enabled it remotely. Be careful: for some inverters and some firmware versions, you need your inverter to be connected via LAN to your router - WiFi will NOT expose the Modbus protocol.

Step 2: Configure the Solaredge Modbus Multi Plugin

This is also well-described on the Plugin-page. I have set the update interval to 30 seconds instead of the default 5 minutes for a bit more snappy readouts. If you have a home-battery like I do and want to use it in TSC, make sure to enable Auto Detect Batteries, so the corresponding sensors show up in Home Assistant.

After you have done this successfully, a lot of new sensors provided by the plugin should show up in your HA-installation - for example in your main dashboard.

Step 3: Add a new custom sensor for Solar Production

Solaredge has a strange way to report current solar production via their UI - and also via Modbus. The plugin just passes through those values - so we need to add a custom sensor to our HA-configuration in order to calculate the current power coming from your panels right now in the way that TSC expects it. Therefore, add this to your configuration.yaml-file from Home Assistant (shamelessly stolen from this repository, which contains the code for the nice dashboard discussed here):

template:
  - sensor:
      - name: "Solar Panel Production W"
        unit_of_measurement: "W"
        icon: mdi:solar-power
        state: >
          {% set i1_dc_power = states('sensor.solaredge_i1_dc_power') | float(0) %}
          {% set b1_dc_power = states('sensor.solaredge_b1_dc_power') | float(0) %}

          {% if (is_state('sensor.solaredge_i1_dc_power', 'unknown') or is_state('sensor.solaredge_b1_dc_power', 'unknown')) %}
            0
          {% elif (i1_dc_power + b1_dc_power <= 0) %}
            0
          {% else %}
            {{ (i1_dc_power + b1_dc_power) }}
          {% endif %}
        availability: >
          {{ states('sensor.solaredge_i1_dc_power') | is_number and states('sensor.solaredge_i1_ac_power') | is_number and states('sensor.solaredge_b1_dc_power') | is_number }}

Make sure to read in your configuration again in Home Assistant afterwards for the changes to become effective.

Step 4: Configure TeslaSolarCharger

This is heavily inspired by Sebastians Step 4 above - as it basically works the same way. For every value in the BaseConfiguration, do the following:

• select REST
• use a URL from the list below
• Add a header with the key Authorization and the value Bearer <yourToken>. Replace the token accordingly with one from your Home Assistant user configuration
• result type is JSON
• Json Pattern is always $.state
• I did not need any correction factors - but your mileage may vary

And finally the actual URL's to use:

• Grid Power Url: http://<localIp:port>/api/states/sensor.solaredge_m1_ac_power
• Home Battery SoC Url: http://<localIp:port>/api/states/sensor.solaredge_b1_state_of_energy
• Home Battery Power Url: http://<localIp:port>/api/states/sensor.solaredge_b1_dc_power
• Inverter Power Url: http://<localIp:port>/api/states/sensor.solar_panel_production_w

Step 5: Enjoy your installation and happy charging!

[StoinernerMa]

Query Solinteg inverters via modbus TCP (pylontec battery)

Hi, here are settings for Solinteg Inverters (www.solinteg.com). Note: according to the manufacturer not every older inverter supports modbus, so don't put too much effort in before being sure that your inverter is modbus capable (a firmware update from solinteg may be necessary). You probably need the LAN module, WLAN is not supposed to work. Best thing to do: try out the swagger-ui on http://MYHOSTNAME:7191/swagger/index.html as suggested in the solarcharger documentation, this is an example for the battery power:

Thanks to solinteg support for assistance. All result types are "direct". Replace hostname and IP as appropriate. Inverter power and battery SOC are unsigned int, grid power and battery power are signed int.

• Grid Power url: http://MYHOSTNAME:7191/api/Modbus/GetTypedValue?unitIdentifier=255&startingAddress=11000&quantity=2&ipAddress=192.168.0.49&port=502&connectDelaySeconds=1&timeoutSeconds=10&modbusValueType=int&modbusRegisterType=holdingRegister&registerSwap=false
  factor=1.0

• Home Battery SOC url: http://MYHOSTNAME:7191/api/Modbus/GetTypedValue?unitIdentifier=255&startingAddress=33000&quantity=1&ipAddress=192.168.0.49&port=502&connectDelaySeconds=1&timeoutSeconds=10&modbusValueType=uShort&modbusRegisterType=holdingRegister&registerSwap=false
  factor=0.01

• Home Battery Power url: http://MYHOSTNAME:7191/api/Modbus/GetTypedValue?unitIdentifier=255&startingAddress=30258&quantity=2&ipAddress=192.168.0.49&port=502&connectDelaySeconds=1&timeoutSeconds=10&modbusValueType=int&modbusRegisterType=holdingRegister&registerSwap=false
  factor=-1.0

• Inverter power url: http://MYHOSTNAME:7191/api/Modbus/GetTypedValue?unitIdentifier=255&startingAddress=11028&quantity=2&ipAddress=192.168.0.49&port=502&connectDelaySeconds=1&timeoutSeconds=10&modbusValueType=uInt&modbusRegisterType=holdingRegister&registerSwap=false
  factor=1.0

Enjoy!

[StoinernerMa]

And here is the configuration for the new modbus plugin... of course you must change the ip :)

[AlexanderTreptow]

Thank you very much. I changed the IP and used all the other values, but still:

Any ideas? Modbus is activated "unrestricted".

Regards,
Alex

[StoinernerMa]

Hi Alex, what inverter do you have? Your first post was at the Huawei inverter, hopefully you weren't misled by my update regarding Solinteg inverters.

[AlexanderTreptow]

Hey, that‘s it. I red Huawei anywhere 🙈

[cpav1978]

Peak: 11.86 kWp
Inverter: Fronius symo Gen 24 10 plus + SmartMeter 65A
Storage: BYD 10kW
Synology NAS - Docker

Please enter your IP accordingly instead. API must still be activated in the Fronius WR. To do this, log in as a customer and activate API under Communication / Solar. Yes, ModBus is certainly better, but this requires the technician PW, which I first have to get or don't even know if I can get.

Status:

Smartmeter Data:

Battery:

Inverter Data:

Grid:
http://192.168.178.61/solar_api/v1/GetMeterRealtimeData.cgi?Scope=Device&DeviceId=0&DataCollection=MeterRealtimeData
$.Body.Data.PowerReal_P_Sum
Battery:
http://192.168.178.61/solar_api/v1/GetPowerFlowRealtimeData.fcgi
$.Body.Data.Inverters.1.SOC
http://192.168.178.61/solar_api/v1/GetPowerFlowRealtimeData.fcgi
$.Body.Data.Site.P_Akku
Inverter:
http://192.168.178.61/solar_api/v1/GetPowerFlowRealtimeData.fcgi
$.Body.Data.Site.P_PV

Patrick, thank you very much for your time and effort. The donation has just gone out!

[jbuchner]

Tesla Powerwall

To integrate the Tesla Powerwall you can use the Powerwall plugin for TeslaSolarCharger.

Follow the instructions on https://github.com/jbuchner/pwgateway

All values required by the TeslaSolarCharger can be retrieved via this plugin.

[axemo]

Configuration for Sungrow Inverter

Configured on TSC 2.28.3 and tested with SH8.0RT and SH10.0RT. It shouldn't matter which battery you use

Requirements:
Modbus connection to your Inverter

Setup:
In TSC open "Base Settings" and "Add new Modbus source" and click on "+ Add Result" for each entry
The final result should look like this:

General Settings:

Inverter Power:

Grid Power:

HomeBatterySoC

HomeBatteryPower
For correct display of the battery power you need two entries. The bool entry defines if the battery is charging or discharging. Additional entries under "advanced Settings" are not required.

[ptar]

Home Battery Configuration for SH20T

• Most probably for SH15T and SH25T as well
  

• With this inverter, battery current is a signed 16-Bit value, so we could use the highest bit (=bit 15) of it to invert the battery power.
  

(In a previous version of this post, bit 0 was inadvertently shown in the screenshot!)

[ptar]

I fixed the screenshot above, because I was wrong about the bit numbering: The sign is bit 15 in a signed 16-bit value, not bit 0!

[sftman18]

Configuration for eGauge EG3010

I enabled the Modbus Server in the settings page: http://<local IP>/66A51/settings.html
The "View Modbus Map" option showed me the 2 addresses I needed:

Address	|	Name		| Description		| Type	| Denominator 	| Unit
36002	|	Generation	| change in value 	| f32	|	1	| W
39000	|	Grid		| change in value 	| f32	| 	1	| W

Through trial and error I discovered that I needed to drop the leading "3" on the addresses above.
In the TSC "Base Configuration" page, I selected a new "Modbus TCP Source"


That configuration allowed TSC to see my eGauge values and operate successfully!