Skip to main content
Home
for DLMS smart meters
Open source solutions for DLMS smart metering

Main navigation

  • Home
  • Products
  • About us
  • Open Source
  • Community
  • Forum
  • Downloads
User account menu
  • Log in

Breadcrumb

  1. Home
  2. Node
  3. DateTimeOffset Is Not Korrekt On Summer/winter Time Change

DateTimeOffset is not korrekt on summer/winter time change

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By Stier , 20 January, 2017
Forums
Gurux.DLMS

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

Profile picture for user Kurumi

Kurumi

9 years 10 months ago

DateTimeOffset

Hi,

This date time is really bad in DLMS. Standard says that date time is range -720…+720 in minutes of local time to UTC. So example here in Finland meter SHOULD be configure -2 hours. Out time zone is UTC +2 h.

We actually broke this some time ago. We have clients who have configure meters using UTC time. We fixed this back to this version.

BR,

Mikko

  • Create new account
  • Reset your password

Hire Us!

Latest Releases

  • Thu, 11/19/2026 - 10:57
    Gurux.DLMS.Python 1.0.204
  • Thu, 11/19/2026 - 10:12
    gurux.dlms.c 9.0.2611.1901
  • Tue, 10/13/2026 - 12:00
    gurux.dlms.java 4.0.97
  • Tue, 09/22/2026 - 14:02
    Gurux.DLMS.Net 9.0.2609.2201
  • Mon, 09/21/2026 - 10:18
    Gurux.DLMS.Net 9.0.2609.2101

New forum topics

  • Landis E650 meter reading over DLMS
  • class_id = 40, version = 2, pushsetup Unparsed data frame
  • GXObisValueItem entries without MaskSize appear to be interpreted as bit flags
  • CheckedListBox incorrectly selects GXObisValueItem Value=0 for non-zero values
  • UIValueType=TextBox is rendered as CheckedListBox when Values are defined
More

Who's new

  • Sayang
  • q80435762@gmail.com
  • ONCAK
  • Berhasil
  • ratirvivege1979
RSS feed
Privacy FAQ GXDN Issues Contact
Follow Gurux on Twitter Follow Gurux on Linkedin