yeah, charger subscribed to broker and i can see topic go-eCharger/123456/acu for example.
Topics also get updates every second.
I double-checked the default topic, that was /go-eCharger, removed the “/” from the start and it seems to work now. Thanks for help!
I don’t remember if I had to remove that also with home -version of this charger.
I have extactly the same problem as Thomas had, MQTT communication is working well but the data ist not shown in HA. Micheal, you have solved it by adding a leading slash th the prefix (e.g. /go-eCharger/020152) in the go-e App, but in my go-e App version I have no possibility to enter a prefix … see picture
EDIT: SOLVED IT MY SELF 
Guys - a little push would be much appreciated
At last I decided to implement the “new” much sleeker and simpler automation. Kudos to @syssi for bringing it this far!
I have perfect mqtt response and see all relevant sensors (total solar power and excess power for charging) in my HA panel. All good. But when I add the automation to my automations.yaml like this:
- id: '1686517196184'
alias: go-e Surplus Charging
description: ''
trigger:
- platform: time_pattern
seconds: /5
condition: []
action:
- service: mqtt.publish
data:
qos: 0
retain: false
topic: go-eCharger/097828/ids/set
payload: {{'{"pGrid": '}}{{states('sensor.total_available_for_charging')}}{{', "pPv":'}}{{states('sensor.smappee_1107000182_local_total_production_active_power')}}{{', "pAkku":0}'}}
mode: single
Then I get the following indentation error and can’t get rid of it for the life of me:
bad indentation of a mapping entry (196:32)
193 | qos: 0
194 | retain: false
195 | topic: go-eCharger/097828/ids/set
196 | payload: {{'{"pGrid": '}}{{states('sensor.total_availabl ...
--------------------------------------^
197 | mode: single
198 | - id: '1688104739643'
If I then save my automations.yaml file anyway and try to restart HA then the configuration.yaml loading gives the following error:
Error loading /config/configuration.yaml: while parsing a block mapping
in "/config/automations.yaml", line 193, column 7
expected <block end>, but found '{'
in "/config/automations.yaml", line 196, column 32
Any clues anybody?
EDIT:
So found the right formatting of payload to be:
- id: '1686517196184'
alias: go-e Surplus Charging
description: ''
trigger:
- platform: time_pattern
seconds: /5
condition: []
action:
- service: mqtt.publish
data:
qos: '0'
topic: go-eCharger/097828/ids/set
payload: '{{''{"pGrid": ''}}{{states(''sensor.totalgrid'')}}{{'', "pPv": ''}}{{states(''sensor.totalsolar'')}}{{'',"pAkku":0}''}}'
retain: false
Hi.
I have a problem with charging the vehicle with three phases.
I have the charging current limit set like this:
Maximum current limit - 16A
Requested current - 16A
When charging the overproduction of energy by the solar system with one phase, the current rightly reaches 16A, and still exports energy to the grid from two unloaded phases (3.6kW).
When overproduction is greater, the go-eCharger switches to three-phase charging, but splits the maximum current into three phases, and charges roughly 6A per phase, and still exports to the grid (3kW).
Shouldn’t the energy limit apply to charging with three phases of each phase separately?
Hi,
i tried the approach but even the Mode is set to ECO with Surplus Charging the device loads with more than what is reported in the pGrid. All three phases are loading with 3+kWh even only 1.3kWh is reported. The charger also does not stop after the surplus drops below the minimum threshold.
Any ideas what is wrong?
Hello,
is it possible to set the eco mode threshold via HO?
Hi, I tried to configure, but got the following message in the mosqiuto log:
2023-09-24 13:19:30: New connection from 192.168.178.147:56172 on port 1883.
error: received null username or password for unpwd check
2023-09-24 13:19:30: Client go-echarger_212162 disconnected, not authorised.
Where is my mistake? What do I have to change?
Thx for help
Hi, have you managed to publish a mqtt setting frc state to charging ? I’m also using EVCC but i would like that my EVCC setup is not dependent on E-go Custom component.
My automation for setting CarConnected looks like this
alias: Set connected state
trigger:
- platform: mqtt
topic: go-eCharger/210283/car
action:
- choose:
- conditions:
- condition: template
value_template: "{{ trigger.payload in ['3', '4', '5'] }}"
- condition: template
value_template: "{{ is_state('switch.ev_smart_charging_ev_connected', 'off') }}"
sequence:
- service: switch.turn_on
target:
entity_id: switch.ev_smart_charging_ev_connected
data: {}
- choose:
- conditions:
- condition: template
value_template: "{{ trigger.payload in ['0', '1', '5'] }}"
- condition: template
value_template: "{{ is_state('switch.ev_smart_charging_ev_connected', 'on') }}"
sequence:
- service: switch.turn_off
target:
entity_id: switch.ev_smart_charging_ev_connected
data: {}
Figured it out by snooping what goecharger_mqtt sends :
alias: EV Smart Charging - Start
description: ""
trigger:
- platform: state
entity_id:
- sensor.ev_smart_charging_charging
from: "off"
to: "on"
action:
- service: mqtt.publish
data:
topic: go-eCharger/210283/frc/set
payload: "2"
qos: "0"
retain: true
enabled: true
mode: single
Hallo @syssi ,
Thank you for your effort to set this integration up.
I read through the entire post. It reads very well.
I still have a question: Does your integration allow for more than one go-e charger to be controlled via the integration within Homeassistant?
I have two chargers connected to each other (well, basically not yet but they already mounted to the wall only waiting for the electrician to connect them to the house electricity net.) with load management etc. and a PV solar system. I’d like to provide the two chargers with the PV excess energy and depending on the EV connection status charge only one vehicle or share the engergy between the two.
Will this work with the integration?
There is no limitation. You can add as many chargers as you like.
Hallo @syssi
I need your advice/help please.
I have installed ( MQTT etc ) now I can see : 1 device 109 entities but all are Unavailable
The MQTT looks like is working correct. When I start listening It receive messages from the charger
Message 334 received on /go-eCharger/avgfhz at 10:45 AM:
49.99420166
QoS: 0 - Retain: false
Message 332 received on /go-eCharger/nrg at 10:45 AM:
[234,233,233,0,0,0,0,0,0,0,0,0,0,0,0,0]
P.S. Charger is V3 firmware 56.1 -Home assistant Core 2024.1.5 , Supervisor 023.12.1
Operating System 11.4 , Frontend 20240104.0
Thanks in advance
Do you have a Linux host and are you able to use mosquitto_sub to record a bunch of MQTT messages? I would like to reproduce the issue locally by replaying your recording.
All are in pi4 if that is your question. 
I got the same issue as here Go-e Integration stopped providing entities although provided via MQTT · Issue #123 · syssi/homeassistant-goecharger-mqtt · GitHub
I can see in the mqtt server logs that the device is correctly registered but all entities are created as “unavailable”.
Hello
I encountered the same issue. When adding a leading slash to the go-echarger Prefix in the App I finally was receiving all the data.
@syssi: Thanks a lot for the great integration and support. It took me some attempts but finally while carefully reading through the posts I could make it running. Just fantastic work syssi, well done! Also thank a lot for adding the additional buttons to start / stop the charger!
Just for your info.
I have uninstall everything and installed again. Was not working.
I downgrade the charger firmware to 55.7. Was not working.
I just upgrade the firmware to 56.1 ( latest ) again and now all is working.
Have anyone an idea what was that?
Sure. How can I get the code?
I just got this from the dashboard
title: Go-E
path: goe
layout:
width: 400
max_cols: 10
type: custom:masonry-layout
badges:
Hi. Can you please give me your setup structure?
I got my meters, I got perfect mqtt readings, I can’t make it charge with solar. Something I do wrong.
@showup when you select the dashboard and press top right three dot menu and select raw configuration editor and copy the code in here.
Ok. At soon I’m back home I will post it.
