Node-Red events fire at UTC time, not local time

General
1

Hello.

I have a problem with an inherited system, a RevPi running Node-Red. Events are added through a third-party cloud-based calendar service. The client has two of these in two locations, one location works fine, the other is 2 hours premature. I have not been involved in setup and programming of these, I'm just the poor sap holding the shortest straw.

Node-red controls some room specific motors for sun screening windows and possibly temperatures as well.

I've checked the time settings for the RevPi with timedatectl and it returns the correct UTC, local time and time zone.

Setting the time zone explicitly in settings.js as mentioned in many threads with the same-ish problem does not make a difference.

I'm guessing the answer is somewhere in the flows, but I'm at a loss where to start.

2

If node-RED is running in a container (docker) on the RevPI, you will need to set the TZ on that.

Show us what you get from CTRL+SHIFT+P -> System Info

chrome_nFo5zvWZp2

3

Hello Steve, thanks for your reply.

I assume it's running on bare metal. I don't see Docker running as a service (service --status-all).

Control-Shift-P gives me a Core:action menu without a system info listed as a possible option.

nodered
nodered1239×407 22.2 KB

I found the "action list" under Menu - View, but it seems to be the same menu as Control-Shift-P.

Edit: This is version 1.3.5 btw. I see that is quite old, but I am hesitant to update.

4

you really really should update. I imagine you are running a very old and outdated (unsupported) version of NodeJs too. Never mind the CVEs and bug fixes, there are soooo many briliant new features in v2.x, v3.x and v4.x

Why are you hesitant? What is it stopping you installing this on a separate computer and testing all your nodes and flows work?

5

I don't have physical access to the site nor a test environment, unfortunately. The person who originally configured it is across the country.

6

Show us how the events are being fired please.

Also configure an exec node to run the command date and see what it says.