DST Issue

[dmelliott20]

Looks like the pricing is out by an hour, anyone else having the same issue?

[markgdev]

You’re completely right, everything on the backend is in GMT rather than BST. I need to revisit how I deal with that, I think the agile api can provide local time but I haven’t had time to look at it.

If you use the rates card it converts to local time/BST for display in Lovelace.

[dmelliott20]

Thanks. So the firing of the timers are unaffected by this?

…

Sent from my iPhone On 9 Jun 2020, at 19:07, Mark Gardner <notifications@github.com> wrote:  You’re completely right, everything on the backend is in GMT rather than BST. I need to revisit how I deal with that, I think the agile api can provide local time but I haven’t had time to look at it. If you use the rates card it converts to local time/BST for display in Lovelace. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADELRFPZM76N5Y6OZF5GGRTRVZ245ANCNFSM4NZNBIOA>.

[markgdev]

Nope, they should be all good. The only thing that it should affect is if you specify requirements in a timer, they will need to be GMT, which is obviously a bit rubbish when daylight savings ends and they’ll need changing. Hopefully I’ve got everything changed to local time by then though!

[dmelliott20]

Thanks!!

…

Sent from my iPhone On 9 Jun 2020, at 20:40, Mark Gardner <notifications@github.com> wrote:  Nope, they should be all good. The only thing that it should affect is if you specify requirements in a timer, they will need to be GMT, which is obviously a bit rubbish when daylight savings ends and they’ll need changing. Hopefully I’ve got everything changed to local time by then though! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADELRFOLDMBQFMFBQAAUCFLRV2F3VANCNFSM4NZNBIOA>.