Small glitches somewhere....

[JLOB]

Is there any way to determine which Isy program caused an event?  Also is it possible that Isy misses seeing occasional X10 signals?  I’ve been having some strange behavior, and am looking for a way to trace it back.  The log, as it were, is not proving very helpful.  An example....today one of three X10 "chime" devices sounded off for no apparent reason.  The log didn't  show the event.  In another instance, a scene was triggered bu I can't fathom why.

 

Thanks.

JLOB

[larryllix]

Is there any way to determine which Isy program caused an event?  Also is it possible that Isy misses seeing occasional X10 signals?  I’ve been having some strange behavior, and am looking for a way to trace it back.  The log, as it were, is not proving very helpful.  An example....today one of three X10 "chime" devices sounded off for no apparent reason.  The log didn't  show the event.  In another instance, a scene was triggered bu I can't fathom why.

 

Thanks.

JLOB

The ISY log only shows status changes received from devices.

The Event log will show most of everything, including the binary codes (in Hex).

 

If you have several programs that can hit on a device you can disable the programs to eliminate other sources of action.

 

I found the  PLM less sensitive to X10 signals than many  native  X10 devices.

 

Insteon and X10 can not play well together at times. X10 has no ACK/NAK system or predictive collision system as Insteon does (for itself).

[Brian H]

My ISY log shows X10 sends and received. I see On Off Dim and Bright X10 commands in the Log. Should not matter but I also have the optional A10/X10 firmware module.

If modules have changed state with an X10 command. It will not be reflect in the modules status displayed in the Administrative Console.