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.
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?
Seems correct. Apparently Someone™ has possibly made undocumented changes, unbeknownst to me until now. Might be too steep of a hurdle for not even a rank amateur.
The events are fired through a web-based calendar service. Would you like to see the the flow tree?
Also, I've been given remote access to the other device at the other location; the device time settings as well as the Node-red version is the same.