Custom component goecharger_mqtt - go-eCharger HOMEfix EV charger integration

Hello. Well after testing, testing and testing. Here is my final automation.

When my inverters are on 2KW production the automation activate and send the mqtt.publish. If they are below the mqtt.publish stops.

alias: go-e Charging
description: Charging Automation
trigger:

  • platform: numeric_state
    entity_id: sensor.GRID_EXPORT
    above: 2000
  • platform: time_pattern
    seconds: ‘/5’
    condition:
  • condition: numeric_state
    entity_id: sensor.GRID_EXPORT
    below: 2000
    action:
  • service: mqtt.publish
    data:
    qos: ‘0’
    topic: go-eCharger/xxxxx/ids/set
    payload: >-
    {{‘{“pGrid”: ‘}}{{states(‘sensor.GRID_INN_OUT’)}}{{’,
    “pPv”:’}}{{states(‘sensor.SOLAR_POWER’)}}{{‘, “pAkku”:0}’}}
    retain: false

So far looks like everything works correct 1 or 3 phases.
I will check/test a few days and if all look correct I will make one pi4 only for the Charger , set it and forget it.

Thanks for your help

1 Like

@syssi , the electrician completed the electrical connections from the two go-e chargers to the house grid today.

I have setup the go-e chargers with the go-e app, run the firmware update, installed your HomeAssistant integration and

simsalabim

both chargers were added! It works like a charm.

Great!

The only missing bit now is to set up the

ids: pGrid

for excess/export power, pv power and battery power and the automation to charge in eco mode. My understanding of the documentation is a bit weak.
How and where to set this up?
Any advice you or anybody else on this community group can share would be very much appreciated!

@SteffenLav ,
can you please advise where within HomeAssistant the above code snippet needs to be added/copied so it refers to the go-e-charger integration?

My code (post) above is automation.

OK. Got it working with adding the code into two new automations (one per charger) within the yaml-editor.
That was easy when you know where to look for.

Next question:
I have an energy storage system (ESS), i.e. a battery, connected to the PV inverter.
Can I setup a minimum battery charge before the go-e chargers get priority?
Otherwise I will first charge the ESS battery in the morning and then drain it by the go-e charger.

Any advice you could share how to set the automation up that the ESS battery get charged to a certain level to enable it to act as a buffer and when the SoC % level is reached then switch the excess PV energy to charge the vehicle via the go-e chargers?

Maybe somebody else can help you on that.

At soon the charger needs only the CLEAN export power, you can make automation when to trigger the charger…after the battery is higher then %.

Sorry I got no battery here, only 738 modules on the roof.

1 Like

+700 modules???
What kind of roof is that?

Horse riding stable/hall. All most 300KW.
I use only 2 inverters from this installation just for the house -+ 30KW the rest goes straight to the Grid

1 Like

@koosoli
How would you go about setting up the evcc.yaml to use a template for the go-e Gemini charger through MQTT ? Do you have an example ?

@syssi thank you for the blueprint.
First day I have solar power exceeding the house consumption and it works like a charm.
Haven’t had enough solar power yet to see if the automatic phase switch works but I am so pleased with the functionality! Great work!

Question: at what intervals does the blueprint check the conditions to:
• change amp settings
• change phase switch
• start EV charging
• stop EV charging

Hi there,

I got this installed but in the dashboard it kind of only shows the data in rows and not in a nice overview as it does within your screenshot. What am I missing?

Thanks,

JohnnyT

Maybe you must add a screenshot…to understand what you mean by data in rows.

Can anyone tell me why Ii dont see any data from my go e chargers?
All say “Not available”…Connection is established …via mqtt…

Check the mqtt PREFIX in the app try with or without the / in the name

/go-eCharger/serial or go-eCharger/serial

Restart home assistant any time you try this change.

Hi,
thank you @syssi for the great work. And thank you all for the hints how to use this for PV surplus loading with the go-e charger.
I am really new in dealing with home assistant, but I was able to get many things working now. Not all - the go-e is not willing to charge the car at all.
I have ther following Automation in HA running:

- id: '1708376875299'
  alias: go-e PV Überschussladen
  description: Ladelogik
  trigger:
  - platform: time_pattern
    seconds: /5
  condition: []
  action:
  - service: mqtt.publish
    data:
      qos: '0'
      topic: go-eCharger/xxxxxxx/ids/set
      payload: '{{''{"pGrid": ''}}{{states(''sensor.pv_anlage_grid_power'')}}{{'',
        "pPv": ''}}{{states(''sensor.pv_anlage_sum_power_of_all_pv_dc_inputs'')}}{{'',
        "pAkku": ''}}{{states(''sensor.pv_anlage_pv_to_battery_power'')}}}'
      retain: false

That leads to an output in MQTT-explorer that looks like this (example):

In the go-e APP I activated ECO-charging:


However, the go-e is not starting to charge the EV.

What confuses me is that I can see in MQTT explorer, that the go-e says “modelStatus” = 17. According to the API, 17 = NotChargingBecauseFallbackAwattar.
May the WB does not start charging because of this. But I did not activate Awattar charging (see picture).
I have a go-e Charger V4 with FW 055.8
Does anyone have any idea what I have set incorrectly?

Thank you very much

@showup : That dashboard looks great. Would you like to share it?

If you install 56.1 it will work I believe.

Check also the go_echarger_SERIAL_pgrid entity ( You must have there the MQTT send data ( that -3307 show in your shot )

I just notice something in your code…

pv_anlage_sum_power_of_all_pv_dc_inputs

That must be the AC power ( or i got it wrong? )

{{‘{“pGrid”: ‘}}{{states(‘sensor.GRID_POWER’)}}{{’,
“pPv”:’}}{{states(‘sensor.SOLAR’)}}{{‘, “pAkku”:0}’}}

Sure at soon I will be in my PC I will send the code.

But first you must make it work. :slight_smile:

  • title: Go-E
    path: goe
    layout:
    width: 400
    max_cols: 10
    type: custom:masonry-layout
    badges:
    cards:
    • type: vertical-stack
      cards:
      • type: horizontal-stack
        cards:
        • type: gauge
          entity: sensor.grid_total
          min: -20000
          max: 20000
          needle: true
          severity:
          green: -20000
          yellow: 0
          red: 0
        • type: gauge
          entity: sensor.power_consumption
          max: 20000
          severity:
          green: 0
          yellow: 5000
          red: 12000
          needle: true
      • type: horizontal-stack
        cards:
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg
          needle: true
          severity:
          green: 210
          yellow: 240
          red: 250
          max: 280
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_2
          severity:
          green: 210
          yellow: 240
          red: 250
          needle: true
          max: 280
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_3
          max: 280
          needle: true
          severity:
          green: 210
          yellow: 240
          red: 250
      • type: horizontal-stack
        cards:
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_8
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_9
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_10
      • type: horizontal-stack
        cards:
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_5
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_6
        • type: gauge
          entity: sensor.go_echarger_SERIAL_nrg_7
      • type: entity
        entity: sensor.go_echarger_SERIAL_wh
    • type: vertical-stack
      cards:
      • type: entities
        entities:
        • entity: sensor.go_echarger_SERIAL_pgrid
        • entity: sensor.id_5_gtx_state_of_charge
        • entity: sensor.go_echarger_SERIAL_car
        • entity: binary_sensor.go_echarger_SERIAL_car
        • entity: button.go_echarger_SERIAL_frc
        • entity: button.go_echarger_SERIAL_frc_2
        • entity: button.go_echarger_SERIAL_frc_3
        • entity: select.go_echarger_SERIAL_ust
        • entity: number.go_echarger_SERIAL_amp
        • entity: button.go_echarger_SERIAL_rst
        • entity: switch.go_echarger_SERIAL_fup
      • type: horizontal-stack
        cards:
        • type: entity
          entity: sensor.go_echarger_SERIAL_rssi
        • type: entity
          entity: sensor.go_echarger_SERIAL_fwv
    • type: vertical-stack
      cards:
      • type: horizontal-stack
        cards:
        • type: entities
          entities:
          • entity: button.go_echarger_SERIAL_frc
          • entity: button.go_echarger_SERIAL_frc_2
          • entity: button.go_echarger_SERIAL_frc_3
          • entity: select.go_echarger_SERIAL_ust
          • entity: select.go_echarger_SERIAL_lmo
          • entity: number.go_echarger_SERIAL_ama
          • entity: select.go_echarger_SERIAL_psm
          • entity: number.go_echarger_SERIAL_amp
          • entity: button.go_echarger_SERIAL_rst
      • type: entity
        entity: sensor.go_echarger_SERIAL_eto
      • type: entity
        entity: sensor.bothinverterstotalpower
        name: Solar Power

Hi, I’m also confused about PV surplus charging.
Here is my setup and my test results:

go-eCharger HOMEfix 11 kW V.3
Firmware 055.8

I´m using the same Automation like @ErFi with an opposite problem.
Despite EcoMode Neutral, charging starts even though there is not enough grid-power for charging. The mqtt values are correctly sent to the wallbox:
image

Then I tested with manual mqtt values with the same result. Charging starts despite grid delivery:
image

The Eco configuration in the App is default. PV=on Awattar=off

Am I doing something wrong or do I also have to upgrade to the beta firmware? Where can I find the changelog for this?

thx!