DateTimeOffset is not korrekt on summer/winter time change

Hey guys,

I actually implementing the latest Gurux.DLMS version (8.5.1612.2006). So far I just identified one problem with this version and I'm able to workaround this easily.

But I just wanna inform you of this problem, so you may fix it once.

The GXDateTime.Value Property contains a System.DateTimeOffset which is great compared to older versions that only provided a System.DateTime. The problem seams to be on the winter/summer change. I wrote a small Console Application to give you an example of the problem:

This is just a readout (load profile 1, Obis: 1.0.99.1.0.255) of an L+G E650 over the time change:
(Just time column splitted up in DateTimeOffset and State)
30.10.2016 00:00:00 +02:00 DaylightSavingActive
30.10.2016 00:15:00 +02:00 DaylightSavingActive
30.10.2016 00:30:00 +02:00 DaylightSavingActive
30.10.2016 00:45:00 +02:00 DaylightSavingActive
30.10.2016 01:00:00 +02:00 DaylightSavingActive
30.10.2016 01:15:00 +02:00 DaylightSavingActive
30.10.2016 01:30:00 +02:00 DaylightSavingActive
30.10.2016 01:45:00 +02:00 DaylightSavingActive
30.10.2016 02:00:00 +01:00 DaylightSavingActive
30.10.2016 02:15:00 +01:00 DaylightSavingActive
30.10.2016 02:30:00 +01:00 DaylightSavingActive
30.10.2016 02:45:00 +01:00 DaylightSavingActive
30.10.2016 03:00:00 +01:00 DaylightSavingActive
30.10.2016 02:00:00 +01:00 Ok
30.10.2016 02:15:00 +01:00 Ok
30.10.2016 02:30:00 +01:00 Ok
30.10.2016 02:45:00 +01:00 Ok
30.10.2016 03:00:00 +01:00 Ok
30.10.2016 03:15:00 +01:00 Ok
30.10.2016 03:30:00 +01:00 Ok
30.10.2016 03:45:00 +01:00 Ok
30.10.2016 04:00:00 +01:00 Ok

As you can see the first block (summertime) from 2-3 o'clock is handled with an offset of +01:00, but the state of the value is set to "DaylightSavingActive", so the offset should be +02:00, or am I wrong?. Second block (wintertime) is okay.

Thanks for your investigation.

Best regards,
Andrea