Requesting the extended Vehicle can have unexpected consequences
As reported in #282 the enabled "Request Extended Vehicle data" can have some serious consequences to the health of your Hyundai EV (at least that's what I have understood so far).
In previous releases the HA integration requested (in the configured update interval) the extended vehicle data (like SOC) from the (undocumented) evcc-configuration endpoints. This feature had been requested multiple times in the past (and till the feature was introduced in the integration there had been documentation available how to request extended vehicle data via the HA REST-Sensor integration). When the data will be requested from evcc it highly depends on the underlying implementation where and how this data will be requested from the vehicle. At least in the case of Hyundai this will cause instant communication with the vehicle itself. So depending on the configured HA integration update interval this could cause some sort of DOS-Attack (at least the vehicle infrastructure would not been able to handle that).
Anyway - It seams to be smarter to disable the new functionality by default and add additional warning information what could be possible consequences when enable the functionality in the configuration dialog.
Please note, that all this only affect you as a integration user, if you have specified your evcc-admin password 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