Thank you so much for your code and explanation. I am a newbie to HA and I managed to set everything up as you do here. So I can read the entities from my wallboy and enable automation for the current value slider .
but my question is, now how do I effectively set the charging amperage through HA programming.
thanks in advance Walter Dekson
@walter.annaert : As shown in the initial post by @lemuba you need two things:
a) A slider to input the desired charge current (which you now have)
b) An automation that triggers on the slider (changes) and sends a command to the wallbox (see the post).
But maybe your question is: how do I automatically start / stop charging?
For this there are multiple integrations. The one that I use is EV Smart Charging which is available under HACS. It uses ‘dynamic pricing’ to find the moment of lowest electricity prices to charge the EV.
If you want to see how I used this, look at the post EV Smart charging with dynamic energy prices in the EU - Energy - Home Assistant Community
There are also Integrations that work with solor panels and home batteries. I have no experience with those.
Thank you for your response. My problem is that I am not familiar with programming in YAML. I always used the visual editor. So, I don’t understand how to change the charging current to, for example, 12A using the current value slider.
My intention is to make the car charge faster depending on the power generated by my solar panels. But i dont know how to do that in the YAML programming section.
Do you perhaps have a photo of how you do this, please?
It is not possible to copy what I have done. But…
You must have an Entity that measures the current/power generated by the solar panel. You can then create (using the visual editor) an Automation that triggers on state changes of this entity.
This will look a little like the following Automation I use when updating the slider:
Under ‘When’ is the trigger, which expands like this:
In the ‘Then do’ section you will set the current limit in de the wallbox using the modbus register. Like this:
Hello BrainDra1n, thank you very much! it works now
I have configured on the Next under load management HEMS activated. The limit is on 6A.What do I need to fill in under external meter ip and port?
The load session stays on 6A even when I change the slider.
I’m not completely sure what you have configured, because ‘load management’ and HEMS are not the same thing.
I have a Unite wallbox. In the webinterface of the wallbox there is an option ‘Local Load Management’, which is seperate from the HEMS (in my case the Monta system connected via OCPP).
Under Local Load Management you choose between:
Selecting Modbus TCP enables a modbus TCP interface. This interface is a modbus slave and can be connected to by Home Assistant (as described above). It has a little bit different registers than the Next. But it is mostly the same. The complete specification is linked below.
So this is the option that you should be looking for in the configuration. Once you have found that, it will not ask for an IP address or portnumber.
Hope this helps.
Links:
I have found a solution which I have discribed here:
Any body else experiencing issues with Meter Reading that either daily or several times a day suddenly measures zero in total kWh? When it return to normal again, Home Assistant think I have used for example 873 kWh in a single day. See the attached image.
I do see the same behaviour.
My Webasto Next has a certified MID meter for energy. Looks like the 0 value is ‘read’ only once and is correct in the next messurement.
I use this value to calculate the actual cost of charging (using the Utility Meter). This seems to work despite this behaviour.
For anyone still searching for a solution with the Webasto Next Charger, I have finally found one. GitHub - cdrfun/webasto_next: This integration allows you to control and monitor your Webasto Next charging station through Home Assistant using Modbus TCP.
@BrainDra1n - Cecile: Sorry for not getting back to the forum to finalise what we started discussing. I really must thank you for all your efforts on this forum. Sadly, I had to back down from implementing it myself because I lack the time. I really appreciate what you are doing here on this forum!!!
To all of you: You can now use these scripts to get Webasto Next to run properly, which it now does on my site.
I had the same when my timeout was too low. 10sec timeout works for me.
Hello, I have copied the program from here. It worked fantastic until now.
Without changing something i cant see anything of my webasto. Can someone help mee please?
Hey everyone! 
I’ve been following this thread for a while and noticed many of you (myself included) struggling with manual YAML configs, keep‑alive automations and Modbus registers.
So I wrapped all the common stuff into a proper custom integration that does the heavy lifting for you.
Webasto Next (Modbus & REST API) integration
The integration handles the annoying bits in the background:
New in v1.1.0:
I just shipped a major update that adds optional Wallbox REST API support. That brings features you don’t get via Modbus:
LED brightness control (dim or turn off).
Free‑charging mode toggle and Tag‑ID management.
Diagnostics: firmware/hardware versions and detailed error info.
Reboot: restart the wallbox directly from Home Assistant.Give it a try if you’re tired of hand‑rolled Modbus configs. Feedback is always welcome!
GitHub repository: https://github.com/tomwellnitz/Webasto-Next-Modbus
Enjoy! 
In my Webasto Next I did’t see the “system maintenance” option in the top-right menu, however this was solved just bij using another browser. 
I need to update the firmware because I want to manage the Webasto via EVCC, for which I need to enable Modbus.
Modbus does not work; I think it is because of the older firmware version.
My firmware: HMI Software Version: v2.99.11
I am trying to contact Webasto. In the mean time it would be nice is someone can point me a firmware download. Cheers!
