Print

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

[jeff h]

I finally got a Smart Macro to work.

But - do I *have* to name it the same as the
Motion Sensor.  I have 4 different motion
sensors outside the house.  And, I want to
do different things depending on time.

Something like this.  If it's in the
evening, just turn on the floods in that
area.  After 10pm, turn on all floods.

I'd prefer not to call all Motion sensors
the same unit code - if I do, I can't tell
where the motion came from.  But, if they
are different, then I have several macros
that look basically the same - and one could
be turning on the lights while the other is
turning them off.  I guess I could use a
flag or something.

I'm starting to think it's time to break out
the Ole SDK and start writing some VB.

The Doc with Smart Macros is pretty light.
Guess I'll do some more Forum reading to see
how people *really* implement this stuff.

Jeff H

[SteveRF]

HI,
I happen to also have 4 motion sensors.. I
addressed them all in the B range..
b1/2, b3/4, b5/6 etc... I used the motion
address to call a macro that drives lights on
D1/2, D3/4, D5/6 etc... I even have a bank of
pure dummy modules called DT-1, Dt-2, Dt-3
etc.. these are Dummy Module Timers giving me
on/off for each...so I suppose the sky is the
limit... but something I have found with the
last release (3.180) is that macro's seem to
be a bit slower than a couple of versions
ago... maybe my imagination... but I do
believe I have bathroom lights coming on a
second later than they used to... no biggie
now... but If you are "in a hurry" hehe... a
second or two more WILL make a difference.
I have 20 modules, 10 marcos, 9 timers
working.. Running XP Pro/SP2/all updates,
dual P3, ver 3.180
regards,
steveRF

Regards,
Steve

[jeff h]

I think I may have figured out what I want
to do from the AccessX10 site.

Basically, create Macris called M1-x for
what I want to do.  The, when the *any* MS
fires, turn on the light assigned to it and
then run Macro M# for "all exterior lights"
for instance.  That way, the correct light
goes first (no 4-sec delay for the 4th
light).

According to AccessX10, the way to call
another macro is to make a "fake" module
with the same name.

The nice that about all this is you cn keep
macros from stepping on either other so
much.

On we go!