IO slots and 30 min windows (Yorkshire rounding) #724
SteveDrakey
started this conversation in
General
Replies: 1 comment
-
I have created a simple template sensor todo this :) |
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
-
"Occasionally, when you stop charging, the current charge slot might get interrupted. However, as per the Octopus FAQ, you still benefit from the lower rate for the entire 30-minute window. For example, if you unplug at 15:01, you enjoy the cheaper electricity rate until 15:30. Being from Yorkshire, I can't overstate how important these extra 29 minutes are!
Upon examining the current_rate entity, it appears to adhere to this rule. It seems to update at the 30-minute mark, as shown in this screenshot:
And here's how it looks at the slot's end:
Currently, my automation relies on the slot end, but I'm considering switching to the current_rate entity. However, I'm not keen on hardcoding values, like setting a rule that below 10 means a cheap rate. It doesn't quite sit right with me.
Is there another way within the integration to implement what I'd call 'Yorkshire rounding', avoiding hardcoded values while still making the most of the cheaper rates?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions