Have been having the same problems. It looks like the dashbord is adjusting its display back to UTC or zulu time based on manual time and timezone you define. In my case from the US/Eastern timezone at 19:00 hours it is showing 00:00 on the dashboard. Which is UTC-5 not adjusted for DST.
If it shows the next day you have probably just crossed the midnight boundry.
Check your local time zone compared to UTC. Then add or subtract that number of hours from the time you set under the manual settings.
Melbourne is +11 from UTC so my quess would be that the dashboard would show a time 11 hours earlier. If you local time was 11:00am then it should show midnight of the day before.
If it shows the next day you have probably just crossed the midnight boundry.
Check your local time zone compared to UTC. Then add or subtract that number of hours from the time you set under the manual settings.
Melbourne is +11 from UTC so my quess would be that the dashboard would show a time 11 hours earlier. If you local time was 11:00am then it should show midnight of the day before.
Under previous version you were had achoice of setting your local clock to GMT or local time. GMT was recommended if you had a number of ASGs in different time zones so reporting was consistent. My system clock is running on gmt which currently is 11 hours behind me (allowing for daylight savings).
Date and time in the menu are correct, but the dashboard and bios show GMT. So somewhere a different call is being used.
