-
Notifications
You must be signed in to change notification settings - Fork 22
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
Demand Tariff Support (Time of use) #56
Labels
Comments
Good thinking! Since both the money view and the energy view are closely related, this also has to be done for the energy view. You could say that users currently supply their This is also a better solution for #57. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I understand that the money view currently doesn't support having variable tariffs based on time of use, but would like to propose a design solution for allowing it to do so.
I don't have that much programming experience, but here's how I'd envisage it in my head. The logic should check if
energy_consumption_rate
orenergy_production_rate
are List/Dict types. If they are, it should look for therate
andentity
variables under each, then run calculations based off those.An example of the adapted configuration would be:
So this would equate to:
consumption_shoulder
sensorconsumption_peak
sensorconsumption_offpeak
sensorGenerating these sensors with templates shouldn't be particularly difficult, and can easily have a combined sensor too. Correct me if I'm wrong, but I believe this is likely the most elegant solution for this problem.
The text was updated successfully, but these errors were encountered: