Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[arf1410]

I set up a simple test Macro -
Trigger Condition F6 ON and
The time is between 9:40 pm and 9:55 pm
Turn upstairs hall ON

Problem is, when I send an F6 at 10:05 pm,
it also turns the upstairs hall light on.
Unless I am missing something, it should
not, because I sent the trigger after 9:55
pm...HELP!

[rick j]

What address is "upstairs hall"?

[arf1410]

Upstairs Hall is E14, though I am not sure
why that would matter

[rick j]

I just wanted to make sure that "Upstairs
Hall" was not the same address as the
trigger.

A couple of things. If your using the Run
Macro button. It will execute every time. I
have added a lamp 'A8' and I use that switch
via the user interface to send the A8
commands which in turn trigger the Macro.
Make sure you download the Macros after each
change. I have found that if I try the Macro
before I get the 'download complete' message
I get flakey results.

Below are my Macros that I cut and pasted
from mt File/Reports/Macros. I did my test
at 1:50 AM and the first did not execute as
expected and second did. Please cut and
paste the Maro Report in the thread if you
are still having troubles.




Test On A8 On and
The time is between Greater Than or Equal To
1:00 am and 1:30 am (A1) New Module ON

Test On A8 On and
The time is between Greater Than or Equal To
1:00 am and 2:00 am
(A1) New Module ON

Test Off A8 Off (A1) New Module OFF

Cheers,
Rick

[arf1410]

I was sending an F6 to trigger the macro
with my Firecracker.

Not sure if I understand your test macros -

"between Greater Than or Equal"  time can
be either greater than or equal to one
time, or between two times.  How can the
time be greater than or equal to two times?

[rick j]

Hey, writing it that way was/is not my idea.
That is how it looks based on the logic that
I cut and pasted from the macro report. It
is that kinda' logic that you have to be
careful with when creating these macros. The
nightime condition is broke because of how
they interpret that logic. Because, and I'm
guessing now, that the greater than breaks
when you go from 24:00 back to 00:00 as you
pass midnight. As long as the times are
equal to the outside times and greater than
the first time it works. 3.170 comes out on
Monday and is supposed to fix the nightime
issue but it may change the logic on
the "time range". We may have to revisit
this again.

Regards,
Rick