ISO 8601 date format ignores timezone

[philchillbill]

Is the ISO 8610 date implementation in Domoticz incomplete? I notice that it ignores the timezone offset if I set an Evohome until-override via JSON:

"http://192.168.178.2:8080/json.htm?type ... &used=true"

in other words, it ignores the +01:00 at the end of "2018-01-09T11:00+01:00". Anybody else see this behaviour?

[jenssen]

Hello,

Just tested this, same here.

I have a other issue with the time.

When I look at the devices/setup, I see this data at a specific zone with an override:
17.6 C, (12.0 C), TemporaryOverride until 2018-01-16T23:30:00

When I look at the dashboard, I see that the override is until 2018-01-17 00:30:00.

Why is there a one hour difference? I set it on 2018-01-16T23:30:00 (via JSON or manuelly).

Do you have the same problem?

[philchillbill]

What I notice is that if I set an UNTIL via json and then check the device status through json, it shows the correct time in the returned json - the issue is in the time displayed in the Evohome widget on the dashboard. The Evohome app on my iPhone and the Evotouch both display the correct until-time as set by my json, so the issue really seems to be the displayed-time on the dashboard.

[philchillbill]

My Domoticz timezone and Evotouch clock are both correct, so it's not that. There really is a discrepancy between the json returned from a rid= call to an Evohome zone idx and what the widget displays. The temps and modes are all ok, it's the 'until' field that's off. Try it yourself and see if you can reproduce it.

[jenssen]

My Domoticz timezone and Evotouch clock are both correct, so it's not that. There really is a discrepancy between the json returned from a rid= call to an Evohome zone idx and what the widget displays. The temps and modes are all ok, it's the 'until' field that's off. Try it yourself and see if you can reproduce it.

I still can, looks like the time on the dashboard widget is still not fixed unfortunately.