When you are providing the integration your evcc password (so that the configuration could be accessed) you probably already have noticed since a couple of evcc releases, that there is a warning about an endpoint that can't be reached (at least that's the case for me).
[custom_components.evcc_intg.pyevcc_ha] _do_request() - 'res.status == 400 content: {"error":"not available"} [caused by GET http://[HOST]/api/config/devices/circuit/main/status]
For whatever reason the objects/names returned by /api/config/devices/circuit does not provide a /api/config/devices/circuit/{name}/status (any longer). I must admit, that I can't remember, if this was always the case, or if this status endpoint was recently removed or never existed.
With this release the devices/circuit configuration will be no longer accessed.
Important
Sill - after you update your evcc server to v0.316
With the latest evcc release the names of the loadpoint modes have changed. This is already supported by this HA integration for quite a long period of time. Nevertheless after you have updated evcc to v0.316 you must restart the integration, so that the adjusted structure in the API can be detected (and an additional loadpoint entity) will be added.
Please consider supporting me
Thanks to everybody who have already supported me in the past weeks or month that is really highly appreciated! Sometimes it has been a though journey. To the other users of this integration: 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