Goodwe inverter support

[thibaultmol]

Do note: the defaut Goodwe integration on Home Assistant does not support manually setting charge/discharge. Only the experimental version of that integration does https://github.com/mletenay/home-assistant-goodwe-inverter

[springfall2008]

If you are willing to try it then it should be possible to configure

[Brkie]

Also intressed in support for goodwe, tell me if I can somehow help to make it possible

[gcoan]

Also intressed in support for goodwe, tell me if I can somehow help to make it possible

If you start from the template apps.yaml you'll need to work out what the input controls and services are to control your inverter/battery - to start it charging, stop charging, determine battery level, etc

see https://springfall2008.github.io/batpred/inverter-setup/#i-want-to-add-an-unsupported-inverter-to-predbat

If you get something working then we can incorporate it into the documentation.

[bpinto]

Has anyone had any success with this? I've started but there are so many configuration options on the apps.yaml that is hard to get started. 😅

It would be nice if there was a template containing the basic information we need to provide to achieve different integration levels: monitor, etc.

I believe that the home assistant integration for goodwe should be capable of providing most of the information that is needed to connect.

If anyone familiar with Predbat could assist me with a basic yaml file, that would be great! 🤗 For what is worth, this is my current attempt that isn't working yet.

Error: Inverter 0 unable to read charge window time as neither REST, charge_start_time or charge_start_hour are set

[gcoan]

I can help you get it working, reading the apps.yaml documentation (which is extraordinarily comprehensive) is a good starting point to understand what all the sensors are.

You'll really need to share full logfiles, and predbat debug files, not snippets as otherwise its extremely difficult to debug what is going on.

However from that logfile and your apps.yaml that you haven't followed the guidance I gave before about setting up apps.yaml for a new inverter type #1000 (comment)

Specifically I can see you have copied a givtcp apps.yaml (or the predbat default one), and filled in your inverter entities, which is good, but you haven't defined what inverter type you are using and the inverter capabilities so predbat assumes you have a givenergy inverter (type GE) and you haven't set the right config items for that.

Go back and follow the link above, define the inverter type (Goodwe), define its capabilities as per the documentation and then share your apps.yaml and logfile.

[bpinto]

@gcoan I appreciate your willingness to help me. :)

Go back and follow the link above, define the inverter type (Goodwe), define its capabilities as per the documentation and then share your apps.yaml and logfile.

I've done that and I have a working setup right now! 🎉 I still need to go back to the documentation and the example apps.yaml to add missing functionality as well as double check the values I have used.

For now, I only two warnings that are coming from me incorrectly assigning a sensor instead of using a number.

[gcoan]

I've done that and I have a working setup right now! 🎉

haha, its a matter of knowing what to look for, even though you provided no logs and little information .....

let us know how you get on

I did notice you made a lot of use of secret config settings, is there a reason for that? Normally we just code everything in apps.yaml and people can then adjust for their inverter if its different from the authors inverter.
Would prefer you do that when you do share the working config as it makes it easier for others to reuse

[bpinto]

I did notice you made a lot of use of secret config settings, is there a reason for that?

I am new to HA so I'm still figuring it out, my goal was to combine all of the hard-coded values in a single place so that it would be easy to know which values to change, however I think that is not a good idea in general since there are way too many hard coded values 😅

I've changed my approach to code everything in the apps.yaml file. I appreciate this type of feedback! 👍

[bpinto]

@gcoan I have gone through most of the documentation and I've updated the code with my findings. I've also managed to successfully integrate the import rate with Portuguese dynamic prices.

I'd appreciate if you could review my config in case I did something very wrong and if I'm being too conservative on the charge/discharge rates/limits.

Is there any configuration for battery health (SOH)? I couldn't find.

---

I intend to work on control mode next but I think this might be delayed since I need to understand how the goodwe integration works first.

[bpinto]

@gcoan I could use your help in this part as I'm not confident I fully understand what I have to do.

I'm working on enabling predbat on Control charge mode, you can see my code changes on this PR. I am unsure about my changes and I have a few questions that I'd hope you could help me answering them.

The inverter has the following operation mode: general, off_grid, backup, eco, eco_charge, eco_discharge. For this implementation, I intend to use general and eco_charge modes only.

These are the options I have to configure the goodwe integration:

# GoodWe Depth of discharge (on-grid) // unit_of_measurement: %
number.goodwe_depth_of_discharge_on_grid

# GoodWe Eco mode power // unit_of_measurement: %
number.goodwe_eco_mode_power

# GoodWe Eco mode SoC // unit_of_measurement: %
number.goodwe_eco_mode_soc

My potentially incorrect understanding is that number.goodwe_depth_of_discharge_on_grid is applied when the inverter is on general mode (charging disabled). And that the other two numbers are meant to be used on eco_charge mode (charging enabled).

With that, do you think the changes on the PR are enough to let predbat control the charging cycles?

---

Regarding inverter_limit value, after reading my inverter datasheet I believe its max charge rate is of 4600W? Should this value be set to 5000W or 4600W? I'm confused given there are too many reported values on the datasheet.

  # Inverter max AC limit (one per inverter). E.g for a 3.6kw inverter set to 3600
  # Set this to your actual inverter limit
  inverter_limit:
    - 5000 # Should it be 5000 or 4600?

[gcoan]

Regarding inverter_limit value, after reading my inverter datasheet I believe its max charge rate is of 4600W? Should this value be set to 5000W or 4600W? I'm confused given there are too many reported values on the datasheet.

assuming you have the first one in the data sheetGW3648D-ES, you should set inverter_limit to the max AC your inverter can generate from PV, so 4600. Battery charge/discharge limits are other config options

These are the options I have to configure the goodwe integration:

# GoodWe Depth of discharge (on-grid) // unit_of_measurement: %
number.goodwe_depth_of_discharge_on_grid

# GoodWe Eco mode power // unit_of_measurement: %
number.goodwe_eco_mode_power

# GoodWe Eco mode SoC // unit_of_measurement: %
number.goodwe_eco_mode_soc

My potentially incorrect understanding is that number.goodwe_depth_of_discharge_on_grid is applied when the inverter is on general mode (charging disabled). And that the other two numbers are meant to be used on eco_charge mode (charging enabled).

are those the only config options you have for the inverter? If so, its going to be very simple in predbat terms.

my guess from reading the names and from how other inverters work with similar names:

• number.goodwe_depth_of_discharge_on_grid controls the percentage limit the inverter is to discharge down to when force discharging the battery. In predbat terminology this would be the reserve
• number.goodwe_eco_mode_power sounds like the percentage power that the inverter uses when in eco mode. So could be the inverter charge and discharge % rate, i.e. you can limit the charge/discharge rate. In predbat this would be charge and discharge percentage
• number.goodwe_eco_mode_soc - that would be the current battery level (state of charge), its read not written to

And mode controls what the inverter does

What is recommended is that you learn what the different controls do when you manually control your inverter. Do you have an app or web portal or screen on the inverter that you can use to control the inverter mode?
What I did for my own inverter was to learn how the inverter worked by manually initiating charges and discharges in the inverter app and seeing how the inverter controls in HA changed as a result.

My guess for your inverter is:

start_charge:

• set number.goodwe_eco_mode_power to 100 (full rate charge)
• set mode to eco_charge

stop_charge:

• set mode to general

Looks like you have come to a similar conclusion about eco_mode_power controlling the charge rate.
But rather than creating a custom sensor to convert to/from watts you should be able to directly use charge_rate_percent https://springfall2008.github.io/batpred/apps-yaml/#chargedischarge-rate

you can comment all the car_charging_planned and similar stuff out of apps.yaml since you don't have an EV configured

in your config I see you have set

has_reserve_soc: False

I think you can set this to true as number.goodwe_depth_of_discharge_on_grid does that (maybe)

in your apps.yaml, it is similar to what I suggested:

  charge_start_service:
    - service: select.select_option
      entity_id: "select.goodwe_inverter_operation_mode"
      option: eco_charge
    - delay:
        seconds: 10
    - service: number.set_value
      entity_id: "number.custom_goodwe_eco_mode_power_watts"
      value: "{power}"
    - delay:
        seconds: 10
    - service: number.set_value
      entity_id: "number.goodwe_eco_mode_soc"
      value: "{target_soc}"

my guess is that eco_mode_soc was read only, obviously you need to confirm this. If it is writeable then you need to set has_target_soc to True and configure

I would recommend that you reverse the order of commands, set the soc (if you can) and the power first, before changing the mode

But actually you can make it even simpler

configure charge_limit to be number.goodwe_eco_mode_soc
https://springfall2008.github.io/batpred/apps-yaml/#schedule

and charge_rate_percent to be number.goodwe_eco_mode_power

and predbat will set these automatically, then you just need to set the mode in the control charge section

BTW the 'delay' option isn't recognised by predbat. I did propose it, and coded it up, but it wasn't needed so its not a command predbat currently recognises

getting there

[bpinto]

assuming you have the first one in the data sheetGW3648D-ES, you should set inverter_limit to the max AC your inverter can generate from PV, so 4600. Battery charge/discharge limits are other config options

Ooops, sorry, I should have been explicit about the model. Mine is the second on the data sheet, the GW5048D-ES which is labeled as a 5kW inverter.

With this information, would you mind checking again what value I should use? 🙏

are those the only config options you have for the inverter? If so, its going to be very simple in predbat terms.

Other inverters have more options, but mine is rather limited. These are all the non-sensors I could find coming from the goodwe integrator:

number.goodwe_depth_of_discharge_on_grid // %
number.goodwe_eco_mode_power // %
number.goodwe_eco_mode_soc // %
number.goodwe_fast_charging_soc // %
number.goodwe_grid_export_limit // W

select.goodwe_inverter_operation_mode // general, off_grid, backup, eco, eco_charge, eco_discharge

switch.goodwe_backup_supply // boolean
switch.goodwe_fast_charging_switch // boolean
switch.goodwe_grid_export_limit_switch // boolean

I can't see any fast charging related information on my inverter configuration (app / web app), so I haven't touched that option.

What is recommended is that you learn what the different controls do when you manually control your inverter. Do you have an app or web portal or screen on the inverter that you can use to control the inverter mode?
What I did for my own inverter was to learn how the inverter worked by manually initiating charges and discharges in the inverter app and seeing how the inverter controls in HA changed as a result.

Yes, I do have one. I have been doing the same for testing the setup. As it is, I do have predbat controlling charging of my batteries but I'm going to apply your suggestions to make the integration better and I'm going to check it's doing the right thing on my inverter app side.

has_reserve_soc: False
I think you can set this to true as number.goodwe_depth_of_discharge_on_grid does that (maybe)

If I understand what you are proposing here is that I could make these two changes:

has_reserve_soc: True
reserve: goodwe_depth_of_discharge_on_grid

Would I need to do any further changes to the configuration?

Like the number.goodwe_fast_charging_soc above I can't see this on my goodwe app either. I have seen screenshots online from other goodwe users where they have access to different information than I have on the same app. I am going to perform a firmware upgrade soon and see if that brings any new options to the inverter app. I won't try to use reserve unless that becomes an option on the inverter app.

my guess is that eco_mode_soc was read only, obviously you need to confirm this. If it is writeable then you need to set has_target_soc to True and configure

Predbat has been successfully updating that value, I see it changing to the correct value when it holds charge (e.g. 29%) and then performs a full a charge (100%). I'm going to test the charge_limit + has_target_soc combo however.

But actually you can make it even simpler

Oh that's great! I'll be testing these proposed changes today!

BTW the 'delay' option isn't recognised by predbat. I did propose it, and coded it up, but it wasn't needed so its not a command predbat currently recognises

Oh 😅 good to know! Thanks to your proposal above I don't actually need any of that anymore :)