-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Target rates seem to be showing time slots from previous period #814
Comments
Yep same here |
Same here |
Seems to have corrected itself after 5pm
…On Sun, 31 Mar 2024 at 17:00, Markt ***@***.***> wrote:
Same here
—
Reply to this email directly, view it on GitHub
<#814 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE5PC2G347XKLKZSPPQKDGLY3AXJBAVCNFSM6AAAAABFQQLBPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYHAYDMMRXHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
same today -target rates only appeared after 5PM |
Hello and sorry for the late response. Target rate data relies on the underlying rate information being available. If the rate data doesn't update to include the new agile pricing (i.e. because it's late), then new rate times won't be calculated. This can be determined by a couple of attributes as per the docs.
The last evaluated is just when HA last evaluated the state of the entity (same as native last_updated before I knew this existed). As the target rates corrected, I suspect this was the issue, so closing. |
Describe the bug
I have a target rate set up from 4pm to 4pm. Target hours is set to 2.5 and the time is now 16:37. Last evaluated is showing as 16:38:45 but the target slots are showing as before this time.
Reproduction steps
Update target hours to any number and it still shows slots from before 4pm.
Expected behaviour
Show slots from 4pm today onwards.
Tariff Code
Agile
Integration Version
Latest
Home Assistant Version
Latest
Fresh Install?
Not specified
Home Assistant Logs
N/A
Confirmation
The text was updated successfully, but these errors were encountered: