Rules With Scheduler Start 2 times
Solved
I noticed, that the rule with scheduler start at time and one hour after too.
Is there a probleme with my hour (France) and serveur hour (Croatia) ?
The same problem 
No connection
Real-time notifications may not work
No, there is not a problem with timezone, we are all in CET.
The problem is that the box boots in GMT, and then changes the timezone with the configuration, and then recalculates the schedules. It looks like somehow the trigger survived that recalculation, and executed your rule once more at 18:24GMT. Most definitely a bug.
No, there is not a problem with timezone, we are all in CET.
The problem is that the box boots in GMT, and then changes the timezone with the configuration, and then recalculates the schedules. It looks like somehow the trigger survived that recalculation, and executed your rule once more at 18:24GMT. Most definitely a bug.
No, there is not a problem with timezone, we are all in CET.
The problem is that the box boots in GMT, and then changes the timezone with the configuration, and then recalculates the schedules. It looks like somehow the trigger survived that recalculation, and executed your rule once more at 18:24GMT. Most definitely a bug.
No, there is not a problem with timezone, we are all in CET.
The problem is that the box boots in GMT, and then changes the timezone with the configuration, and then recalculates the schedules. It looks like somehow the trigger survived that recalculation, and executed your rule once more at 18:24GMT. Most definitely a bug.
Hey, I experienced exactly the same thing this morning: 7.40 and 8.40.
I updated the timezone in the box general settings yesterday (from GMT+1 to GMT+1 paris)
This rule is opening my main gate, I don't want this to happen everyday!
How to deal with this? Simply reboot the box? switch everything to GMT ?
Hey, I experienced exactly the same thing this morning: 7.40 and 8.40.
I updated the timezone in the box general settings yesterday (from GMT+1 to GMT+1 paris)
This rule is opening my main gate, I don't want this to happen everyday!
How to deal with this? Simply reboot the box? switch everything to GMT ?
Anyway I have to say that http notifications through pushingbox.com and prowl have successfully warned me directly on my phone that my main gate was opened!
Anyway I have to say that http notifications through pushingbox.com and prowl have successfully warned me directly on my phone that my main gate was opened!
Only one rule execution this morning so it's OK.
But I received two notifications ;-)
another night and I will confirm if this gets corrected by the new firmware
Only one rule execution this morning so it's OK.
But I received two notifications ;-)
another night and I will confirm if this gets corrected by the new firmware
Hello,
Rules with Scheduler start always 2 times. At time and one hour after.
Sorry
Hello,
Rules with Scheduler start always 2 times. At time and one hour after.
Sorry
Darko should have debug info from my box.
A new thing also happened today: my rule was actually executed 6 to 8 times in a few seconds at the scheduled time (8 http notitications received).
As I saw the corresponding device switching between offline and online state before, i wonder: could a new "trigger" be created each time the device is going online (and not cleaned well when going offline) ?
Darko should have debug info from my box.
A new thing also happened today: my rule was actually executed 6 to 8 times in a few seconds at the scheduled time (8 http notitications received).
As I saw the corresponding device switching between offline and online state before, i wonder: could a new "trigger" be created each time the device is going online (and not cleaned well when going offline) ?
This morning observations:
GOOD: no execution one our later
BAD: still 9 received notifications within 2 seconds, which let me think the rule is executed 9 times (as notifications from other rules work fine)
This morning observations:
GOOD: no execution one our later
BAD: still 9 received notifications within 2 seconds, which let me think the rule is executed 9 times (as notifications from other rules work fine)
it's true when i use "scheduler" to start my AC with ZXT120, i can see that the ZXT120 sends betwen 3 and 10 times the order.
When i use HTTP request with my phone to start my AC, i can see just one order.
In the event widget, it's the same "scheduler" or "Http", just one time.
it's true when i use "scheduler" to start my AC with ZXT120, i can see that the ZXT120 sends betwen 3 and 10 times the order.
When i use HTTP request with my phone to start my AC, i can see just one order.
In the event widget, it's the same "scheduler" or "Http", just one time.
hey it seems a new firmware is out to fix this issue!
hey it seems a new firmware is out to fix this issue!
firmware upgrade done.
will check fixes tomorrow!
firmware upgrade done.
will check fixes tomorrow!
The rule executed once at the scheduled time.
But my fibaro FGS221 did not change status.
Doesn't work either when triggered manually.
Should I have re-sync devices after the firmware upgrade?
The rule executed once at the scheduled time.
But my fibaro FGS221 did not change status.
Doesn't work either when triggered manually.
Should I have re-sync devices after the firmware upgrade?
Hello
Sheduler start just at time my rule and not one hour later too.
Good job,
Hello
Sheduler start just at time my rule and not one hour later too.
Good job,
Everything OK today for me !
Everything OK today for me !
Replies have been locked on this page!