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...