ha-evcc - Show WebSocket connection state in device information [tweaked]

Showing WebSocket connection state

With the new release the WebSocket connection state will be displayed as part of the Device Information (tweaked: Only show when WebSocket is enabled). I'm brief, since I am so fed up with what is happening in this crazy world.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 7 days ago

ha-evcc - Show WebSocket connection state in device information

Showing WebSocket connection state

With the new release the WebSocket connection state will be displayed as part of the Device Information. I'm brief, since I am so fed up with what is happening in this crazy world.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 8 days ago

ha-evcc - Support for BatteryBoostLimit per Loadpoint

Battery Boost Limit

I am not 100% sure, if or when this slipped through my attention - at least I saw in the evcc release notes of 0.301.0 that there is a setting (and the evcc GUI have been adjusted) to specify till which SOC (of your home battery) the battery boost should be used. With this release you can specify now this limit also via the integration (100% = deactivated)

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 19 days ago

ha-evcc - pv panel list is so "anonymous" #233

adding title to PV Sensors

As requested in #233 the optional PV sensors have the title as additional sensor attribute (when title is available) - If you have no clue about what this change is, then you probably have not enabled the additional PV power & energy sensors, which is totally fine if you have a single PV source.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 23 days ago

ha-evcc - HA 2026.2 adjustments (patched)

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 month ago

ha-evcc - HA 2026.2 adjustments

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 month ago

ha-evcc - HA 2026.2 adjustments

HA 2026.2 adjustments

The upcoming release of HA 2026.2 requires an update of this integration. That's why it's so important, that an integration will be actively maintained.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 month ago

ha-evcc - A little Load Management enhancement

Two additional (disabled by default) Entities for Load Management

Initial requested in #221, in #228 additional sensors had been requested - I just can guess, if this update will go into the right direction (cause of missing details)... In any case with this update the Integration will add for each of your configured circuits two new sensor entities that will show the power and current values provided via the state API (only a single value for the current - not separated by phases)

Please note that the name of the circuits the integration is using is just the technical ID - since the human readable name is only available via the config endpoint (that required authorization, which is not implemented in the integration).

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 month ago

ha-evcc - Minor Fix in Optimizer charge/discharge entities

SensorStateClass corrected

Of course with the unit change from W to Wh also the SensorStateClass must be adopted from MEASUREMENT to TOTAL - with this patch the initial warning when restarting HA should disappear.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Enhancement for Optimizer values (v4)

Added Timeseries Sensor

Turned out, that all the values available in the optimizer values are Energy (not Power) - but in you might be interested in which time-frame? So the new Version have added an additional 'Optimizer' Sensor. This contain all the time-deltas. Further details can be found in the Issue #224.

Also with the release the unit's of the charge/discharge Optimizer Sensors have been adjusted - so make sure to use the 'fix statistic' function of the HA developer tools [http://your-ha-ip:8123/developer-tools/statistics]

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Enhancement for Optimizer values (v3)

Expect the unexpected

The 2026.1.5 introduced timestamp if of course only a single time available in the result list (and not separate per Battery optimization) - I did not expected that - once the object is an list - but again the evcc optimizer is EXPERIMENTAL - and this is the nature of experiments :-) So just another short update during my lunch break.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Enhancement for Optimizer values (v2)

When... When Will I Be Famous?

You don't have a single clue, for what time the new optimizer values are relevant - also you don't know the time delta between the different values (while the time delta between the points can be smart guessed), this is not the case for the start (=first) point.

Therefor the new release will add the attribute timstamp to the attributes of the three optimizer sensors that have been introduced with https://github.com/marq24/ha-evcc/tree/2026.1.2

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Enhancement for Optimizer values

Switching Optimizer Sensors

Unfortunately the current evcc implementation will switch the objects for the different batteries, depending on the connection state of your vehicles - currently there is no real solution in the HA Integration to detect this switching dynamically and handle it generally - so you must handle this in your local templates.

Therefor the new release will add the attributes name, type and capacity (also title when available) to the attributes of the three optimizer sensors that have been introduced with https://github.com/marq24/ha-evcc/tree/2026.1.2

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Fix #225 'WARNING' NO 'circuits' found [circuits] in the evcc data

Bugfix

The new Release will fix #225 - Warning in HA log on every restart read_evcc_config_on_startup(): NO 'circuits' found [circuits] in the evcc data - of course circuits are just optional, so this should be just info/debug.

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Initial Optimizer values

Support of (optional) Optimizer Values

In the issue #223 it has been requested, if it would be possible to add optional available EV Optimizer values via this Integration. Even if the complete optimizer stuff is quite experimental, adding some basic support for this was not that complicated - ok, lets say this implementation is at least not over engineered.

The integration is now offering for the following new Sensors (deactivated by default):

• Optimizer: Charging Power
• Optimizer: Discharging Power
• Optimizer: Total Energy (State of Charge)

the current value as state (index 0), as well as all other values in the attributes of the new sensors

There are up to 3 batteries that the integration is supporting right now (adding more can be done very easy if there is the need). All the new entities are disabled by default, so if you want to use them you must activate them (you can search for 'Optimizer').

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 2 months ago

ha-evcc - Happy New Year 2026

Initial support for Load Management

In the discussion #221 the question came up, if the integration could provide the status of the load management (for a given circuit). I have to admit, before this discussion was started, that I was not aware of all the related stuff - that had send me directly into a deep deep rabbit hole of § 14a des Energiewirtschaftsgesetzes.

In any case, before I will spend more time (in this hole) trying to understand, How to access my SMGW via HAM (passing the auth). I want to wish you all the best for the year 2026 and release an initial version of the support for the Load Management.

The Integration will add for each of your configured circuits a new boolean_sensor entity (in the diagnostic section) that will indicate the status of the circuits - if it's currently dimmed or not.

Please note that the name of the circuits the integration is using is just the technical ID - since the human readable name is only available via the config endpoint (that required authorisation, which is not implemented in the integration).

Please consider supporting me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 2 months ago

ha-evcc - "Ahead of its time" Release | This repository is active notice

No functional changes

With this release I just want to signal, that this repository is activity maintained and I am continue to monitor it for any reported issue in the year 2026.

Please consider support me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 2 months ago

ha-evcc - Tariff data... way more Tariff data

Site Tariff Values

While I was implementing #124, extracting the data from the forecast object, I was made aware that the current/now value is also available directly at the site as tariffFeedIn. Well, looks like that after the initial release of this integration evcc providing multiple values in a tariff* block. While tariffGrid and tariffPriceHome had been present in this integration from the start, with this release the following values will be added as well:

• tariffCo2
• tariffCo2Home
• tariffCo2Loadpoints
• tariffFeedIn
• tariffPriceLoadpoints
• tariffSolar [current PV prognosis]

All sensors names of this group (incl. Cost Grid & Cost Usage) will now have the suffix [Site] in HA, so you can distinguish them from the Sensors based on the forecast object and the ones from the tariffs-api-endpoints (which have the suffix [Tariff-API]).

And yes the naming for the new sensors might be quite strange - specially in German - if you have smarter ideas - just make a PR.

Sensors for the Forecast Object

The forecast object will be updated frequently via the websocket connection. This afternoon I realized, that beside the already existing solar & grid forecast data there exist also sequences for Feedin and Planner. So there are the two new Sensors:

• FeedIn
• Planner

Beside the current values (which should be identical to the 'Site Tariff' Sensors) there will be attributes with the full data sequence in the compressed format that was introduced with 2025.12.1.

Please note, that this new sensors are disabled by default.

Tariff API Endpoint Sensors

Beside the forecast object, the data sequences are also available via sperate API endpoints (will be requested in a certain (must double check this) update interval.

The structure of the response is quite similar to the forecast object - but I am not that much into the evcc details, to explain, why the data is available vie additional endpoints, this might be historic reasons - in any case since solar and grid is already supported by the integration, I have also added feedin & planner as well.

Please note, that this new sensors are disabled by default.

Please consider support me

Thanks to those who have already supported me in the past weeks or month that is highly appreciated! To the other users: I am putting quite an amount of energy and passion into this integration. Perhaps you could give yourself a little push (if you can afford it) and become a sponsor.

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 3 months ago

ha-evcc - 2025.12.3

Bugfix

As 'mentioned' here in a commit comment the integration was not able to handle Version strings that contained - (minus character). This will be fixed with this release.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes as well as supporting the evcc development directly. And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 3 months ago

ha-evcc - Fixing 'current value' dependent Selects

Bugfix

As reported in #217 in evcc there are some configuration options (selects) where the available options are dependent from current values of other selects. This dependency functionality was broken in 2025.10.2. With this new release it should work again.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes as well as supporting the evcc development directly. And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 3 months ago

ha-evcc - BREAKING CHANGE: reduce object size of Forecast / Tariff attribute Information

BREAKING CHANGE: Reduzed size of Forecast / Tariff attribute Information

As reported in #214 the initial approach to reduce the size of some entity attributes was not enough [see releases 2025.10.1/2/3/4/5/6]. So I have decided for a complete different approach to reduce the size of the JSON/DATA object that evcc backend is providing.

When you use the attributes (range or timeseries) of the following entities in your templates:

• sensor.evcc_forecast_grid
• sensor.evcc_forecast_solar
• sensor.evcc_tariff_api_grid
• sensor.evcc_tariff_api_solar

You must adjust your templates to be compatible with the new release - please continue reading for further details.

Some background Information

When the evcc backend is going to provide a time series of data points, then this will be done in a list of objects. Each object contain a start timestamp information (sometimes also a end timestamp) and the actual value. The timestamp information is a String like this 2025-12-06T00:00:00+01:00. When there are 400 data points in the list, this means, that there are at least 400 start time timestamp information (beside the actual values). This approach makes it very easy for a frontend to consume this data - with the downside, that the data structure is quite large.

In the previous releases the attempt was to keep this overall structure but reducing the length of a this time information string by concerting it to so called UNIX Timestamps (in the UTC-Timezone). This was working some sort of ok for the switch from 1h data points data to 15min data points (4x size). But when solar prognosis data is now available for +4 days, this approach is still failing.

So in this new release I have implemented a different approach to reduce the size of data of the range & timeseries data lists.

Instead of storing for each value the time, I will now store the start time of the first value and then only store the time delta in minutes between the points. So far this time delta is always 15min in my case - but it might happen in the future that this will change - so I want to keep the delta's in a second list.

So a evcc object like this:

{ "range": [
{"start":"2025-12-06T00:00:00+01:00","end":"2025-12-06T00:15:00+01:00","value":0},
{"start":"2025-12-06T00:15:00+01:00","end":"2025-12-06T00:30:00+01:00","value":1},
{"start":"2025-12-06T00:30:00+01:00","end":"2025-12-06T00:45:00+01:00","value":2},
{"start":"2025-12-06T00:45:00+01:00","end":"2025-12-06T01:00:00+01:00","value":3},
{"start":"2025-12-06T01:00:00+01:00","end":"2025-12-06T01:15:00+01:00","value":4}
]}

Will be converted to a structure in a home assistant attribute like this:

{"range": {
"start_utc": "2025-12-05T23:00:00+00:00"
"deltas_in_minutes": [15, 15, 15, 15]
"values": [0, 1, 2, 3, 4]
}}

I hope you see, the benefit size wise in this new structure.

Home assistant template examples working with the new structure

Getting the origin format / JSON [updated]

{%set json_data=state_attr('sensor.evcc_forecast_grid', 'rates')%}
{% set start_time = as_local(as_datetime(json_data['start_utc'])) %}
{% set deltas = json_data['deltas_in_minutes'] %}
{% set values = json_data['values'] %}
{% set ns = namespace(result=[]) %}
{% for i in range(values |length) %}
  {% set current_start = (start_time + timedelta(minutes=(deltas[:i]|sum))) %}
  {% set current_end = (current_start + timedelta(minutes=deltas[(i, deltas|length-1)|min])) %}
  {% set grid_entry = {
    'start': current_start.isoformat(),
    'end': current_end.isoformat(),
    'value': values[i]
  } %}
  {% set ns.result = ns.result + [grid_entry] %}
{% endfor %}
{{ ns.result }}

Getting current (now) value

{%set json_data=state_attr('sensor.evcc_forecast_grid', 'rates')%}
{% set total_minutes_since_start = (( now() - strptime(json_data['start_utc'], '%Y-%m-%dT%H:%M:%S%z')).total_seconds() // 60)|int %}
{% set tmp = namespace(total=0, index=0) %}
{% for delta in json_data['deltas_in_minutes'] %}
    {% if tmp.total < total_minutes_since_start %}
        {% set tmp.total = tmp.total + delta %}
        {% set tmp.index = tmp.index + 1 %}
    {% else %}
        {% break %}
    {% endif %}
{% endfor %}
{{json_data['values'][tmp.index]}}

Getting average value from series

{%set json_data=state_attr('sensor.evcc_forecast_solar', 'timeseries')%}
{{json_data['values']|sum / json_data['values']|length}}

Getting average value from (now)

{%set json_data=state_attr('sensor.evcc_forecast_solar', 'timeseries')%}
{% set total_minutes_since_start = (( now() - strptime(json_data['start_utc'], '%Y-%m-%dT%H:%M:%S%z')).total_seconds() // 60)|int %}
{% set tmp = namespace(total=0, index=0) %}
{% for delta in json_data['deltas_in_minutes'] %}
    {% if tmp.total < total_minutes_since_start %}
        {% set tmp.total = tmp.total + delta %}
        {% set tmp.index = tmp.index + 1 %}
    {% else %}
        {% break %}
    {% endif %}
{% endfor %}
{% set relevant_values = json_data['values'][tmp.index:] %}
{% set average_value = (relevant_values|sum) / relevant_values|length if relevant_values|length > 0 else 0 %}
{{ average_value }}

Rephrased Initial setup dialog

Thanks @olli-dot-dev to remind me in his YT Channel, that it might had been the time to rephrase my rant (after a year).

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes as well as supporting the evcc development directly. And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 3 months ago

ha-evcc - 2025.12.0

Working on issues

Issue #140 started with the request, to be able to show the vehicle soc limit and ended with an agreement, that for what ever reason the evcc API return loadpoints[n]:limitSoc as 0 when the vehicle will be connected to the loadpoint, while the loadpoints[n]:effectiveLimitSoc is showing the value, that's displayed in evcc as the main loadpoint slider value.

Moving the this slider in evcc UI, will cause the update of the loadpoints[n]:limitSoc and the loadpoints[n]:effectiveLimitSoc values to the selected value of the slider.

So the initial state (after a vehicle is connected to a loadpoint):

• loadpoints[n]:limitSoc = 0
• loadpoints[n]:effectiveLimitSoc = vehicles['connected_veh_id']:limitSoc

Once the slider is moved in evcc UI

• loadpoints[n]:limitSoc = slider-value
• loadpoints[n]:effectiveLimitSoc = slider-value
• vehicles['connected_veh_id']:limitSoc = not changed

I made the mistake, to assume, that when the API provides loadpoints[n]:limitSoc = 0, that I then can use 100 as value (since that was matching my setup at that time).

In the new version of the integration, the value for the slider with the entity id number.evcc_[lp:id]_limit_soc will use still loadpoints[n]:limitSoc from the evcc API, but when this API value is 0, then the integration will use the value of loadpoints[n]:effectiveLimitSoc as fallback (instead of the previously hard coded value 100).

There are way to much different soc limit values/fields - and I am pretty sure this will be quite confusing for plenty of users and I am confident, that in +10 days I have forgotten again, how this is all working together...

New Sensor per Loadpoint: Vehicle Charging limit

Since #140 initially started with the request, to add also a sensor, that will provide the current connected vehicle soc limit, the integration now provide sensor.evcc_[lp:id]_vehicle_limit_soc

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes as well as supporting the evcc development directly. And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 3 months ago

ha-evcc - Added charging Currents P1-P3 as Sensors

Added charging currents P1-P3 as Sensors

As requested in #205 this release will add additional sensors for the charging sessions information available from the loadpoints.

Please note, that this new sensors are disabled by default.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 4 months ago

ha-evcc - 'just' maintenance (fixed?)

Maintenance

this new version does no provide any new functionality - the device names have been slightly adjusted and some internal code stuff had been cleaned up - if everything run smooth you will not notice anything in this new release - keep my fingers crossed.

Enjoy the rest of the weekend!

2025.11.1 patch

fixing #204

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 4 months ago

ha-evcc - 'just' maintenance

Maintenance

this new version does no provide any new functionality - the device names have been slightly adjusted and some internal code stuff had been cleaned up - if everything run smooth you will not notice anything in this new release - keep my fingers crossed.

Enjoy the rest of the weekend!

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

If you haven't starred this integration in Github yet - please do so - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 4 months ago

ha-evcc - Support to delete Vehicle & Loadpoint plans

Create & Delete Loadpoint/Vehicle plans

While creating a loadpoint plan has been implemented quite a while ago (and creating a vehicle plan had been added recently), there was no option to delete this plan again.

In #154 it had been requested, if I could add this 'simple' toggle to enable/disable a plan - unfortunately this can't be supported out of the box. Since when you toggle this switch to off, evcc will delete an existing plan, and when you enable the switch it will create the plan.

So with the latest changes you have also this options via the HA services this integration is providing.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Recent updates in evcc, that just ...

New message-keys in Websocket data

No clue which update, but in recent evcc version the key forcast.solar have been added to the websocket data stream - previously these message keys only contained two . or none... So each time the new key was received the integration generated a log message on INFO level (#192).

In this new release - yes another day - another release this have been fixed and also new single-dot-message-keys will be handled (if the domain exist).

BREAKING CHANGE (just if you have missed the release 2025.10.1/2/3/4/5/6)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Added option to set priority of a Loadpoint

Loadpoint priority

As asked in #191, you can now adjust the priority of a loadpoint via HA (have in mind, that a possible existing priority of a vehicle will overwrite this setting (see https://docs.evcc.io/en/docs/reference/configuration/loadpoints#priority for details in the evcc documentation).

The setting have been implemented as slider and allow the max priority of 10 - which should be fine in most of the scenarios - I don't expect evcc users who have more the 11 Loadpoints configured.

BREAKING CHANGE (just if you have missed the release 2025.10.1/2/3/4/5)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Another day, another update...

Set Vehicle Loadplan by @thecem [FIXED]

Recently the Service to set a load plan for a vehicle (that is currently not connected to a Loadpoint) have been introduced, somehow I misunderstood the PR from @thecem so the initial release was 'suboptimal) - still required a Loadpoint ID - this have been now fixed, and when you know the evcc vehicle name (like db:nn) then you can set the SOC via the Service.

Fixing NoneType error (Tariff-API Endpoint Sensors) [FIXED]

As reported this morning in https://github.com/marq24/ha-evcc/issues/188, the code did not check, if there is any data (that should be shortened). This is fixed in this release

Option (via configuration) to delete & recreate all devices

As reported in #186 it could happen, that you have orphan devices for this Integration - Manually deleting devices is quite tricky (yaml file editing) so in this release you have the possibility to delete all devices created by the integration (config_entry). During the restart all devices (that should exist) will be recreated.

You can request a cleanup via a new checkbox in the configuration of the integration entry called: Remove an recreate all Devices.

The implementation of this functionality require, that all current exiting devices will be removed and new ones will be generated - if you have some automations, templates or what so ever based on a device_id, then you must adjust this device_id after the update. I am sorry of this inconvenience.

BREAKING CHANGE (just if you have missed the release 2025.10.1/2025.10.2/2025.10.3/2025.10.4)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Vehicle Loadplan Service & EarlyBird Fix (another Tariff-API Endpoint issue)

Set Vehicle Loadplan by @thecem

Recently the Service to set a load plan for a vehicle (that is currently not connected to a Loadpoint) have been introduced, somehow I misunderstood the PR from @thecem so the initial release was 'suboptimal) - still required a Loadpoint ID - this have been now fixed, and when you know the evcc vehicle name (like db:nn) then you can set the SOC via the Service.

Fixing NoneType error (Tariff-API Endpoint Sensors)

As reported this morning in #188, the code did not check, if there is any data (that should be shortened). This is fixed in this release

BREAKING CHANGE (just if you have missed the release 2025.10.1/2025.10.2/2025.10.3)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Vehicles configured via UI (v2 - or better 2'nd attempt)

Vehicles configured via UI - v2

There is more than one 'platform_translations' - there is also 'default_language_platform_translations' in HA - I hope, when adding the Vehicle Name keys's also to this second dictionary, that then the display of db:nn will be history - Bernd has to provide his feedback. #184.

BREAKING CHANGE (just if you have missed the release 2025.10.1/2025.10.2)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Rollback of replacement of ':' (with '_') for evcc vehicle identifiers

Rollback of patching identifiers (that was a BAD idea)

Thanks to the feedback of @thecem I have debugged the issue with the evcc vehicle identifiers containing a : character more intense. And I could not find any evidence, that the : character is not supported by HA state translation-keys. Therefore I have decided to roll back this change and keep the names as they are...

Additionally I have included to the VEHICLENAME Select entity an additional state attribute vehicle, containing all internal details the integration have collected for the current selected vehicle identifier (that should not shown in the select as identifier - it should be still shown with its specified title (human readable name). Thanks once again to @thecem for his comments!

BREAKING CHANGE (just if you have missed the release 2025.10.1)

I have replaced all iso formatted date/time information by Unix timestamps in the tariffs & prognosis sensor state attributes (to reduce the size of the dictionary). These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Fix, fix as fix as I can... (probably that's sounds only funny for Germans - and even than...)

More max size of 16384 bytes stuff

Even if some of the entities have been fixed with 2025.10.0 concerning the attributes size limit of '16384 bytes', it have been reported in #185, that there are other entities with a similar problem - Actually that have been the ones, that querying the additional tariff API endpoint (and that are disabled by default).

These entities are now also fixed.

But in general there are different issues with the size of the data that the evcc API is returning. E.g there a values with 8 or more fraction digits. I am not sure where this is coming from, but I don't see any value in this additional precision. So I have added some rounding code in order to reduce the number of digits.

But that's not all!

BREAKING CHANGE

In addition I have replaced all iso formatted date/time information by Unix timestamps. These timestamps are all GMT time zone based.

So if you are using evcc sensor attributes like the 'rates': You must adjust your templates, and you must adjust your date/time information parsing [switch from datetime.fromisoformat(a_entry["ts"]).astimezone(timezone.utc) to datetime.fromtimestamp(a_entry["ts_utc"], tz=timezone.utc)]

I have to admit, that I assume, that HA user have the costs and the solar prognosis data already elsewhere in Home Assistant, and does not rely on the information present in the evcc sensors of this integration. If this is not the case, and you use evcc sensors from this integration, then this update will break your current setup. In this case just check the new attributes and the used keys and adjust your templates. I am sorry for this inconvenience.

Vehicles configured via UI

This is a long running issue - reported again in #184. Well, when configure a vehicle via the UI of evcc, the internal vehicle name will contain a : character. While this seams to be no deal in evcc, this cause quite some trouble in the HA integration. Finally I found and (IMHO) acceptable workaround for patching these kind of IDs internally - I will keep my fingers crossed, that this will not mess up any other stuff.

If you have any issues with the Vehicle selection for a Loadpoint after this release, please create an issue, sharing your api/state response as well as the HA debug log output (can be sent by eMail) - TIA

Please consider to support me

Thanks for the people who already did - that's highly appreciated! In the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Grid Forecast Sensor can exceed the '16384 byte' Limit (for attribues)

With the change to prizes ever 15 minutes the size of the Grid Forecast Sensor (attributes) have been also increased by factor 4 - Unfortunately HA can only handle a max size of 16384 bytes. So I have to remove the 'end' key from the forecast array. Since this info was IMHO anyhow redundant, since n:end value is always n+1:start.

Also thanks to @pergolafabio for reporting #182 and fixing it in #183

... aaaand since of https://github.com/marq24/ha-evcc/discussions/178 you might (or will be for sure) requested to repair the unit in the statistics data - since the sensor unit changed from (invalid) CO2/kWh to (valid) g/kWh

Please consider to support me

I the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 5 months ago

ha-evcc - Charging Session [total values] as integrated Sensors (per Loadpoint & per Vehicle)

Charging Session Sensors per Vehicle & per Loadpoint

In evcc you have the option to show all kind of statistic data based on the charging session [Ladevorgänge]. In the new release for each loadpoint and for each vehicle the the integration will provide three additional sensor entities which is the sum of all charging session:

• Total chargedEnergy (in kWh)
• Total chargeDuration (in seconds)
• Total costs

This will make the manual creation of the template sensors for active vehicles & loadpoints obsolete. All the new entities will contain the string cstotal (charging session total) as part of their entity ID.

The sessions sensor will be updated every hour... no matter of a possible configured update interval.

Please consider to support me

I the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Create a template sensor [for inactive vehicles and loadpoints]

Accessing Charging Session data for inactive vehicles and loadpoints

It could be the case, that your historic charging session data will contain outdated vehicles or loadpoints - For this legacy vehicles/loadpoints the integration will not provide sensor entities.

But you can still access the data via the generic sensor.evcc_charging_sessions entity.

Inspecting via

{{state_attr('sensor.evcc_charging_sessions', 'vehicles') }}
{{state_attr('sensor.evcc_charging_sessions', 'loadpoints') }}

Example for a Vehicle:

{% set key='vehicles' %}
{% set veh='MachE XX-XXABC' %}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargedEnergy']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargeDuration']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['cost']}}

So if you want to have the total energy for a vehicle (to use it e.g. in the HA Energy tab), create a template sensor and use {{state_attr('sensor.evcc_charging_sessions', 'vehicles')[YOUR_VEH_NAME_HERE]['chargedEnergy']}} as value

Consumption - Mobility and Transportation - Python
Published by marq24 6 months ago

ha-evcc - Supporting Charging Session [total values] - (fault tolerant v2)

Charging Session Sensor [fixed]

In evcc you have the option to show all kind of statistic data based on the charging session [Ladevorgänge]. In the new release a sensor have been added sensor.evcc_charging_sessions that provide the total summary [of the fields: chargedEnergy, chargeDuration & cost (in evcc this is price)] of all sessions per loadpoint and per vehicle as sensor attributes. In v2025.9.1 & v2025.9.2 the code will check, if the fields are present in the session entry before using them.

The sessions sensor will be updated every hour... no matter of a possible configured update interval.

Create a template sensor

Inspecting via

{{state_attr('sensor.evcc_charging_sessions', 'vehicles') }}
{{state_attr('sensor.evcc_charging_sessions', 'loadpoints') }}

Example for a Vehicle:

{% set key='vehicles' %}
{% set veh='MachE XX-XXABC' %}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargedEnergy']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargeDuration']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['cost']}}

So if you want to have the total energy for a vehicle (to use it e.g. in the HA Energy tab), create a template sensor and use {{state_attr('sensor.evcc_charging_sessions', 'vehicles')[YOUR_VEH_NAME_HERE]['chargedEnergy']}} as value

Added option to specify precondition for set_vehicle_plan Service

Kudos @thecem

Please consider to support me

I the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 6 months ago

ha-evcc - Supporting Charging Session [total values] - (fault tolerant)

Charging Session Sensor [fixed]

In evcc you have the option to show all kind of statistic data based on the charging session [Ladevorgänge]. In the new release a sensor have been added sensor.evcc_charging_sessions that provide the total summary [of the fields: chargedEnergy, chargeDuration & cost (in evcc this is price)] of all sessions per loadpoint and per vehicle as sensor attributes. In v2025.9.1 the code will check, if the fields are present in the session entry before using them.

The sessions sensor will be updated every hour... no matter of a possible configured update interval.

Create a template sensor

Inspecting via

{{state_attr('sensor.evcc_charging_sessions', 'vehicles') }}
{{state_attr('sensor.evcc_charging_sessions', 'loadpoints') }}

Example for a Vehicle:

{% set key='vehicles' %}
{% set veh='MachE XX-XXABC' %}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargedEnergy']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargeDuration']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['cost']}}

So if you want to have the total energy for a vehicle (to use it e.g. in the HA Energy tab), create a template sensor and use {{state_attr('sensor.evcc_charging_sessions', 'vehicles')[YOUR_VEH_NAME_HERE]['chargedEnergy']}} as value

Added option to specify precondition for set_vehicle_plan Service

Kudos @thecem

Please consider to support me

I the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 6 months ago

ha-evcc - Supporting Charging Session [total values]

Charging Session Sensor

In evcc you have the option to show all kind of statistic data based on the charging session [Ladevorgänge]. In the new release a sensor have been added sensor.evcc_charging_sessions that provide the total summary [of the fields: chargedEnergy, chargeDuration & cost (in evcc this is price)] of all sessions per loadpoint and per vehicle as sensor attributes.

The sessions sensor will be updated every hour... no matter of a possible configured update interval.

Create a template sensor

Inspecting via

{{state_attr('sensor.evcc_charging_sessions', 'vehicles') }}
{{state_attr('sensor.evcc_charging_sessions', 'loadpoints') }}

Example for a Vehicle:

{% set key='vehicles' %}
{% set veh='MachE XX-XXABC' %}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargedEnergy']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['chargeDuration']}}
{{state_attr('sensor.evcc_charging_sessions', key)[veh]['cost']}}

So if you want to have the total energy for a vehicle (to use it e.g. in the HA Energy tab), create a template sensor and use {{state_attr('sensor.evcc_charging_sessions', 'vehicles')[YOUR_VEH_NAME_HERE]['chargedEnergy']}} as value

Added option to specify precondition for set_vehicle_plan Service

Kudos @thecem

Please consider to support me

I the past weeks I had to invest plenty of my time in order to keep the Integration up to date with the latest changes... And there might be just more that will come around the corner...

Consumption - Mobility and Transportation - Python
Published by marq24 6 months ago

ha-evcc - Implemented 'retry integration start till evcc is up and running'

Kudos @meks007 for providing a solution for #158 - during the start of the Integration it will be checked, if the configured evcc server is reachable and raise ConfigEntryNotReady exception, if this is not the case.

Your HA installation should (& will) handle this early ConfigEntryNotReady signal appropriate by retry to initialize the Integration again (after a short while) - this loop will be repeated till the integration will finally can reach the evcc server.

Local tests have shown that this HA-retry-to-init-integration-loop can run for over 1h... where the pause to the next retry will increase over the attempts.

As so often - just let HA handle the situation and "just" provide the correct signals. I am not sure where I have left this path with this evcc-integration. Nevertheless once more Thanks @meks007.

Ceterum censeo Carthaginem esse delendam - I am still have the opinion, that (automated) frequent re-starts of a HA-Server can be and appropriate solution to any problem.

Consumption - Mobility and Transportation - Python
Published by marq24 7 months ago

ha-evcc - Maintenance Update | added HA backward compatibility | fixed restart issue

If you are not on the latest HA Version, then the fix for #161 will cause errors - so the code check now, if the new property is present... and if not use the old code... Hopefully this solves #163

The previous changes of the restart-procedure of the integration have been rolled-back - make sure that your EVCC is up and running before starting this Integration.

Consumption - Mobility and Transportation - Python
Published by marq24 7 months ago

ha-evcc - Maintenance Update | added HA backward compatibility

If you are not on the latest HA Version, then the fix for #161 will cause errors - so the code check now, if the new property is present... and if not use the old code... Hopefully this solves #163

Consumption - Mobility and Transportation - Python
Published by marq24 7 months ago

ha-evcc - Maintenance Update

Fixing #162 , #161, #157

Consumption - Mobility and Transportation - Python
Published by marq24 7 months ago

ha-evcc - Support multiple Battery Installations (SOC & Power Sensors)

As asked in #153 - with this release it's possible to enable additional Battery SOC & Power Sensors for multi-battery-installations.

Consumption - Mobility and Transportation - Python
Published by marq24 8 months ago

ha-evcc - Supporting charger feature 'IntegratedDevice' & 'SinglePhase'

During the weekend I have spend some time to evaluate a evcc feature called 'IntegratedDevice'.

I am not sure, since when evcc is supporting '' [my understanding: a Loadpoint with a "hardcoded" Vehicle] - but for sure when you have configured such a loadpoint in your evcc installation, then multiple entities (like the vehicle selector) are obsolete in home assistant.

With this release some of the loadpoint entities will not be available for such a IntegratedDevice Loadpoint. Please let me know if you are missing entities (that should be in your opinion still present - TIA.

Binary Sensor Entities

• Tag.CONNECTED - Vehicle connectivity status
• Tag.VEHICLEDETECTIONACTIVE - Vehicle detection active status
• Tag.VEHICLECLIMATERACTIVE - Vehicle climate control active status
• Tag.VEHICLEWELCOMEACTIVE - Vehicle welcome feature active status

Button Entities

• Tag.VEHICLEPLANSDELETE - Delete vehicle charging plans
• Tag.PLANDELETE - Delete charging plan
• Tag.DETECTVEHICLE - Trigger vehicle detection
• Tag.SMARTCOSTLIMIT - Smart cost limit button

Select Entities

• Tag.VEHICLENAME - Vehicle name selection
• Tag.VEHICLELIMITSOC - Vehicle limit state of charge
• Tag.VEHICLEMINSOC - Vehicle minimum state of charge

Sensor Entities

• Tag.VEHICLEODOMETER - Vehicle odometer reading
• Tag.VEHICLERANGE - Vehicle remaining range
• Tag.VEHICLESOC - Vehicle state of charge
• Tag.VEHICLEPLANSSOC - Vehicle planned state of charge
• Tag.VEHICLEPLANSTIME - Vehicle planned charging time

Consumption - Mobility and Transportation - Python
Published by marq24 8 months ago

ha-evcc - Supporting re-Configuration

Supporting re-Configuration

In previous releases it was not possible to change a config_entry. When you wanted to change settings like the IP, toggle WS or other initial settings you had to do this via the additional configuration. This approach implied, that the core configuration values existed twice - once as config_entry.data and then a second one as config_entry.options.

Few days ago I realized, that HA is supporting also a 'reconfiguration' of an existing config_entry - overwriting/updating previous data.

Preparation for an upcoming change in evcc-API's

Prepare the code to handle the changes in the API that will be rolled out in the future - https://github.com/evcc-io/evcc/pull/22299

Consumption - Mobility and Transportation - Python
Published by marq24 8 months ago

ha-evcc - Additional checks on startup

Integration will check (before accessing) if vehicle or `loadpoint data is available from your evcc server [which is essential to be present IMHO] - but anyhow checking is better then crashing.

Consumption - Mobility and Transportation - Python
Published by marq24 9 months ago

ha-evcc - Fix "no car" at Loadpoint connected should show '-none-' (and not unknown)

Thanks @Piranha1511 for reporting that 'with some change @ the evcc backend' the Vehicle@Loadpoint select was proken - see #139 - This has been fixed in the new release

Consumption - Mobility and Transportation - Python
Published by marq24 9 months ago

ha-evcc - Catch possible errors in async SELECT 'check_min_max' function

Fix (I'll keep my fingers crossed) issue #136

Thanks @Moritz921 for starting the discussion #135

Consumption - Mobility and Transportation - Python
Published by marq24 9 months ago

ha-evcc - Multiloadpoint scenario: One HA device per evcc-loadpoint

When you have configured multiple loadpoints in your evcc installation, then the Integration will now split up the entities to one core evcc Device, and then for each loadpoint a separate HA device. So when you have two loadpoints configured the integration will create three devices.

If you have a just a single loadpoint (and my assumption is, that this are the majority), then this update will not change anything - all entities are together in a single HA device.

Thanks @grogi for your suggestion - for me as "single loadpoint user" this was never an issue ;-)
https://github.com/marq24/ha-evcc/issues/134

Consumption - Mobility and Transportation - Python
Published by marq24 9 months ago

ha-evcc - Update always all states data (removed filter)

If you are still not using websocket communication (for what ever reason), then with the new build all values present in the plain api/state request. So in the new build the previously existing filter statement have been removed.

If you make use of the websocket communication the new build should have no impact at all.

Consumption - Mobility and Transportation - Python
Published by marq24 10 months ago

ha-evcc - Feature request #118 - Show Heating SOC fields as ° and not as % [patched II]

As requested in #118 this new version should show SOC values of Loadpoints that are maked as chargerFeatureHeating in ° Celsius (and not as %)

This is why it's also called Banana-Software...

Consumption - Mobility and Transportation - Python
Published by marq24 11 months ago

ha-evcc - Support for alternative API keys (renamed JSON attributes)

From time to time it can happen, that the evcc decide to rename attributes in the json. In order to support such a renaming (without the need to rename the entities in HA I have implemented key_alias feature. Let's keep fingers crossed, that this did not mess up something else. 💯

Consumption - Mobility and Transportation - Python
Published by marq24 11 months ago

ha-evcc - Allow to alter EVCC-Server host/URL via Configuration

issue #116

Consumption - Mobility and Transportation - Python
Published by marq24 12 months ago

ha-evcc - Websocket is now default + bugfixes

Websocket is the new default

Looks like the websocket works stable - let's use it as default

Fix for #112 (no data available)

If there is no data - well - then there is obviously no data... but the code should handle this (and don't throw a error)

Fix for #113

New keys had been logged - but not been added - so if in evcc a new value appeared, this value was not present in ha (this 'should' be fixed now)

'Clarified' installation instructions for generation TikTok

I am really starting to get mad about the users reporting, that installation does not work, when they specify the HA-URL (with an alternate port)...

Consumption - Mobility and Transportation - Python
Published by marq24 12 months ago

ha-evcc - Bugfix release

Fix for #112 (no data available)

If there is no data - well - then there is obviously no data...

'Clarified' installation instructions for generation TikTok

I am really starting to get mad about the users reporting, that installation does not work, when they specify the HA-URL (with an alternate port)...

Consumption - Mobility and Transportation - Python
Published by marq24 12 months ago

ha-evcc - Support for multiple EVCC Instances & Celebrate default HACS repository [+Hotfix]

Support for multiple EVCC Instances & Celebrate default HACS repository

This release fix an issue I have discovered this morning when testing using multiple evcc servers from a single HA instance - looks like nobody tried before - or did not bother... in any case this is now fixed by setting a correct device-id identifier object.

Also since yesterday this integration is now part of the default HACS repository - which makes adding this to HACS as custom repository obsolete.

Hotfix - tuple_idx Sensors had been broken

#107 Thanks to @mpw96 for your report - this slipped though my attention...

Consumption - Mobility and Transportation - Python
Published by marq24 12 months ago

ha-evcc - FIX for multiple EVCC Instances & Celebrate default HACS repository

This release fix an issue I have discovered this morning when testing using multiple evcc servers from a single HA instance - looks like nobody tried before - or did not bother... in any case this is now fixed by setting a correct device-id identifier object.

Also since yesterday this integration is now part of the default HACS repository - which makes adding this to HACS as custom repository obsolete.

Consumption - Mobility and Transportation - Python
Published by marq24 12 months ago

ha-evcc - Data update via Websocket communication [experimental]

Websocket FTW!

The EVCC server supporting websocket communication - This allow the server to push data-updates as they happen, which makes polling the data by the integration obsolete.

[!IMPORTANT]
The new new communication layer, is disabled by default - if you want to support the development, I would kindly ask to go to the configuration of the integration and enable the websocket support by checking Use Websocket (experimental) - Polling Interval will be ignored. After a short while the Integration should be reloaded in HA and the integration will listen to the websocket of your configured EVCC server.

If you don't want to try the new feature - the update 'should' not harm your current setup.

[!NOTE]
After the initial stuff has been implemented and is working fine in the past 2 days, I have learned something additional today about how HA can handle/work with web sockets. This have been reflected now in the update [make use of coordinator.async_set_updated_data(...) once data have been received via the web socket]
If you have issues when enabling the new feature, please create an issue in the repository and disable the Websocket support in the configuration of the integration.

Also would be quite nice to get feedback, when the websocket will work for you :-)

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Data update via Websocket communication [experimental]

Websocket FTW!

The EVCC server supporting websocket communication - This allow the server to push data-updates as they happen, which makes polling the data by the integration obsolete.

[!IMPORTANT]
The new new communication layer, is disabled by default - if you want to support the development, I would kindly ask to go to the configuration of the integration and enable the websocket support by checking Use Websocket (experimental) - Polling Interval will be ignored. After a short while the Integration should be reloaded in HA and the integration will listen to the websocket of your configured EVCC server.

If you don't want to try the new feature - the update 'should' not harm your current setup.

[!NOTE]
I have implemented this just in few hours this morning/afternoon - so there are for sure the possibility that something might not work as expected - specially this is my first websocket client implementation. So if you have issues when enabling the new feature, please create an issue and disable the Websocket support in the configuration of the integration.

Also would be quite nice to get feedback, when the websocket will work for you :-)

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Adjustment for upcoming changes in EVCC tariff response objects

I was made aware, that the price attribute in the tariff response object will be renamed to just value in one of the next EVCC releases - so this release will take care about this upcoming change.

When you process one of the new evcc_tariff_* sensor attributes you must also adjust your parser once the attribute will be renamed by EVCC.

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Added pvAction (+CODE), pvRemaining (as Timestamp), and enable-/disableDelay

As requested in #101 this new build tries to support few additional sensors/settings

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - EVCC 0.200+ addons [incl. nightly support + bugfix]

We all are happy with all ne new features introduced in EVCC 0.200+ release. With the 2025.2.2 release of the HA Integration some of the new available fields have been added to this Integration:

• Tariff's for GRID and SOLAR are now accessible via two new sensors (new sensors are disabled by default). The complete range is then available via the sensors attribute(s) - please note, that this data will be updated only every hours to save resources.
• Added some of the new API fields that are related to the Plan feature of EVCC:
  • EffectivePlanTime,
  • EffectivePlanSoc
  • PlanProjectedStart
  • PlanProjectedEnd
  • PlanActive & PlanActiveAlt - please note, that the 'alternative' PlanActive boolean sensor is not enabled by default - it has been added, since I made her locally the experience, that the API value 'planActive' is not always correct (at least IMHO)
• All date related fields (PlanTime, VehiclePlansTime, EffectivePlanTime, PlanProjectedStart & PlanProjectedEnd) are now SensorDeviceClass.TIMESTAMP

...and please don't forget to star the repository and support the development - TIA

---

This release fix #98

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - EVCC 0.200+ addons [incl. nightly support]

We all are happy with all ne new features introduced in EVCC 0.200+ release. With the 2025.2.2 release of the HA Integration some of the new available fields have been added to this Integration:

• Tariff's for GRID and SOLAR are now accessible via two new sensors (new sensors are disabled by default). The complete range is then available via the sensors attribute(s) - please note, that this data will be updated only every hours to save resources.
• Added some of the new API fields that are related to the Plan feature of EVCC:
  • EffectivePlanTime,
  • EffectivePlanSoc
  • PlanProjectedStart
  • PlanProjectedEnd
  • PlanActive & PlanActiveAlt - please note, that the 'alternative' PlanActive boolean sensor is not enabled by default - it has been added, since I made her locally the experience, that the API value 'planActive' is not always correct (at least IMHO)
• All date related fields (PlanTime, VehiclePlansTime, EffectivePlanTime, PlanProjectedStart & PlanProjectedEnd) are now SensorDeviceClass.TIMESTAMP

...and please don't forget to star the repository and support the development - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - EVCC 0.200+ addons

We all are happy with all ne new features introduced in EVCC 0.200+ release. With the 2025.2.2 release of the HA Integration some of the new available fields have been added to this Integration:

• Tariff's for GRID and SOLAR are now accessible via two new sensors (new sensors are disabled by default). The complete range is then available via the sensors attribute(s) - please note, that this data will be updated only every hours to save resources.
• Added some of the new API fields that are related to the Plan feature of EVCC:
  • EffectivePlanTime,
  • EffectivePlanSoc
  • PlanProjectedStart
  • PlanProjectedEnd
  • PlanActive & PlanActiveAlt - please note, that the 'alternative' PlanActive boolean sensor is not enabled by default - it has been added, since I made her locally the experience, that the API value 'planActive' is not always correct (at least IMHO)
• All date related fields (PlanTime, VehiclePlansTime, EffectivePlanTime, PlanProjectedStart & PlanProjectedEnd) are now SensorDeviceClass.TIMESTAMP

...and please don't forget to star the repository and support the development - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Added 'effectiveLimitSoc' (readonly)

As requested in #88 & #89

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Maintenance Release

Minor change to handle HA restart when EVCC-backend is not available

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Simpler implementation to check grid-data-as-object

Thanks @dasadi for your detailed issue #86

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Support for changed JSON structure for Vehicle PLAN (vs. PLANS array)

Thanks to the report #85 from @gorzan14 I was made aware, that the internal structure of the vehicle plan(s) object have been changed recently (well early December 2024 - https://github.com/evcc-io/evcc/pull/16091) - nevertheless in previous evcc versions an active charging plan for a vehicle was included in a plans array object - now this is just a simple single plan object... The adjusted code is able to deal with both versions of evcc.

I am sorry, that we have this kind of compatibility issues - evcc is under active development and there is no simple way to 'listen/watch' upcoming API changes - for the 'last' change I was notified by the evcc team - that was just great (but this type of manual notification can't be guaranteed). So we will probably see this kind of issues & fixes again and again.

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc -

Support for evcc 0.132.1 (release 2025.1.2)

With evcc 0.132.1 the change https://github.com/evcc-io/evcc/commit/65bdb404941483d8340d81c92505741763a4d930 introduced a new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with https://github.com/evcc-io/evcc/commit/e9d67ee0069a3c088ff9ecbb504a3c0108e64d6d, this HA integration became incompatible with the updated evcc version.

The release 2025.1.2 (and this one) make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.

Situations like this will probably occur also in the future, since I (as developer of the HA integration) am not part of evcc team. We are separate projects and obviously the integration rely on functionality provided by evcc. The developers of evcc a really great people who give me all support I could ask for - but nevertheless there is always the possibility of bad luck or bad timing.

Fixing sets option flow config_entry explicitly warning (release 2025.1.2)

Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...

https Support [by @RustyDust] (release 2025.1.3)

When you are running your evcc instance via https you now can simply add the schema https:// as part of your evcc-url during the initial setup of the integration (obviously you should not specify 443 as additional port in this case)

Support for upcoming change in evcc /api/state response (grid data related) (release 2025.1.3)

@andig from evcc made me aware of an upcoming change in the evcc api that would lead to another incompatibility between evcc and the HA integration.

But this time I (hopefully) could adopt the code to the change and make sure that it will work with both implementations (the old=current and the new=future). So you could already update the HA integration and when ever you update evcc you just need a HA restart to allow the integration to 'detect' the change and take appropriate action.

Fix for issue #77 caused by 2025.1.3

Fix for issue #78 caused by 2025.1.4, 2025.1.5, 2025.1.6

Fix for issue #80 caused by 2025.1.7

Credits

• Thanks @RustyDust for providing the https support
• Thanks @andig for sharing the PR https://github.com/evcc-io/evcc/pull/18063 with me - so I was able to prepare the integration code for the upcoming change

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc -

Support for evcc 0.132.1 (release 2025.1.2)

With evcc 0.132.1 the change https://github.com/evcc-io/evcc/commit/65bdb404941483d8340d81c92505741763a4d930 introduced a new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with https://github.com/evcc-io/evcc/commit/e9d67ee0069a3c088ff9ecbb504a3c0108e64d6d, this HA integration became incompatible with the updated evcc version.

The release 2025.1.2 (and this one) make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.

Situations like this will probably occur also in the future, since I (as developer of the HA integration) am not part of evcc team. We are separate projects and obviously the integration rely on functionality provided by evcc. The developers of evcc a really great people who give me all support I could ask for - but nevertheless there is always the possibility of bad luck or bad timing.

Fixing sets option flow config_entry explicitly warning (release 2025.1.2)

Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...

https Support [by @RustyDust] (release 2025.1.3)

When you are running your evcc instance via https you now can simply add the schema https:// as part of your evcc-url during the initial setup of the integration (obviously you should not specify 443 as additional port in this case)

Support for upcoming change in evcc /api/state response (grid data related) (release 2025.1.3)

@andig from evcc made me aware of an upcoming change in the evcc api that would lead to another incompatibility between evcc and the HA integration.

But this time I (hopefully) could adopt the code to the change and make sure that it will work with both implementations (the old=current and the new=future). So you could already update the HA integration and when ever you update evcc you just need a HA restart to allow the integration to 'detect' the change and take appropriate action.

Fix for issue #77 caused by 2025.1.3

Fix for issue #78 caused by 2025.1.4, 2025.1.5, 2025.1.6

Credits

• Thanks @RustyDust for providing the https support
• Thanks @andig for sharing the PR https://github.com/evcc-io/evcc/pull/18063 with me - so I was able to prepare the integration code for the upcoming change

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc -

Support for evcc 0.132.1 (release 2025.1.2)

With evcc 0.132.1 the change https://github.com/evcc-io/evcc/commit/65bdb404941483d8340d81c92505741763a4d930 introduced a new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with https://github.com/evcc-io/evcc/commit/e9d67ee0069a3c088ff9ecbb504a3c0108e64d6d, this HA integration became incompatible with the updated evcc version.

The release 2025.1.2 (and this one) make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.

Situations like this will probably occur also in the future, since I (as developer of the HA integration) am not part of evcc team. We are separate projects and obviously the integration rely on functionality provided by evcc. The developers of evcc a really great people who give me all support I could ask for - but nevertheless there is always the possibility of bad luck or bad timing.

Fixing sets option flow config_entry explicitly warning (release 2025.1.2)

Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...

https Support [by @RustyDust] (release 2025.1.3)

When you are running your evcc instance via https you now can simply add the schema https:// as part of your evcc-url during the initial setup of the integration (obviously you should not specify 443 as additional port in this case)

Support for upcoming change in evcc /api/state response (grid data related) (release 2025.1.3)

@andig from evcc made me aware of an upcoming change in the evcc api that would lead to another incompatibility between evcc and the HA integration.

But this time I (hopefully) could adopt the code to the change and make sure that it will work with both implementations (the old=current and the new=future). So you could already update the HA integration and when ever you update evcc you just need a HA restart to allow the integration to 'detect' the change and take appropriate action.

Fix for issue #77 caused by 2025.1.3

Credits

• Thanks @RustyDust for providing the https support
• Thanks @andig for sharing the PR https://github.com/evcc-io/evcc/pull/18063 with me - so I was able to prepare the integration code for the upcoming change

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc -

Support for evcc 0.132.1 (release 2025.1.2)

With evcc 0.132.1 the change https://github.com/evcc-io/evcc/commit/65bdb404941483d8340d81c92505741763a4d930 introduced a new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with https://github.com/evcc-io/evcc/commit/e9d67ee0069a3c088ff9ecbb504a3c0108e64d6d, this HA integration became incompatible with the updated evcc version.

The release 2025.1.2 (and this one) make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.

Situations like this will probably occur also in the future, since I (as developer of the HA integration) am not part of evcc team. We are separate projects and obviously the integration rely on functionality provided by evcc. The developers of evcc a really great people who give me all support I could ask for - but nevertheless there is always the possibility of bad luck or bad timing.

Fixing sets option flow config_entry explicitly warning (release 2025.1.2)

Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...

https Support [by @RustyDust]

When you are running your evcc instance via https you now can simply add the schema https:// as part of your evcc-url during the initial setup of the integration (obviously you should not specify 443 as additional port in this case)

Support for upcoming change in evcc /api/state response (grid data related)

@andig from evcc made me aware of an upcoming change in the evcc api that would lead to another incompatibility between evcc and the HA integration.

But this time I (hopefully) could adopt the code to the change and make sure that it will work with both implementations (the old=current and the new=future). So you could already update the HA integration and when ever you update evcc you just need a HA restart to allow the integration to 'detect' the change and take appropriate action.

Credits

Thanks @RustyDust for providing the https support
Thanks @andig for sharing the PR https://github.com/evcc-io/evcc/pull/18063 with me - so I was able to prepare the integration code for the upcoming change

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Support for evcc 0.132.1

With evcc 0.132.1 the change https://github.com/evcc-io/evcc/commit/65bdb404941483d8340d81c92505741763a4d930 introduced the new property chargerPhaseSwitching and removed the chargerPhases1p3p... Even if this adjustment has been rolled back already with https://github.com/evcc-io/evcc/commit/e9d67ee0069a3c088ff9ecbb504a3c0108e64d6d, the current release version of evcc is incompatible with the HA integration.

This new release make sure, that the integration will work with chargerPhases1p3p and/or chargerPhaseSwitching - so that what ever will be released in evcc in the near future, the integration should be able handle it.

Also this new build fix a small issue reported Detected that custom integration 'evcc_intg' sets option flow config_entry explicitly...

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Removed hardcoded area 'Basement'

No clue why I implement HA integration stuff during the Dart-WM final... Go Luke!

In previous releases the 'Area' was hardcoded to Basement - this new build allow you to configure/select the area - as requested in #57

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - €/kWh max limits set to 2.5€ [and for none € countries to 25.0]

First of all HappyNewYear to you all...

I was made aware, that the current implemented cost limit number selectors have the limitation, that they will only work for € (some sort of) - So the BATTERYGRIDCHARGELIMIT and the SMARTCOSTLIMIT Sensors will come with a max value of 2,50€ - and for none € countries the limit will be 10 times higher.

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Added BatteryBoost switch [per Loadpoint] (working)

The initial implementation of the new switch did not work with the 'latest' release of evcc https://github.com/evcc-io/evcc/releases/tag/0.132.0 cause of a tiny bug in evcc that will be fixed with the PR https://github.com/evcc-io/evcc/pull/17951.

But instead of waiting for the next evcc release (which will be available for sure quite soon), I have implemented a simple workaround (using 0 & 1 instead of true & false at the API endpoint).

All the best for the new year!

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Added BatteryBoost switch [per Loadpoint]

Please note, that this switch is disabled by default (since not all evcc installations will support this additional switch - including mine) - please let me know, if this implementation will work for you - TIA

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Bugfix release

Fixing #48 - checking for None value

Consumption - Mobility and Transportation - Python
Published by marq24 about 1 year ago

ha-evcc - Remove smart cost limit via button

Button to delete current smart cost limit setting. Please note, that you must 'activate' the new button in the Integration settings before it become visible the UI

Solving issue https://github.com/marq24/ha-evcc/issues/43

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Bugfix for upcoming HA2024.11.x

Please update the integration before updating to HA2024.11.x

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Support for multiple PV power values

If you have configured multiple PV sources in your evcc, in previous versions only the overall sum was available. In the new release an additional sensor (1-4) have been implemented in order to provide PV Power per configured source (up to 4 - let me know, if you need more).

Please note, that the new Entities are disabled by default and need to be manually activated once.

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Added Vehicle Odometer (& ClimaterActive, WelcomeActive)

Thanks @mpw96 for providing this feature (I just two other diagnostic values that I haven't implemented/saw when I made the initial implementation)

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Fix for Duration values (v0.131.1) related

API provide data is seconds - added preferred display unit minutes (get rid of factor)...

https://github.com/marq24/ha-evcc/issues/33

Thanks @d3ni3 for your report

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Added Statistics (with fixed typo)

Typofixed Version - Even if the sun is shining today, I have implemented https://github.com/marq24/ha-evcc/discussions/21 this morning. Please note, that most of the statistic sensor entities are disabled by default. E.g. if you are interested in the, 30d, 365d or thisYear stats you must manually activate the corresponding sensors.

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Added Statistics

Even if the sun is shining today, I have implemented https://github.com/marq24/ha-evcc/discussions/21 this morning. Please note, that most of the statistic sensor entities are disabled by default. E.g. if you are interested in the, 30d, 365d or thisYear stats you must manually activate the corresponding sensors.

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Fixing Vehicle *vehicle_plans_time

Fixing display of *_vehicle_plans_time (*_plans_time) value(s).

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Added 'missing' batteryGridChargeActive & batteryGridChargeLimit

Thanks @MarcelMertens for reporting it [I hope cost limit unit will match]

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Supporting default HA sensor customization's

By default HA sensors can be customized by the user [mainly this are unit factor's and the display precision]. This feature was totally ignored by previous implementations of this integration and with this release its finally supported.

The change implies, that for some of the existing sensors the default display (precision) have been adjusted - if you dislike the new display format you can now simply adjust it the sensor settings.

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Keep default PrioriySOC options, when BufferSOC is 0%

Fix for #17

For what ever reason in my local evcc installation it's not possible to set BufferSOC value to 0% - but looks like that @swa72 just have exactly this scenario configured - so the code that adjust the select options have been modified in order to deal with the situation, that BufferSOC have the value of 0% [how ever this can be achieved]

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Just more logging

trying to find root cause of reported issue #17

[make sure that you update to latest HACS to be able to install pre-releases again]

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - The 'smartcostlimit' attribuet have now a step size of 0.5 cent

No idea, if in previous evcc versions the step size was 1 cent or if this issue was present since the first release of this integration - in any case step size have been adjusted to 0.5 cent

Thanks @JonisK for reporting the issue

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Adjustments for latest HA release (get rid of warning)

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Make sure that Grid imported (Netzbezug) is only increasing

Since multiple users have reported issues that the GridImported Sensor can fall down to "null"/"0"/"unavailable" [https://github.com/marq24/ha-evcc/discussions/7] this new build checks, if this value is available and larger then the previous sensor value.

Enjoy your Sunday

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Fix for #9 - Wrong state class for SessionEnergy & ChargedEnergy

Please note, that it might be required to rest/fix the long term stats via http://[YOUR-HA-IP]:[PORT]/developer-tools/statistics for the corresponding entities.

Thanks to @Roeland54 for reporting this issue #9

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Just maintenance

Just discovered that binary sensors can have device classes - so just let use them

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Added missing unit for Loadpoints Total import from Grid value

Addressing discussion issue #7 (might be that the unit is still incorrect)

Consumption - Mobility and Transportation - Python
Published by marq24 over 1 year ago

ha-evcc - Fix: Detected blocking call to open inside the event loop by custom integration

Consumption - Mobility and Transportation - Python
Published by marq24 almost 2 years ago

ha-evcc - Fixing dependant 'Select' options

#3 -> #4

Affected Sensors:

• Min/Max Current [per loadpoint]
• HomeBattery SOC values

Consumption - Mobility and Transportation - Python
Published by marq24 almost 2 years ago

ha-evcc - BREAKING CHANGE! - All entities have been renamed - please update with care!

This is a BREAKING CHANGE - update with care!

My apology to all early adopters - based on the discussion here #2 there was the "need" to adjust all entity ids of this integration - the easiest way to update might be to remove the current configuration and just reinstall it (just to make sure that all old entities are gone).

The new entity ids will start (as before) with the name you have selected during initial setup, but then the next part will be the loadpoint name followed by the "camal_case to snake_case converted" json object name.

Yes - this will break all possible automation you have already build based on this integration - but at the end it's better to break early.

Thanks @ThomDietrich for your very valuable and constructive feedback!

Consumption - Mobility and Transportation - Python
Published by marq24 almost 2 years ago

ha-evcc - Implemented 1'st Enhancement Request

Implemented #1

The Battery Mode is now available as additional entity - please note, that the value is translated by default - if you want to have the original (source) value from the API (unknown|normal|hold|charge), you can activate the additional available 'Battery Mode [CODE]' Entity.

Implemented additional evcc-Site entities

• auxPower
• batteryPower
• batterySoc
• gridCurrents
• gridPower
• homePower
• pvPower
• batteryCapacity
• tarifGrid
• tarifPriceHome

Consumption - Mobility and Transportation - Python
Published by marq24 almost 2 years ago