Ghost program turning on light and another strange behavior

[dbwarner5]

i have an extensive Insteon set up with ELK, some Zwave and some older X10 devices, mostly motion detectors. I have been an x10 / ISY/ Insteon user for over 10 years, but now have two strange problems that I need help with. 

 

FIRST QUESTION...At one time, I had an x10 device in a bathroom turning on the light and then w/o motion, after a delay of 20 minutes, turning the light off. However, due to unreliable x10 communications to turn the light on for this guest bathroom, I changed the program to only turn the light off, if it has been on and there is no x10 motion detected after 20 minutes. 

 

However, somewhere along the way, the light began turning on again, all by itself. I have now tracked it down to turning on when another x10 motion detector, set to a different code, in a another room is activated. 

 

The strange part is that the ISY shows the light as off, even though it is on, and there is no proof that i can tell in the program details that any program has even run to turn on the light, as that program was deleted long ago. So even if i have the wrong house code (am using the x10 add-on module), there is no program to make anything happen to the switch, 

 

Additionally, i have deleted the light switches (three-way) in the bathroom, and re-added them to the ISY to ensure there isn't some other program somewhere running it. So far i am baffled. Lastly, absolutely nothing even shows up in the Event log. 

 

SECOND QUESTION.. I have another program that runs from sunrise to 5pm and checks weather conditions for sun / clouds and wind speed/ direction to control an awning. At 5pm, the program should turn false and the awning should retract. The program runs but not until 5:08? why is that?

 

Are there limits on the ISY that i am pushing up against? I have about 230 devices, 400 programs, elk integration, etc. 

 

Any help is appreciated. thanks.  

[larryllix]

Do you have any Smartenit devices?

 

Do you have the ISY Pro option?

[Techman]

Regarding the X10 switch that turns on - When I used X10 I found that occasionally the contacts on the House Code and Unit code developed oxidation and created problems. Try spinning the code wheels back and forth to clean the contacts.

 

Post a copy of your awning program.

Verify that the time is correctly set on your ISY

[Brian H]

Most X10 Motion Sensors also have a Dusk/Dawn sensor function. Uses the X10 address of the Motion Sensor + 1 Unit Code.

So a Motion at A4 would be a Dusk/Dawn at A5. I have seen things like Dusk/Dawn Sensor address being on another devices address. So light changes trigger the Dusk/Dawn address and control an unwanted device.

[dbwarner5]

Question two is solved: my error, I have another program that temporarily disables the awning program if the weather changed such that the awning doesn't open and then close in a short period of time based on a short term weather change. And that program seems to run very frequently as the weather changes subtlety but not enough to change the condition of the awning. My bad on that one.

 

Question one though is still a very large mystery. There are no dials on the motion sensors that can get corroded. The codes are set via push buttons and feedback via led light.

 

I have all my x10 devices spaced 2 numbers apart... A1 a3 a5 etc for the desk dawn setting. But again, there is NO program that runs or shows in the event log when this bath light turns on, but in know it's from a motion detector in another room, which used to turn on that rooms light and is now no longer showing up at all when triggered.

 

Are there are any known issues around the x10 add-in module? My problems seem to come when I converted my x10 devices to the module / library names.

 

Thanks