DateTime variables stored with Daylight saving offset

[user2972]

Hi, with the recent DST change any DateTime variable is now displayed an hour behind - so a time set for 07.30 is now displayed as 06:30. It continues to operate correctly and allows a rule trigger at 07:30 but clearly has the potential to cause confusion for a user. If you then set the time from a dashboard tile, the time on the drop down shows correctly and when changed reverts to displaying an hour earlier. If the DateTime variable is updated using the settings page then the time is then displayed correctly, however the settings page display of the variable shows a UTC offset (+1 in my case), and if cleared and set again then the newly set variable now shows +0. Clearly this will cause issues when the clocks change again next year. My hub is configured correctly with the correct timezone and lat/long set. What I really want is for DateTime variables to not contain any UTC offset and just be used against the current local time. Any suggestions on how to achieve this?

Thanks

Andy

[jshimota]

Maybe have a look at Date & Time Parser. It's got GMTDiffHours, DSTActive (T/F), ObserveDST (T/F). Maybe you can use that value instead?

[user2972]

@jshimota

Date & Time Parser

Many thanks for the quick reply. I have had a look at this and whilst it could be used I think it would mean separating my time values into their respective hh and mm as separate variables rather than using the DateTime type. I would rather find a way of using the DateTime variables without the UTC offset (NB which is also not accessible and seems to use the current offset applicable when the variable is set!)

Appreciate any other thoughts....

Regards

Andy

Thanks for the suggestion