You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create an tech input node and set mode to time picker. If you fill for example 02:00 in the dashboard on version 3.4.0 you will get a value of 7200000 which is ofcourse 7200 seconds which is obvious.
What happens?
But on version 3.5.0 this is translated to 01:00. There is an offset of one hour since the latest update.
I have 4 installations which are perfectly the same but 2 of them are on 3.5.0 and 2 on 3.4.0 with the same dashboards but the times are shifted 1 hour on 3.5.0
What do you expect to happen?
It would be some sort of logical that this doesnt change. I checked if i could find any settings about this but it seems not to be there around.
Please tell us about your environment:
Node-RED-Dashboard version: 3.5.0
Node-RED version: 3.0.2
node.js version:
npm version:
Platform/OS: Windhoos 10
Browser: Firefox and Chrome
The text was updated successfully, but these errors were encountered:
liquidacid
changed the title
Times of imput time picker shift 1 hour
Times of imput time picker shift 1 hour 3.4.0 -> 3.5.0
Aug 2, 2023
Don't worry - need new glasses - second system was actually on 3.5.0!
Upgraded to 3.6.1 and all is good!
Is this fixed in 3.6.1?
I have two installations - on the first I have 3.6.0, server is running in GMT (currently = UTC) and the time returned by the time picker matches what I input on the browser.
On the second, I have 3.6.1 but this server is running in UTC and I probably can't change that. On the second system the time picker returns 1 hour less than the time I enter.
Is this the same problem?
What are the steps to reproduce?
Create an tech input node and set mode to time picker. If you fill for example 02:00 in the dashboard on version 3.4.0 you will get a value of 7200000 which is ofcourse 7200 seconds which is obvious.
What happens?
But on version 3.5.0 this is translated to 01:00. There is an offset of one hour since the latest update.
I have 4 installations which are perfectly the same but 2 of them are on 3.5.0 and 2 on 3.4.0 with the same dashboards but the times are shifted 1 hour on 3.5.0
What do you expect to happen?
It would be some sort of logical that this doesnt change. I checked if i could find any settings about this but it seems not to be there around.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: