Announcement

Collapse
No announcement yet.

Phantom Device

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Clever1
    replied
    Yeah Rupp is the man... I sure am Happy he is local... Course we haven't met yet..

    Leave a comment:


  • kwolter
    replied
    Yep, Rupp's suggestion worked great. I still had a script active that I thought I had abandoned a long time ago. The virtual device didn't exist anymore, but the script kept referencing it.

    Thanks!

    Leave a comment:


  • Clever1
    replied
    Excellent point Rupp.... Probably a faster response too...

    So how did it go???

    Leave a comment:


  • kwolter
    replied
    Thanks, Rupp. I'll try this too.

    Leave a comment:


  • Rupp
    replied
    kwolter,
    Another option I have used in the past is go to the HS root directory and using windows search the "A word or phrase in the file" option enter Q17 to see if you get any hits especially in the HTML or scripts folders.

    Leave a comment:


  • kwolter
    replied
    I only have one Palm Pad remote.

    "Create a virtual device "Q17" and see what the status is changing to. This will help you to find out which script or plug-in is the problem. Meaning that if Q17's status changes to "Partly Cloudy" you know it is a weather script somewhere."

    I'll try this. Thanks!

    Leave a comment:


  • Clever1
    replied
    k,

    Create a virtual device "Q17" and see what the status is changing to. This will help you to find out which script or plug-in is the problem. Meaning that if Q17's status changes to "Partly Cloudy" you know it is a weather script somewhere.

    Leave a comment:


  • George
    replied
    kwolter,

    That Exec Command entry in the log is coming from an EXECX10 statement from either a script or plugin. One thing you can check is to stay by your HS log screen and check to see if a script starts running when the log entry is created. If no script shows running then a plugin might be the cause.

    Leave a comment:


  • bruce l
    replied
    So this would be a virtual device as the X10 spec only has A-P housecodes not even your X10 interface should report noise as anything above P housecode.


    Do you have any new plugins? Maybe girder or parallel port or Ocelot. Something that is not X10.

    Leave a comment:


  • Rupp
    replied
    Good point Dick. I assumed that some of the keyfob remotes would go further than the X10 controllable codes. You know what they say about assuming.

    Leave a comment:


  • RAM
    replied
    Remotes don't do "Q"

    Originally posted by Rupp
    Do you have a remote in the drawer somewhere that is on the Q house code? I had a box of X10 stuff and one of the stick a switches was wedged between 2 boxes and transmitted A1 ons for a few days before I found it. It could be noise on the powerline but this is a low house code for noise.
    Probably not a remote stuck somewhere. First off, remotes normally only do house codes A-P and secondly they normally only do addresses 1-16. Gotta be something else, probably noise as you suggested.

    Leave a comment:


  • Rupp
    replied
    Do you have a remote in the drawer somewhere that is on the Q house code? I had a box of X10 stuff and one of the stick a switches was wedged between 2 boxes and transmitted A1 ons for a few days before I found it. It could be noise on the powerline but this is a low house code for noise.

    Leave a comment:


  • kwolter
    started a topic Phantom Device

    Phantom Device

    I have an entry in the event log "Exec Command: Q17 Off dim: 0 Extra: 0" The problem is that I don't have a device Q17 defined anywhere. These fill up the log day and night.

    Any ideas where to start with this one? Not a showstopper, but kind of annoying.

    Thanks!
Working...
X