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