That is funky. Please report it to Ed @ Ambient.
I'm going to hold off upgrading as I usually do and let it simmer.
It is never a good idea to use local time in a database, so that is poor practice to see. It is best to use UTC which is never adjusted for daylight saving time. What the WS-2000 should then do is convert the UTC in the database to local time when displaying the data charts. Then so that people don't complain that their data exports contain UTC instead of local time, there could be a second data column that is the converted local time which was also saved. Then if the user needs to import the data into some software package they can then choose to use either field depending on the software and its capabilities.