Vehicles: remove title/icon from yaml config (BC)
This PR removes the special case of vehicle having their "own" title and icon instead of title/icon being part of the device meta data. This has the following consequences:
- title/icon configuration via yaml is no longer possible- it is via config UI
- vehicle API nick names are removed (it was never clear if an API or given title had preference)
- this supported better OAuth user experience for https://github.com/evcc-io/evcc/pull/24264
TODO
- [ ] remove UI special casing @naltatis
@andig any chance we can keep supporting the deprecated yaml title/icon for a couple of releases? Since config ui is not marked as stable yet, there will be no non-experimental way to set a vehicle title. Having a vehicle title is much more critical from a user-base-perspective than meter titles.
If we can't support both, I'd say we should hold this PR until config ui is stable.
this supported better OAuth user experience
Is the new vehicle title api really necessary for this? Publishing a vehicle name would also be fine for UI. We have everything there to perform a lookup for title.
Is the new vehicle title api really necessary for this?
What new api?
The ability to get the title from a vehicle via go api (this PR).
If the main objective is to provide a better name for the OAuth flow in UI the name of the vehicle would be sufficient.
I donβt understand π
on hold until config ui is stable since we loose ability to configure vehicle title in our recommended setup