I just worked around my problem and want to let folks know that I was unsucessful in getting boolean decisions made on flags (in my case Flag 1 and 2). I had 3 macros triggered by B16ON (sent by my motion detector) and wanted to take 3 different actions depending upon the time of day. Dawn: Flag1 clear, Flag 2 clear , Dusk: Flag1 clear, Flag 2 set, and midnight: Flag1 set, Flag 2 set. These are each unique conditions, but when used to try to discriminate which macro should run there was total chaos.
My first workaround was to use 2 phantom modules (switches) as the flags, and again, checking module status instead of flag status gave the same result.
The latest sucessfull workaround uses 3 Phantom modules, each time mark sets the approriate switch on and switches the other two off.
I think there is a bug in the software to not allow what clearly they intended in the conditions sections where they provide for And/Or operations on the flags or modules.
I did not revist the use of Flags, and perhaps this technique will work with flags like it does for phantom modules.
One more comment: I find that it is good practice to end a macro with a phantom module "call", turning it either On or OFF. That way the pending address becomes a don't care. To clarify: I have experienced this:
MACRO 1: A1 ON, A2 ON (Both Go on) Activity log: A1, A2, AON
MACRO 2: A2 OFF (A2 Goes OFF) Activity log: A2, AOFF
MACRO 3: A7 ON ( A7 Goes on, but unexpectedly A2 comes on as well, even though not instructed to do so)
The activity log shows a combined transmission A2, A7, AON
The A2 address from MACRO 2 seems to be left as the last iaddressed unit, and then incorrectly is used for the next MACRO.
Another bug that will drive you nuts. Perhaps the last issued address goes invalid after some interval, but I have been testing
by sending commands within 30 sec of each other and have been getting bad results until I put in a phantom at P1 at
the end of each MACRO.
I am using V 3.204