evcc-io
Config UI: release and final touches
depends on https://github.com/evcc-io/docs/pull/957 fixes https://github.com/evcc-io/evcc/issues/25910#event-21436552030
Prepare config ui for becoming the new recommended way of configuring evcc 🥳
👩🔬 remove experimental conditions/notes 👋 drop the evcc.yaml vs. config ui tradeoff explainer 🪧 prominent "start with a charger" message (see screenshot) 🔌 integrations: unconfigured integrations are shown hollow style (like add buttons) 🔆 shm integration is shown unconfigured when not customized (addresses https://github.com/evcc-io/evcc/issues/24277) 🚀 remove experimental flag for battery boost 🧪 move experimental toggle to a dedicated modal (config) and explain better
Todos
- [x] adjust e2e tests (drop enable experimental)
- [ ] prepare docs, drop experimental notes (e.g. linux) https://github.com/evcc-io/docs/pull/957
- [x] move unconfigured tariff card to hollow style
- [x] clarify sponsor token ui
Screenshots
start with loadpoint hint
unconfigured integrations
I´m still missing the configuration of "log.level" within Config UI. That is the last point in my yaml 😃
I´m still missing the configuration of "log.level" within Config UI.
Good point. I've created an issue.
I´m still missing the configuration of "log.level" within Config UI. That is the last point in my yaml 😃
Bei mir sind es der Log Level und die plant ID. Log Level ist nun geplant. Die plant ID könnte ich auch als Umgebungsvariable bei docker definieren. Ansonsten wäre die Frage, ob diese eventuell auch in der UI geplant wird.
Die plant ID könnte ich auch als Umgebungsvariable bei docker definieren.
Yes, I'd say being able to set this via environment variable is fine. It's a quite technical topic. I don't see a dedicated UI for this. Using the evcc.yaml will still be possible for the foreseeable future.