Changing mode on GoodWe ES Inverter is successful but results in incorrect inverter behaviour

metandesaneGit commented 11 months ago

The problem

With ES Inverter, GW5048D-ES, since the update to inverter firmware version 2525J, changing the Inverter Operation Mode through the Integration results in the inverter reporting the correct mode, but displaying the incorrect behavior. The following sequence of events highlights the issue.

While Inverter is connected to the Grid, and in General Mode:

Using SolarGo app on local network, change the Inverter Mode to Backup. Result: In SolarGo app, Inverter mode is reported as Backup. In SEMS App, Inverter Mode is reported as Backup. In Home Assistant, Inverter Mode is reported as Backup. -- Inverter charges the battery from the Grid.

Revert Inverter to General Mode

Using SEMS app, through the cloud, change the Inverter Mode to Backup Result: In SolarGo app, Inverter mode is reported as Backup. In SEMS App, Inverter Mode is reported as Backup. In Home Assistant, Inverter Mode is reported as Backup. -- Inverter charges the battery from the Grid.

Revert Inverter to General Mode

In Home Assistant, change the Inverter Mode to Backup. Result: In SolarGo app, Inverter mode is reported as Backup. In SEMS App, Inverter Mode is reported as Backup. In Home Assistant, Inverter Mode is reported as Backup. -- Inverter will not charge the battery from the Grid.

The same sequence can be repeated for Eco Mode, with the same results: changing the parameters in HA results in the correct mode but not the correct behaviour from the Inverter. All other methods of changing the mode, excluding HA, results in the correct behaviour - batteries charge from the grid.

No errors are reported in the logs (Debug Logs enabled) of the Integration when changing modes.

What version of Home Assistant Core has the issue?

core-2023.11.3

What was the last working version of Home Assistant Core?

core-2023.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

GoodWe

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_2023-11-24T08-01-22.506Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No errors besides those relating to a custom template that recieves an Unavailable result when expecting a float. This is an error in my config and unrelated to the reported behaviour.

Additional information

I am a developer (not python, but I can learn) and am willing to run debug steps on my side to find the issue. I suspect that there is a control code that is sent to the inverter over UDP that used to be a single code but is now a combination thereof in the new firmware. I am happy to run WireShark or some other sniffer to intercept the working command from SolarGo to see what has changed, but will require guidance from mletenay to set this up correctly.

home-assistant[bot] commented 11 months ago

Hey there @mletenay, @starkillerog, mind taking a look at this issue as it has been labeled with an integration (goodwe) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `goodwe` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign goodwe` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

goodwe documentation goodwe source _{^{(message by IssueLinks)}}

issue-triage-workflows[bot] commented 8 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / core