-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic Tariffs includes time-dependent tarrifs, clarification of documentation #563
Comments
@gijs007 thanks for this feedback. Are you talking about https://docs.evcc.io/en/docs/devices/tariffs or the still untranslated Feature pages https://docs.evcc.io/en/docs/features/plans and https://docs.evcc.io/en/docs/features/dynamic-prices ? |
I'm referring to the untranslated feature pages, I used Google Translate for this. I assume the German text is in essence the same ;) |
Ok, thanks for the clarification. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The "dynamic tariffs" term is a bit confusing, as this wording can be associated with dynamic energy prices (e.g. from Tiber or other energy providers). Instead of time-fixed energy prices, which are still commonly used.
Furthermore, the dynamic tariffs page does not include time-depended charging in the initial description of this feature:
"If you have an electricity tariff with flexible electricity prices like Tibber or Awattar , you can optimize your network charging with evcc."
Only at the bottom of the page the description mentions: "If a time-dependent or dynamic electricity tariff is configured, the planning algorithm automatically selects the cheapest hours for charging."
Users who don't take the time to read the whole page, might think that the Time-dependent pricing is not used to optimize the charging (and instead is only used to calculate the pricing).
On a side note: The Charge Planner page also refers to the term Dynamic Tariffs, but doesn't mention that Time-dependent charging is included here.
The text was updated successfully, but these errors were encountered: