If you have a go-e Smart meter than everything works out of the box and you don’t need to do anything. If you don’t have it I doubt that the charger is never taking energy from the net. Even the support mentioned that this will not work. In any case if you are happy with your solution do don’t need the blueprints. They are designed around my need around charging (minimum charge in the morning, charging only PV Surplus, Having a calendar integration that defines when the car needs to be full because i am going on a trip, …).
I have one wallbox with go-controller and one wallbox with home assistant. Both working exactly same way. They not pull from the NET.
The automation you point ( charching on low in the morning etc ) yes is worth it to use your blueprints but that is another story.
What i want to say is that the go-controller send exactly the same data like the homeassistant nothing more nothing less. The magic with homeassistant is that you can trigger the wallbox with the trigger data you like…and that you can’t do it with the controller.
I am sorry but you are wrong the only way that the go-e charger is able to know what the current energy flow is, is when you have a smartmeter from the same company which is double the price from any other one (I talked with their support). If you are having one from Gowatter or any other company the go-e chargerd does not get the information about consumption (in/out of energy to the house). In this case you need something inbetween to let the go-e charger has no idea about energy flows and therefor can’t take it into account. I can even tell you how the smart meter communicates with the charger as i studdied the protocol. This extension bridges the gab if you have another smart meter. It can take information from any smart meter that provides the data in HomeAssistant and then tell the go-e what to do.
It is even clearly stated at their website: go-e Controller: PV Surplus Charging & More | go-e Shop.
Let me clarify what I was trying to say earlier:
I have two wallboxes — one using the go-eController and one fully integrated into Home Assistant. Both work the same in terms of how they handle energy input: neither of them pulls directly from the grid/net unless explicitly configured to do so.
Now, the key difference is how flexible Home Assistant is. While the go-eController sends the same kind of basic control data to the charger as Home Assistant does (start/stop charging, limit current, etc.), the big advantage of Home Assistant is that I can define any logic I want for those triggers.
For example, I can use:
- Any smart meter (not limited to go-e’s),
- Solar production data,
- Tariff schedules,
- Weather forecasts,
- Even custom conditions like “only charge if battery > 40% and sun is out”.
This kind of customization just isn’t possible with the go-eController alone. So yes, if you want true energy-aware charging using any third-party smart meter, you do need something in between, like Home Assistant, to bridge the gap and send the correct commands to the charger.
