Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Go-e Firmware 56.8 and API-v2 / PV surplus charging 5A current cap per phase #233

Closed
karliwalti opened this issue Jul 15, 2024 · 8 comments

Comments

@karliwalti
Copy link

After I updated 56.8, I observed that the PV optimized charging not longer worked properly.
In my setup (huawei PV, homeassistant with API2, go-e), the charger caps the current on each phase to max 5A. When there is enough power from PV (4.2kW), the phase switch to 3 phases works, but still only 5A on each phase. Downgrade to 56.1 did make it work again, but unfortunately the sun was then soon gone to do further tests.

Here some more details to illustrate the issue:

You can nicely see how PV did not go into car:
image
Go-e did see the surplus (so API transmits correct values), but charger did nothing:
image

L1 was limited to 5A (I did downgrade of the FW around 14:30 )
image

Settings were correct:
image
image
image

There have been no reported errors.

It does not seem to be linked to the API2 integration in HA (this is a copy of what I originally posted there marq24/ha-goecharger-api2#11 (comment)) but more likely to some firmware changes that mess with the PV surplus charging algorithm.
Would be great to have access to the FW changelog. The app does not show a changelog for 56.2 and 56.8.

The weirdest thing is that the API can only limit current to minimum of 6A number.goe_259493_ama (and mine was set to 16A), so not sure how a cap of 5A is even possible.

@peterpoetzi
Copy link
Member

Hi,

you can have a look at the grafana integration on the data export website. To access it, go to the mobile app in "Information" and click the "Download information" link on the bottom. You will get a website where you can view past charging sessions. For every charging session, you can view some graphs of the allowed current, and the actual current per phase.

The charger itself cannot signal 5A to the car. I had a look at the support data and it shows, the car was constantly given a 16A signal in that timerange. So the limit of 5A comes from the car and not from the charger.

Peter

@karliwalti
Copy link
Author

thank you for the info, did not know about this little grafana feature.

I would not have an explanation for why the car would not allow higher currents...and why after the downgrade it didnt anymore.

@erxbout
Copy link
Collaborator

erxbout commented Jul 16, 2024

Can you try again with the new firmware?

@erxbout
Copy link
Collaborator

erxbout commented Jul 23, 2024

Any kind of new information? @karliwalti

@karliwalti
Copy link
Author

I am sorry, I do not currently have a car at hand to test it.

@karliwalti
Copy link
Author

I finally got to test the configuration again. First, old firmware all worked as expected (25.8.). Updated firmware yesterday. Will keep you posted when Sun reappears ...

@karliwalti
Copy link
Author

So, finally, a sunny day....
I confirm that firmware 56.8 works again and sending API2 calls to track surplus solar is responsive. I no longer can reproduce above pattern. The 5 A per phase will remain a mystery.
Phase switching also works.

Still, the following behaviour is illogical and might be worth another ticket.

The requested current limit amp is overriding the surplus dynamics. This means, if amp is set to 6A, the charger would charge only at 1.6kW (6A on 1phase) until there is enough surplus to charge at 4.2kW (6A on 3 phases). In the surplus calculation, only the max current limit ama should be used?

@erxbout
Copy link
Collaborator

erxbout commented Sep 25, 2024

We treat the amp setting as the customer wish for charging..
While charging dynamically we factor in this wish as we limit the current to the minimum value of all the available current limits..
I do not think that we should change that or we will potentially break other customers wishes..

Please just increase the amp setting according to your wishes

@erxbout erxbout closed this as completed Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants