I had a similar problem when I tried using a
macro to set a flag bit which had a RF
trigger with the same house/unit code as the
motion detector.. triggering the flag macro
then had the same effect as generating the
motion detector trigger, which then executed
the motion detector macro. In my case the
motion detector was also programmed to
generate the same house/unit code as the
flag set macro, which repeated the whole
process for several cycles. It was kind of
exciting, since the code was set to generate
a chime.
I don't know if this is true in your case,
but to avoid this scenario ensure that the
motion detector (and its reserved '+1' unit
code) are unique and not used as triggers by
any other flag setting macros.