Replace YAML with UI instructions on tariff and vehicle feature pages#1107
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of the series replacing
evcc.yamlsnippets in the features section with UI instructions (follow-up to #1106).co2 (en/de): CO₂ data source now via Configuration → Tariffs & Forecasts → Add forecast → Add CO₂ forecast, provider example Grünstromindex.
dynamic-prices (en/de): grid tariff via Configuration → Tariffs & Forecasts → Add tariff → Add grid import tariff — fixed price (Fixed Price), time-based zones (Time-based Tariff, Default price, Add zone), dynamic providers (e.g. Tibber). Currency pointer to Configuration → General → Currency. Drive-by: "EVCC" → "evcc" in the smart feed-in section.
vehicle (en/de): offline vehicle (Generic vehicle (without API)), online vehicle (manufacturer selection + account credentials), loadpoint default vehicle (Vehicles → Default vehicle), RFID and Plug & Charge identifiers via the vehicle's RFID identification field — the identifier is read from the charging point card in the UI, the
evcc chargerCLI mention is gone.All labels match the UI translations in
evcc-io/evcci18n/{en,de}.jsonand template product names.Deliberately excluded:
external-control.mdxandloadmanagement.mdx(circuits are not form-based yet) — separate PRs later.🤖 Generated with Claude Code