Replies: 2 comments
-
Hello. I'm not really following your table. Are you looking for a continuous 2 hours, or intermittent 2 hours? Which slots would you expect the sensor to come on for? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Closing as it doesn't make sense. Replaced by #430 . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi! I have the following scenario: I want the sensor to turn on on the cheapest 2 hours for which the current_average_cost is lower than my export rate.
This is not the same thing as a sensor that turns on on the cheapest two hours, and then setting the condition on top of it in an automation. For example, suppose that my appliance runs for 2 hours, and I have rates as in the following table:
You can see that evaluating a condition on top of the sensor only activates 3 slots, whereas having a sensor with a built-in condition activates 4, which is what I need to run my appliance at the cheapest possible cost.
Hope it makes sense... :-)
Beta Was this translation helpful? Give feedback.
All reactions