Timer flows require to be set up in UTC time, not local time, else they do not trigger at the correct time. My time zone is GMT+2 ( Africa, Namibia). I set the Date/Time on cerbo console Date & Time page to Namibia Standard Time (UTC+2) . The data&time on said page shows correct local date/time then. In my node red flows I use node-contrib-timer which allows setting of multiple on/off time schedules per day, etc - there is no local/UTC time setting selection in the node - it uses the node red time as its time reference. In all cases I now have to set the timer to local time -2hours and then the timer triggers on the 'correct' local time - eg, set to come on @ 08H00 and it comes on at 10H00 local time. Changing the Cerbo date & Time to UTC time makes no difference.
ssh into cerbo root and 'date' returns 'day month date time UTC 2024'
with 'day month date' correct, time is in UTC, NOT local, and indicates UTC on same line.
The timer ( and cerbo and all flows) worked for the last 2 years, and now...
I am reluctant to use the manual symbolic link method to change the time zone - I don't know what else may be affected.
Any Advice please...
Joe
