# Timerswitch triggering at wrong time, timezone offset?

**URL:** https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801
**Category:** General
**Created:** [16 February 2020 16:05 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801 "2020-02-16T16:05:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![RudyFiero](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rudyfiero/32/8836_2.png) [@RudyFiero](https://discourse.nodered.org/u/RudyFiero)
#### Post date: [16 February 2020 16:05 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801/1 "2020-02-16T16:05:39Z")

</div>

I am using Node-red 1.0.3. I am having a problem with node-red-contrib-timerswitch 1.2.4

> **[node-red-contrib-timerswitch](https://flows.nodered.org/node/node-red-contrib-timerswitch)**
>
> An easy, intuitive and precise node-red timer that allows you to turn something on/off multiple times a day and supports schedules as low as 1 second.

The time set to trigger an event is off by six hours. I am in GMT-6 so I assume the problem I am having is related to the time zone offset. I have a different node that shows the time on the dashboard and it has the correct local time, so I expect that my Raspberry Pi is set to the correct time zone.

I have used node-red-contrib-timerswitch at work on a setup R-Pi setup there and I am get switch events correctly. I don't know what the versions are but I think they may not be current.

What should I check to help find the issue?

Programmed time is 15:39:03,  
message using debug happens at 9:39:08 AM

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [16 February 2020 16:20 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801/2 "2020-02-16T16:20:26Z")

</div>

You could try  
[node-red-contrib-cron-plus](https://flows.nodered.org/node/node-red-contrib-cron-plus)

It supports timezones, can have an unlimited number of schedules, can send any payload at any time you need.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [16 February 2020 17:51 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801/3 "2020-02-16T17:51:36Z")

</div>

> [@RudyFiero](#):
>
> I expect that my Raspberry Pi is set to the correct time zone

Open a terminal on the Pi and run  
`date`  
that will show you what time it thinks it is and the timezone.

---

<div class="post-metadata">

### Author: ![RudyFiero](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/rudyfiero/32/8836_2.png) [@RudyFiero](https://discourse.nodered.org/u/RudyFiero)
#### Post date: [16 February 2020 18:34 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801/4 "2020-02-16T18:34:12Z")

</div>

I thought that the timezone was correct because a clock node I am using had the correct time. I thought they would get the time from the same place. I assumed wrong.

I did the date command and the time was wrong. I then ran raspi-config and the timezone was not set. I must have missed that step when I did the last setup. I don't use linux much. It is only running a mqtt broker so far and haven't had a need to go much further yet.

I thought this would be something simple. Thanks for the help.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [1 March 2020 18:34 UTC](https://discourse.nodered.org/t/timerswitch-triggering-at-wrong-time-timezone-offset/21801/5 "2020-03-01T18:34:17Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
