Dataview UTC time seems incorrect

Hi,
When I view my RS4D locally it has correctly auto changed todays DST end back 1 hour.
I also note that RSUDP also displays the UTC correctly as it did before DST End.

However when I view (Data View it is not UTC as shown in lower legend, it actually seem to be BST ( 1 Hour ahead of UTC ).

Unless of course I am missing something.
Kindest Regards,
Tony

1 Like

Hello Tony,

Yes, there seems to be a discrepancy there. I have tried to replicate it on my side, but DataView and RSUDP continue to match in their UTC timestamps.

Can I ask you to try the following?

  1. Try to hard-refresh the browser window (using Ctrl+F5) to see if some cookie/localstorage data was causing this issue. Also, try a different browser to see if the issue can be replicated there.

  2. If you click on the UTC label at the bottom, does it correctly change to your time zone? Or does it display something else?

  3. And, if you click back, does it revert correctly to UTC? Or is the error still there?

DataView acquires the time from data fed by your browser, so you could also check that all timezones are correctly set there, if you haven’t already.

A final check: does StationView display the same issue in the live data for your station?

Thank you for your collaboration.

Hi Stormchaser,

Thanks for the reply, running my own weather site I always use Ctrl+F5 to clear cache as I did yesterday many times on 2 different PC’s and 3 different Browsers. Oh and also cross checked 5 other Tasmanian RS-Shakes and all displayed incorrect.

The last time I checked it yesterday was around 10:30 AEST, which was 8.5 hours after DST End Change. I was down South of Tasmania driving all day after that and did not check again until 01:00 AEST this morning and it was displaying correct. Absolutely no idea why it did not change until after midnight, well at least up till 8.5 hours after change was still not displaying.
I’ll keep a closer eye on it next change 2015-10-05.

Kindest Regards,
Tony

1 Like

Hello Tony,

I can always count on your extensive troubleshooting. Thank you.

Indeed, this seems quite unusual (to say the least), but this part

why it did not change until after midnight

makes me think that there could be something cached that wasn’t updated until after midnight, thus resulting in the correct time being showed.

Nonetheless, I have reported it to our software team so that they can take a look on our side of things.

Thanks again!