Replies: 1 comment 3 replies
-
|
I have been doing some further investigation and found that the number of slots aren't available to do the calculation: |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Hello and sorry that you've encountered this issue. May I assume that you're on OE agile? If you are, then the default window that is evaluated (midnight to midnight) won't be compatible with the data available. It is advised in this scenario to set you to/from times to something within a standard agile window (e.g 16:00-16:00 or 23:00-23:00). Or you can set the end time to 23:00 (if you don't mind never taking 23:00-00:00 into consideration). In the next update, which in trying to find the time to finish, there will be the ability to evaluate with partial data which means that sensors can evaluate without the full data window being available. |
Beta Was this translation helpful? Give feedback.
-
|
I am on OE Agile. Yes partial data would be brilliant. Since I dont have devices like a washing machine etc, that are smart, I was trying to use it to at least notify me of the cheapest windows. I have got a work around from your Octopus integration to get me the best time for 1/2/3 hour windows within the next X (hours a device needs to run for) value. But the target time frames, unless I set up multiple different sensors, one looking at 6 hours ahead then another n+1 hours ahead etc. I will wait for a stable release of partial date until then. |
Beta Was this translation helpful? Give feedback.
-
|
The partial data config option is available as part of the latest release. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have setup the blueprints and added my sensors to the entities. No matter what I try I cannot force it to update. I created a standard Target Timeframe Sensors with 1h 2h and 3h slots. the last time it updated was 16:01. I assume the rates weren't available yet but I kind of expected it to recalculate when they did become available. Nonetheless, even now the rate shows the date of best time for 12th (today is 13th).
The entity
sensor.target_timeframes_octopus_energy_data_source_last_updatedI can see rates from the 13th. But it doesn't seem to be triggering mybinary_sensor.target_timeframes_octopus_energy_best_fixed_1hwith updated times.What am I missing
Beta Was this translation helpful? Give feedback.
All reactions