I got also this charger… with Beta 56.1 all is working correct…But…I just use the POWER FROM GRID (ids)_where I just send the Grid Status ( from the MQTT ) . In your screenshots Is there power from solar and battery power.
I changed to the 56.1 beta now, but the problem is still available.
In Mqtt Explorer I can see the value for go_echarger_SERIAL_pgrid = NULL., in HA: Not available (all other value are available)
Will try this the next days.
But as all entities of the go-eCharger are visible in HA (exept the three ones pgrid, pakku and ppv) I don’t think this will solve the problem.
I will give feedback after testing.
Have you check the MQTT it sends the data?
Have you disable API v1 on the app ?
Have you check the automation is correct ?
Have you reboot the charger after the changes ?
Is impossible that not working because if you check the posts in here ( around 95 to 106 ) everybody got an issue with the MQTT but at the end they resolved.
In my setup I was also got an issue ( like yours ) All readings but not charging and NOT readings at Pgrid…after the change on /go-eCharger/serial in the app all start working.
So try please and let us know
P.S. try on the App…MQTT /go-eCharger/serial/
P.S.2 Try also this … rest_command:
update_ids:
url: >- http://192.168.1.XX/api/set?ids={{‘{“pGrid”: ‘}}{{states(‘sensor.GRID’)}}{{’, “pPv”:’}}{{states(‘sensor.SOLAR’)}}{{‘, “pAkku”:0}’}}
method: GET
I deleted the “/” in the /go-eCharger/serial part of the automation, and now I can see the feeback-values of the pgrid, pakku and ppv sensors in the HA dashboard:
(values are 0 because it’s dark outside)
It seems that the values have not been sent to the go-e or if the go-e has not accepted them.
Additionally I set the values for lmo (Logic mode) to 4 (Eco mode), and fup (Use PV surplus) to true. This is reflected in the go-e APP now.
Unfortunately I cannot test the charging function because the car is away and it is dark outside.
But it I think it looks much better now. I will be able to test it next weekend.
Do I have to change anything in the “Base Topic” when installing the integration? Currently it is “/go-eCharger” (everything without " ).
EDIT 2:
It finally works. The error was, the configuration of the MQTT integration was not yet completed, after I added the mqtt-user in the MQTT integration, it worked immediately.
Thanks a lot for this integration. I found it confusing that the setup screen suggests base topic /go-Echarger while this should be without slash. To make it work as suggested you have to add the prepending slash in the app, but that does not follow the standard mqtt setup. So I just reinstalled without the suggested slash.
Thank you! Thats nice! Means you are just sending the data to the Go-e Charger like the Go-e controller would do and all the logic is processed on the charger itself ?
Cause othes in this forum do the logic in Homeassistant and then send the amp and power state to the charger.
Like your approach more if it works cause its very clean then.
Well, in fact the the integration from @syssi does that (instead of any selfmade automation) very well!
If you have an ESS battery and want to prioritize the car charging you need to add a template sensor in the configuration yaml and substract the battery charge current from the current feeding into the grid.
Yes, exactly. I perform no processing in HA at all at the moment. I leave it all to the charger.
Partly because my EV has had a fault in the charger causing it to trip the RCB when stopping 3-phase charging. But now that is fixed and I have no issues letting the charger switch freely between 1- & 3-phase depending on available power. So I may start playing with more logic now.
You could do additional processing in HA if you want. The logic in the charger is simple, and not very flexible. So if you want to do some more advanced calculations, maybe using the electricity price as input, you could do that. I know the charger has logic for that too. But I have not tried it since initially it was not supported in my country.
This is the beauty of this charger, imo, it has an open, cloud-free, API, that allows you to fully control it. But it still has enough logic in itself that a user who doesn’t have somthing like HA can still enjoy these feature.