Sunrise/Sunset clocks going forward

[Mapantz]

Hi, I had a little message on my PC this morning saying that the clocks had gone forward but that my PC didn't change it .. i have no idea why, i didn't get the problem when they went back.

Anyway, i've just noticed the the sunrise/sunset/moonrise/moonset times are now all an hour behind, do i need to wait another 24 hrs or something?

Cheers.

[steve]

It updates on the hour.

[Mapantz]

It updates on the hour.

I guess there's a problem then? They have been an hour out and they've not updated.

[steve]

I guess there's a problem then?

I guess so. Mine updated automatically as always. If you changed your PC clock before 1500 (BST) then it should have updated the sunrise and sunset times at 1500. It's hard to see how it couldn't have, assuming your PC settings are correct. You could try restarting Cumulus, but the update that it does when it starts up is exactly the same as the one it does on the hour.

My guess would be that your PC is still on GMT.

[Mapantz]

I saw the message on the PC at 9:30am about it not changing, so i did it manually. I restarted Cumulus but nothing changed.

I have just solved it now though, i clicked the message about daylight saving and it put my clock forward by another hour and then i had to manually move it back one hour. It seems i didn't have the clock set to move forward automatically and if you do it manually, Cumulus doesn't pick it up.

[steve]

If you manually moved your PC clock forward by one hour, then that is all you are doing - changing the time and not the DST setting - and there is nothing for Cumulus to pick up; your clock is showing the correct time BST but you are still on GMT. So Cumulus shows sunrise/sunset etc in GMT.

[gluepack]

Not sure I quite understand.

PC, weather station and Cumulus console all show correct current local time. WU RapidFire, desktop gadget, silverlight app. all show current local time.

However, WU and PWSWeather graphs show an hour behind.

Also, despite the graphs being an hour behind, WU tabular data shows to current local time but PWSWeather data history shows to an hour behind.

Hopefully, everything will correct by tomorrow, lol?

Oh, also, not sure if it is to do with the time change or not but my partner, who has a Nexus 7 hasn't been able to get the AccuWeather app to work today "unable to connect to server".

[steve]

My WU data and graphs are both showing GMT+1 (which is current local UK time). My PWS data and graphs are both showing GMT. I've heard it mentioned before that PWS Weather don't handle DST properly.

Cumulus sends data to both with timestamps in GMT/UTC. If you turn on the debug log, you can look at the time stamps that it's sending. Given that your WU and PWS tabular data are both showing the expected times (given the PWS DST issue) then it presumably is sending then correct timestamps, and your only unexplained issue is the WU graphs, so you would have to ask WU about that. I see the same thing as you when looking at your WU graphs. I suspect it's because it's still the same day that the clock changed - note that there is no gap or flat line in the graph for an hour.

[gluepack]

Well, that is weird.

WU is back on track with current time and data and there is an hour of data missing between 03 and 04 yesterday but the graphs don't flatline for that hour. ??

PWSWeather is showing the incorrect time still but, despite the log being per minute it is showing no data since midnight. Perhaps they are in the process of adjusting it.

edited to add...
Well, at 08:10 local time, the PWSWeather graphs/data show two hours missing from 00:00 to 02:00 and current time as "07:10 at GMT + 02.02" which, I guess, is valid in some weird way but where the two lost hours went is anybody's guess.

[Mapantz]

Well, that is weird.

WU is back on track with current time and data and there is an hour of data missing between 03 and 04 yesterday but the graphs don't flatline for that hour. ??

PWSWeather is showing the incorrect time still but, despite the log being per minute it is showing no data since midnight. Perhaps they are in the process of adjusting it.

edited to add...
Well, at 08:10 local time, the PWSWeather graphs/data show two hours missing from 00:00 to 02:00 and current time as "07:10 at GMT + 02.02" which, I guess, is valid in some weird way but where the two lost hours went is anybody's guess.

I lost an hour of data too, the graphs didn't flatline either.
I forgot to mention, when i moved my clock forward, i closed Cumulus and reopened it, it then downloaded 60 archived records. If you move the clock back, i could understand it but forwards?

[steve]

I forgot to mention, when i moved my clock forward, i closed Cumulus and reopened it, it then downloaded 60 archived records. If you move the clock back, i could understand it but forwards?

It is now 1400 (say); Cumulus is running and up to date. You stop Cumulus, and move the clock forwards one hour so it is now 1500. You start Cumulus. Cumulus last had data for 1400, it is now 1500, so it needs to download the data from 1400 to 1500 to catch up. It doesn't know that you have just moved the clock forwards an hour, all it knows is that it was last running at 1400 and it is now 1500.