Well Tuicemen,
It may just be me too, trying to do something it was not designed to do. Here is what I am trying to do. Need to turn have my garage close automatically when the temperature is below a certain point, or when it is snowing or raining. No one can seem to remember to push the button when they come home! Anyway, I need to check 3 or 4 conditions. I used a macro that set a flag which I then used to tell the garage what to do, in this case it was flag 1. In the macro, I first cleared the flag in WWL everytime it checked conditions, I did this by checking if the month was less than 13, which it always is (there may be better ways, but bear me out!). Then it evaluated each condition, if the first one was true it set the flag if it was off (which it always was because of the month condition), all subsequent conditions were then checked as well, but the macro's condition was if the flag was already set, do nothing. This way, the flag was always set on the first true condition, and then was never cleared if subsequent conditions were false. If I recall there was not an "else" option in earlier versions. Originally, in the last version, it seemed to work fine. In this version I set up a test using 1 condition and then more than one condition. I would hit reset and see what AHP would send. Here is what seems to be happening. If I want D4 On to fire when the temp is below 60, it sends my D4 OFF (which is actually my month condition, which is first, which is alway true), then the D4 ON (the temp condition), the first time I hit the reset timer button. This is expected. After that, when it checks, if the temp is still below 60 it sends nothing on all subsequent checks. Does not fire the D4 OFF for the month condition, nor the D4 ON for the temp condition, just does nothing. (I removed all conditions in my macro for the test, and I used no else statement in WWL). If the temp then goes above 60, it will send the D4 OFF (the month check condition which is first, and ignore the D4 ON for the temperature condition, since it is not met), as expected. I could also swear, but not certain that the next time it checked it would send the D4 ON when it was not supposed to, then the next time it would not, then it would alternate between just D4 OFF (which it should do-month check) and D4 OFF and D4 ON (which should not fire, temp check). Thus on every check, my flag would switch between on and off. I'll check this more thoroughly later today.
When you add more than one condition, it seems to do go nuts, now for sure alternating between (in my case D4 ON and OFF, turning my flag on, then off, on then off, regardless of the condition being met or not), as well as other strange behavior that I have not pinpointed as of yet. I have not checked the docs lately, but does it evaluate each condition in order? And is it supposed to fire the "else" if the condition is not met? What if I do not use an "else" and leave it blank? Anyway, have at it, I'll try again later today.
jjsalobird
Author
Topic: PC Companion Weather Issue (Read 85589 times)