I have checked the flow using the new pre-release build of the dashboard and the timestamps show the same as the release version.
Yes, sorry for the confusion, thatās the expected behaviour
@CJS did you try my function node to check the time settings in node-red?
My apologies on the delay got busy on another project at work. Here was the msg from the debug node.
And what was the local time at the server at that time, and the local time where the browser is running?
Also what is the time zone at server and browser, in UTC+-n?
So that was taken at 7:56AM CST so that would have been 8:56AM EST where it is located and should be adjusted to.
Well as you can see the environment that node-red is running in at the server is configured for UTC (timezoneoffset is 0) and it thinks the time is 08:55 UTC. So that is probably the problem.
Thanks for your time and attention to this matter, Iāll get with my team and look into it. Its probably something we messed with trying to get around the timezone issues we were having for the project.
Iām sure Iāll see you around the forum! Have a good day!
One thing to watch out for, if node-red is running in a Docker environment in the device (I don't know whether it is or not) then the docker container may have the wrong settings even though the system time and zone are setup correctly, if they are. Check the system settings first though.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
