Rate tracker fail pull

[rory2409]

Describe the bug

It’s all been working flawlessly but the clocks change I think has resulted in no rates being pulled onto the current rate tracker. All other features working

Reproduction steps

Clock change?

Expected behaviour

To pull cheapest rates through the day

Tariff Code

E-1R-AGILE-23-12-06-E

Integration Version

Latest

Home Assistant Version

Latest

Fresh Install?

Not specified

Home Assistant Logs

12_Home_Assistant.log

Confirmation

• I confirm that I cannot find my solution within the documentation
• I confirm that I cannot find my solution within the FAQ

[rory2409]

[BottlecapDave]

Hello and sorry for the late response. Is this still happening? There was an issue with target rate sensors not refreshing in certain scenarios which should be fixed in v10.2.0.

[rory2409]

I’m on 10.1.4 and no updates are showing yet I’ll keep you posted once i receive the update.

…

On Sat, 6 Apr 2024 at 15:55, David Kendall ***@***.***> wrote: Hello and sorry for the late response. Is this still happening? There was an issue with target rate sensors not refreshing in certain scenarios which should be fixed in v10.2.0. — Reply to this email directly, view it on GitHub <#813 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMV25BDJKET3ZO5DIUZLGLDY4AEGTAVCNFSM6AAAAABFQOMJ22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGEYTANZXGM> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[rory2409]

Update received seems to be working however it’s an hour out like the other bugs listed

[BottlecapDave]

Ok, as this issue is now fixed, I'll close this issue :)

[rory2409]

Unfortunately issues remain

[seanmaskey]

Hi
I had a similar issue I think; attributes were correct on UTC until 23:00/midnight when they became "unknown". I had set the start & end times in the individual configs to 2300. changing that to 19:00 solved the problem. wasn't sure if it was coincidental as other things were changing around the same time.
S

[rory2409]

I’ve just changed to 1600 and now it is showing on when it should be off as no time matches now time hope this makes sense

[BottlecapDave]

@rory2409 I'm not too sure what you're showing here or what you're trying to describe. Please update to v10.2.1 and see if this fixes the issues you're experiencing.

If it doesn't fix your issue, please supply

• The target times that have picked by the sensor (which are displayed in UTC format)
• A screenshot of the entity in the history tab highlighting when the sensor turns on/off, ideally with annotations of comments on when you feel it should go on/off.

@seanmaskey I believe this was related to #815, which was fixed as part of v10.2.1