notDIRK /
luxtronik2-modbus-proxy
Home Assistant HACS integration + Modbus TCP proxy for Luxtronik 2.0 heat pumps (Alpha Innotec, Novelan, Buderus, Nibe). Direct HA integration — IP eingeben, fertig. Plus optional evcc support via Modbus.
Loading repository data…
marq24 / repository
Home Assistant integration for evcc☀️🚘- optimized charging of electric vehicles, connecting your EV charger with your PV system. Please note, that this integration is not official and not supported by the evcc developers. Please consider becoming a monthly sponsor for this project - TIA

I was surprised that it looks like that there does not exist a simple Home Assistant integration for the very popular evcc. So before my first EV spawned at my driveway, I wanted to contribute a very simple and basic integration that allows you to control evcc objects simply via the default HA gui and use sensors and switches in your automations.
Please note, that this Home Assistant integration is not official and not supported by the evcc developers. I am not affiliated with evcc in any way. This integration is based on the evcc API and the evcc API documentation.
[![hacs_badge][hacsbadge]][hacs] [![hainstall][hainstallbadge]][hainstall] [![Wero][werobadge]][wero] [![wise][wisebadge]][wise] [![Revolut][revolutbadge]][revolut] [![PayPal][paypalbadge]][paypal] [![github][ghsbadge]][ghs] [![BuyMeCoffee][buymecoffeebadge]][buymecoffee]
Please be aware that we are developing this integration to the best of our knowledge and belief, but can't give a guarantee. Therefore, use this integration at your own risk.
Supporting all evcc API-POST & DELETE requests (except POST /api/settings/telemetry/<status>) to adjust the evcc settings, loadpoints and the corresponding vehicles
Supporting most of the other loadpoint and vehicle data that is available via the API – please let me know if you miss some data – probably it just slipped through my attention during testing.
With the release of 0.3.x, evcc is now fully configurable via the graphical user interface (GUI). Since to be able to access the evcc-configuration GUI section requires a user authorization (for good reasons) is required, THIS INTEGRATION DOES NOT OFFER ANY ENTITIES OF THE CONFIGURATION SECTION of EVCC! Please don't ask me to add them to this integration. There is no plan to support the evcc-configuration GUI entities in the future. This would require storing the evcc user credentials in the integration configuration, and the variety of possible objects is just too big.
If you want/need to adjust the evcc configuration via home assistant, make use of the HA-REST integration and create the required API calls yourself. Here in this readme you will find an example of what needs to be done.
Take a look at this sample Dashboard (showing Sensors from one load point):

@mkshb have created multiple custom cards that can be installed via HACS (or manually) that
will be a great enhancement for this integration. You can find all the details @ https://github.com/mkshb/hass-evcc-card.
Make sure, that you leave a GitHub star also at mkshb's repostitory!
7070).evcc☀️🚘- Solar Chargingconfiguration.yaml).custom_components directory (folder) there, you need to create it.custom_components directory (folder) create a new folder called evcc_intg.custom_components/evcc_intg/ directory (folder) in this repository.You must have installed the integration (manually or via HACS before)!
Just click the following Button to start the configuration automatically (for the rest see Option 2: Manually steps by step):
Use the following steps for a manual configuration by adding the custom integration using the web interface and follow instruction on screen:
Configuration -> Integrations and add "evcc☀️🚘- Solar Charging" integrationhttp://your-evcc-server-ip:7070After the integration was added, you can use the 'config' button to adjust your settings, you can additionally modify the update interval
Please note that some of the available sensors are not enabled by default.
Please see the separate document where you can find examples how to provide your evcc instance with HA sensor data.
This is IMHO a very powerful feature of evcc, that is not known to many users (yet). You can use evcc to control your Home Assistant devices or Automation, e.g., to switch on/off anything you like when you are actually feeding power into the grid.
Using the maximum out of your solar panels to charge your EV is great, but what if you have more power available — or if your EV is already fully charged? I am facing this challenge for quite a long time now and used several helpers & Blueprints to control my home devices with larger energy consumption.
You can use evcc to control any Home Assistant entity that has implemented the turn_on and turn_off services. This means you can control devices like smart plugs, or even Home Assistant automations (which is IMHO the door to PV surplus handling heaven).
Since the setup and configuration of this evcc feature might not be straight forward, I have created a separate document where you can find examples Master PV surplus handling with evcc & Home Assistent.
I use this feature to control the hot-water temperature of my waterkotte heat pump.
Do you know, that as owners of a go-eCharger (V3+) there is no need to use evcc for solar surplus charging? Even without any additional hardware! Home Assistant and the go-eCharger APIv2 Connect Integration is all you need. Get all details from https://github.com/marq24/ha-goecharger-api2.
There is a known issue when using HASS-IO - For whatever reason it has been reported that the startup sequence of the containers (the different installed AddOns) might not match the requirements of this Integration: Your evcc-server must be up and running before the Integration can be initialized in HA. This is because during the initial start of the Integration your evcc configuration (active loadpoints and configured vehicles) will be evaluated in order to create the corresponding HA entities.So when you restart your HASS-IO server, it can happen that HA already starting to initialize this Integration before the HASS-OS has started the evcc-instance. This will lead to the situation that the Integration is not started correctly.I am sorry that my HA developer skills are not sufficient to find a solution that works in this scenario – nor did I found other integrations with similar challenges (to find inspiration). If you know one (that's actively maintained), please let me know. Of course, I am also open to any PR solving this issue for AddOn users that work in the different scenarios (deactivating/activating the integration, with WebSocket support and without).As a personal note on this: IMHO restarts of HA Servers should only happen under observation, and should not be automated in any kind – but I might be alone with my opinion. ↩
Selected from shared topics, language and repository description—not editorial ratings.
notDIRK /
Home Assistant HACS integration + Modbus TCP proxy for Luxtronik 2.0 heat pumps (Alpha Innotec, Novelan, Buderus, Nibe). Direct HA integration — IP eingeben, fertig. Plus optional evcc support via Modbus.