Ticket #327 (closed defect: invalid)

Opened 7 years ago

Last modified 7 years ago

Time based triggers do not work in the event system

Reported by: juha kaarlas <juha.kaarlas@…> Owned by:
Priority: major Milestone:
Component: Telldus Live! Version: 2.1.1
Keywords: Cc:
Blocked By: Blocking:
Platform: All Sensitive: no
Verified by Telldus: no

Description

Summary

The timezone in the event system seems to be in Swedish time OR the system does not consider daylight savings time. This causes time based events to trigger later than they should. Example triggers: block heater, time/clock.

Background:
I was testing the block heater trigger event with an email action and noticed that it did not fire as expected. Local time is GMT+2 (Finland).

Departure time was set to 08:00. Outside temperature was between 6-7 C. At 08:24 I got an email that the event had fired.

Reproduced behavior
I tested the trigger again. I modified it at 10:58 local time to get exact values. Departure time was set to 10:43 (in the past). Outside temperature was 6.6C. The tooltip on the trigger said "At current temperature this will be triggered around 10:06." The event was triggered at 11:06 local time the same day. It should have fired at 10:06 the next day (assuming the same temperature).

I managed to reproduce the same behavior with a simple time/clock based trigger.

Steps to reproduce block heater trigger

  1. Create a new event
  2. Set block heater trigger's departure time to desired value
  3. Write down the prediction about when the event will be triggered
  4. Add an email trigger or equivalent so you will get a notification
  5. If in Finland (GMT+2), the trigger fill fire 1 hour later than it should

(If in another country or timezone, the trigger will probably fire at another offset.)

Steps to reproduce time trigger

  1. Create a new event
  2. Drag the clock icon to the triggers box
  3. Set the trigger time to desired value (e.g. 13:00)
  4. Add an email action so you receive some sort of notification
  5. If in Finland (GMT+2) the trigger will fire at 14:00 and email will be sent

Further information
Unsure if this is a daylight savings time issue or a timezone issue or both.

The times set in Scheduler work as expected.

Change History

comment:1 Changed 7 years ago by micke prag <micke.prag@…>

Try to restart the TellStick Net after changing the timezone.

comment:2 Changed 7 years ago by juha kaarlas <juha.kaarlas@…>

TellStick Net was restarted after moving to Daylight Savings Time. DST happened on October 28th. Then we had a power outage on November 5th for several hours which was a natural restart.

Timezone and current offset for the client seems correct: timezone="Europe/Helsinki" timezoneAutodetected="1" tzoffset="7200".

Using the Scheduler functionality works correctly. For instance I have a heater on a set schedule and it works every time.

For some reason the actual execution times in My Events are off by one hour (1h too late).

Last edited 7 years ago by juha kaarlas <juha.kaarlas@…> (previous) (diff)

comment:3 follow-up: ↓ 4 Changed 7 years ago by micke prag <micke.prag@…>

Your timezone is set to autodetect. Try setting it instead and then restart it.

comment:4 in reply to: ↑ 3 Changed 7 years ago by juha kaarlas <juha.kaarlas@…>

Replying to micke prag <micke.prag@…>:

Your timezone is set to autodetect. Try setting it instead and then restart it.

That fixed it. Thanks!

comment:5 Changed 7 years ago by micke prag <micke.prag@…>

  • Status changed from new to closed
  • Resolution set to invalid
Note: See TracTickets for help on using tickets.