Goecharger-api2 - Control your go-eCharger Wallbox directly via the API v2 [Gemini/flex, HOMEfix & other]

Share your Projects! Custom Integrations
41

Include this to avoid updates during the night:

conditions:

  • condition: and
    conditions:
    • condition: sun
      after: sunrise
    • condition: sun
      before: sunset
1 Like
42

I just have added that to the repo readme - thanks!

3 Likes
43

Hello,

I’m trying to get PV surplus charging working with my go-e Gemini charger.
I’ve installed the ha-goecharger-api2 integration in Home Assistant and enabled APIv2. The charger is reachable locally and responds to /api/status.

Here’s what I get from:

http://[IP]/api/status?filter=lmo,fup,acp,pgrid,ppv

{
  "lmo": 4,
  "fup": true,
  "acp": true,
  "pgrid": -7.22,
  "ppv": 7250.47
}

That should be correct:

  • Logic mode (lmo) is set to Eco (Awattar)
  • PV surplus mode (fup) is enabled
  • Charge pausing (acp) is enabled
  • pgrid is negative → I’m feeding ~7.2 kW into the grid
  • The charger works perfectly in normal (non-surplus) mode

However, it doesn’t start charging automatically in surplus mode.
I’m sending data to the wallbox every 5 seconds using this Home Assistant automation:

alias: PV surplus charging
triggers:
  - seconds: /5
    trigger: time_pattern
conditions:
  - condition: and
    conditions:
      - condition: sun
        after: sunrise
      - condition: sun
        before: sunset
      - condition: not
        conditions:
          - condition: state
            entity_id: sensor.goe_266304_car_value
            state: Inaktiv/Frei
actions:
  - data:
      pgrid: "{{ states('sensor.shellypro3em_08f9e0e95ddc_total_active_power')}}"
      ppv: "{{ states('sensor.shellypro3em_08f9e0e95ddc_total_apparent_power')}}"
    action: goecharger_api2.set_pv_data
mode: single

I see that pgrid and ppv arrive at the wallbox via the /api/status endpoint, but still no charging starts.

Is there something I’m missing?

Thanks a lot in advance!

44

Hi,

I did the same mistake :wink:

Your pgrid value is “-7.22” in KW, but this value needs to be “-7220” in Watt. So just multiple the value with 1000 → " *1000 " and the problem is solved.

1 Like
45

Hi, first of all thank you for the integration. I have it up and running, my next step would be to make an automation. On the Github page is a link to a Blueprint, when I want do download it, I get an error. Is something wrong, or is the Blueprint discontinued? Thanks for the feedback.

46

Hi all,
maybe a stupid question… I have just installed the API to my Home Assistant, but I am not able to see any entities on my Dashboard. It is the first time this happend but no clue why.
What I did: I configured the the extension, and added the extension to “Bereich” I think it is Area to Wallbox. Next I created a Dashboard to show only Wallbox, but it is always blank.
I checked the Bereich again and it says no entities connected but looking to the entitiy list directly it says it is connected to the area… Any Idea?

47

enable the debug log and check what output is generated during the startup

48

The Blueprint was just added few days ago… I fixed the links… Thanks for letting me know

49

Hello Matthias, thank you for the update on the blueprint!

51

First of all, @marq24 thank you for great integration. It has been game changer for optimizing the cost of charging.

I’ve built small automation that updates the awattar max threshold price to charge on cheapest hours/15 mins when I connect the charger to my car. Automation calculates time needed to charge my car to 80% and which is the minimum price to set awattar price limit to get needed hours for charging and charge on the cheapest hours/15 mins.

The API works flawlessly for full cent prices. With prices including desimals (i.e. 2.32) the full price is imported to HA if updated in go-e app. But if I set price on HA the desimals are dropped off before appearing on go-e app (2.32 → 2).

According the eco price sensor (goe_wan_xxxxxx_awp ”[go-e] Awattar maximum price threshold”) it should work with 2 decimals. Prices updated on go-e app actually land with 9 decimals to HA.

Is there a way to push desimals to awattar max price threshold via this API?

It’s not a major issue, but with my driving kilometers the savings from desimal prices could be 75e / year. More nice to have, than critical feature, but would make 15min charging optimization even more optimal.

Thank you in advance.

(I have the new go-e Core charger with SIM and max 22kWh capped to 11kWh)