marq24 / ha-goecharger-api2

HA integration for go-eCharger series (V3 and higher) communicate via the HTTP API v2.0. [supporting 148 of 172 API-Keys]. Please note, that this integration is not official and not supported by the go-e developer team. This project is not affiliated with go-e.com in any way.
Apache License 2.0
12 stars 1 forks source link

ECO mode cannot be activated. #7

Open MiJo112 opened 3 weeks ago

MiJo112 commented 3 weeks ago

Checklist

Add a description

ECO mode cannot be activated. Values are transferred. Configuration is complete. Any ideas? I have checked everything several times. IMG_6715 IMG_6714

Add your DEBUG log output

2024-06-27 16:42:50.477 INFO (MainThread) [custom_components.goecharger_api2.pygoecharger_ha] going to write {'ids': '{"pGrid": -7699.0, "pPv": 8593.0, "pAkku": 0.0}'} to go-eCharger@192.168.25.124
2024-06-27 16:42:50.521 DEBUG (MainThread) [custom_components.goecharger_api2] write result: {'ids': {'pGrid': -7699.0, 'pPv': 8593.0, 'pAkku': 0.0}}
2024-06-27 16:42:51.335 DEBUG (MainThread) [custom_components.goecharger_api2.pygoecharger_ha] going to request 20 keys from go-eCharger@192.168.25.124
2024-06-27 16:42:51.378 DEBUG (MainThread) [custom_components.goecharger_api2.pygoecharger_ha] read 20 values from go-eCharger@192.168.25.124
2024-06-27 16:42:51.378 DEBUG (MainThread) [custom_components.goecharger_api2] Finished fetching goecharger_api2 data in 0.043 seconds (success: True)
marq24 commented 3 weeks ago

mhhh - so what happen, when you open (in the go-eCharder App) the Settings for the PV-Surplus charging?! I have to admit, that I can't remember if there was an additional setting option?

In the Charger-Tab I select ECO-Mode and then on the ECO-Tab I just configured the "Enable PV" ON and then just double checked, if the settings in the submenu seams to be fine...

Then (once the HA-Automation started to send data to the wallbox) the "not available" went away after a short while (less then 5 minutes)...

And the log output you shared - looks like that the automation does what it supposed to do - and the "write result" output also indicates, that the WB have no issues processing the sent data...

One thing you can verify if the WB will provide a plausible sensor.goe_[SERIAL-HERE]_lpsc_delta and sensor.goe_[SERIAL-HERE]_pvopt_averagepgrid values ?!

CjmHo commented 2 weeks ago

Hm, if my memory doesn't betray me I had the same issue. I think I configured the settings under "Flexibler Energietarif" and then I was able to switch on Eco mode. I did NOT switch on the "Flexibler Energietarif" option!

I find it a tad strange that one needs to specify "Preisgrenze", "Country", "Anbieter", "Tarif" and so on, even though the "Flexibler Energietarif" switch says "Aus" (off). Probably a bug in the go-echarger software?