AMS reader date changes with timezone setting in OS

UtilitechAS / amsreader-firmware

ESP8266 and ESP32 compatible firmware to read, interpret and publish data to MQTT from smart electrical meters, both DLMS and DSMR is supported

Other

381 stars 73 forks source link

AMS reader date changes with timezone setting in OS #819

Closed manfi001 closed 1 month ago

manfi001 commented 3 months ago

Describe the bug AMS reader date changes with timezone setting in OS

To Reproduce change timezone to less than 0, e.g. UTC-1 and AMS reader date changes to 1 day less than real date.

Expected behavior AMS reader date should be independent of timezone setting on readout device

Hardware information:

Country: Austria
Meter: Sagemcom
Encryption enabled [yes]
AMS reader: [ESP8266]
M-bus adapter: TSS721

Relevant firmware information:

Version: [2.3.6]
MQTT: [yes]
MQTT payload type: [JSON]
HAN GPIO: [UART2]
HAN baud and parity: [2400 8E1]
Temperature sensors [none]
ENTSO-E API enabled: [no]

Additional context Discovered this behavior by chance during a recent stay in Latin America

ArnieO commented 3 months ago

Were you using the device in Latin America when you saw this, or did you read your home device remotely?

manfi001 commented 3 months ago

I read the home device remotely. But it's the same beaviour if I change the time zone of the PC or tablet at home and access the readers page.

ArnieO commented 2 months ago

Just to be sure I understand your report:

This is the date indicated in upper right corner of the GUI, not timestamp on parameters sent to MQTT - right?
Is the indicated date correct according to the time zone set, or is there a 1 hour error?

manfi001 commented 2 months ago

Yes, it's the date in the upper right corner, MQTT timestamp is not affected
The indicated date is wrongly set one day back
The timezone must be set at least 3 hours ahead of local time, e.g. Vienna is UTC+1 and if set to Greenland UTC-2, the date goes one day back.

ArnieO commented 2 months ago

Thank you for the clarifications, this must be a bug. Using the device in other time zones is not common, you are probably the first one to "test" this.