Print

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

[danno]

I've got a new problem with a macro I
created.  I have a motion sensor that
triggers a macro.  That macro is used to
trigger another macro.  Ocassionally the
macros go crazy and get stuck in an endless
loop (but not always).  I have to unplug
the CM15A from the wall for a few seconds
then plug it back in to get it to cancel
the macro loop.

Setup is something like this:

Motion sensor triggers macro M1
M1: If flag 1 is cleared execute macro
Execute M2
end
M2: Set flag 1
A1 on
Delay 10 mins.
Clear flag 1


There is no reason for this to turn into an
endless loop.  At first I thought the
sensor went berserk but disabling the
sensor did not stop it.  I had to
disconnect the CM15A.

Anybody seen this?  I have a diag unit but
I'm not sure if this is the kind of thing
the diag unit can diagnose.  Anybody have
any ideas before I send this in as a bug
report?

Dan

[martin]

Is your second Macro on A1 On? Try to move
your delay into A1 or A1 steps incorporated
in your M2.

[danno]

A1 is a chime module

[julian]

Dan, it sounds like a flag issue to me... I
have a couple of macros that sometimes ignore
the flags and start looping too. According to
X10 Pro, they are working on this issue and
should have something for us in the next release.

[steven r]

As a general rule, I stay away from house
code A1. (For that matter, I don't use
house code A at all but that's another
story.) When your battery gets weak in your
motion detector, it may reset to A1. After
that, Murphy rules.

Actually I do have an A1 macro. It blinks
the lights instead of the regular dimming.
That way I know when when batteries need to
be replaced.

[joe s.]

Steven - clever idea re: A1.  I have
something similar - A1 turns on a whole bunch
of lights (sorta like dusk, but even more) -
If that happens...I know it's "battery time"
in one of my sensors.