UK BST end. Timed events have stopped working

#1

In the UK we went from BST to GMT in the early hours of this morning,
Since then my pistons with timed events have stopped running.
Anyone else having issues?
Here is a very simple one for my porch light.

image
image.png1178×683 33.8 KB

Logging was not on so I cannot provide any information there…
EDIT. If I test it it runs and the light turns on.
EDIT 2. In the webCoRE app I have completed the following.
Disable all pistons.
Enable all pistons.
Clean up and rebuilt data cache.
Not sure if this has helped.
Time will tell.

Problem with DST?
#2

Mine are still running, but one hour early.

#3

You’ll find that they reschedule correctly for the next run.

The ones firing early would have been scheduled before the clocks went back… after firing they would have scheduled themselves for the next run, using the corrected time.

#4

Thanks Robin.

#5

Yeah. Same for me. Have an event to wake me up at 6am - imagine my suprise when it fired at 5am… then 6am again!

Glad to hear they’ll be fixed on the next run!

EDIT: Could there be a feature put in where this is automatically done (or a button where we can do this ourselves?). That way we can put something in our diaries to remember to run it on the date prior to the clocks going back.

#6

Just got home and none of my announcements or heating pistons ran.
Went into them all and did a test. They ran as they should.
Now going out again to see if they are now OK.
@ady624 did you see @Hilly_2015 's request above?
Might be an idea if there was a button or something in the app that could be pressed to run a test of all the active pistons.
Maybe something that could be done in a piston so perhaps the following can be done.

Cancel all pending tasks on all pistons.
Test all pistons.

Would that cure any DST issues?

#7

@Robin I knew it was down to the clock change, but I had no idea what to do to fix it. Thanks for the information.

#8

None of my mode changes are running.
Will pause, resume and hit test button.
Think I will do it for all my pistons to see if this resolves my issues.

#9

Yeah I’ve been struggling with mode changes in the last 24 hours. Thought it was just me. Like you, I think I’ll pause, resume and test all my pistons and see what happens.

Ideally it would be good for these checks to be built into WebCore. If it helps, here are the dates when the clocks change here in the UK up until 2029…

FORWARD

2018 - Sunday, 25 March, 01:00
2019 - Sunday, 31 March, 01:00
2020 - Sunday, 29 March, 01:00
2021 - Sunday, 28 March, 01:00
2022 - Sunday, 27 March, 01:00
2023 - Sunday, 26 March, 01:00
2024 - Sunday, 31 March, 01:00
2025 - Sunday, 30 March, 01:00
2026 - Sunday, 29 March, 01:00
2027 - Sunday, 28 March, 01:00
2028 - Sunday, 26 March, 01:00
2029 - Sunday, 25 March, 01:00

BACK

2018 - Sunday, 28 October, 02:00
2019 - Sunday, 27 October, 02:00
2020 - Sunday, 25 October, 02:00
2021 - Sunday, 31 October, 02:00
2022 - Sunday, 30 October, 02:00
2023 - Sunday, 29 October, 02:00
2024 - Sunday, 27 October, 02:00
2025 - Sunday, 26 October, 02:00
2026 - Sunday, 25 October, 02:00
2027 - Sunday, 31 October, 02:00
2028 - Sunday, 29 October, 02:00
2029 - Sunday, 28 October, 02:00

EDIT: After doing the above, the ‘countdown timer’ for the mode changes on the WebCore dashboard have returned. They weren’t there before.

#10

My sunset timed routine didn’t fire today after the clcoks went back so I guess this problem isn’t fixed yet.