Print

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

[troll334]

Sorry guys,  I know I've seen this somewhere but couldn't find it (yeah I know...but I really tried).
The system's fairly stable (95plus% actually). However, I hear some random clicking and see some random light
activity (on/off, off/on). XTBM says no noise, BSC, etc.. Powerlines look clean.
Dug into the AHP log and found some interesting stuff. Nothing new to you guys I'm sure.
I've got an MS14 on I15/16, and an LM15 on I9. I9 is not controlled by I15 or any macros related to I15.
Setup: LM15 on I9 is turned on and I'm happy. Here we go...
Someone trips the MS14 on I15. Four minutes later, MS14 sends I15 Off. That's cool/normal.
So, the log shows the MS14 sending an off command. I15 Off, I Off. But, there's something in between...read on...
Right between I15 Off and I Off (in the log) someone walks in front of I9  and he sends his On like he should.
So the actual log sequence is I15 Off, I9 On, I Off.
Well, there's my ghost. The MS14 sent the Off command right on time, AHP heard the On command from I9,
then sends the I Off which turned my lamp off even though I9 Off was not explicitly sent.
Is there some config that tells AHP to send On and Off pairs in immediate sequence, i.e., don't allow another
command to slip in between?
I remember Brian talking about a feature where you could send I1, I5, I12, I On...that's kinda what's happening here.
At a minimum, I think I need to keep ALL motion sensors off the same HC's on which I have modules. That might help.
thanks,

[JeffVolp]

So the actual log sequence is I15 Off, I9 On, I Off.
Well, there's my ghost. The MS14 sent the Off command right on time, AHP heard the On command from I9, then sends the I Off which turned my lamp off even though I9 Off was not explicitly sent.

Actually, that is exactly the way X10 modules are designed to operate.  You can "queue up" several modules on the same housecode, and have them all respond to the same function code - ON, OFF, etc.

This reduces the amount of X10 powerline traffic, provides faster response, and allows different unit codes on the same housecode to be controlled in sync.

If you move that other module to a different housecode, your problem will go away.  Of course, it may induce its own set of problems on that new housecode...

Jeff

[troll334]

Hey Jeff,
thanks for the quick resp.
Yeah, agreed. Perhaps I can minimize it by spreading the zillions of modules across
the available HC's. Now that I know what's happening, I'll exorcise that ghost
thanks!