X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Topic started by: nextccie on September 12, 2006, 09:51:35 PM

Title: AHP turns one appliance on for no reason
Post by: nextccie on September 12, 2006, 09:51:35 PM
One of my appliances is always on when I come home from work but I have no timers set for it.  The other one( I have only 2 )never comes on accidentally.
I did a scan on the X10 network (Find other Computers) and it did not detect any conflicts around the house..
What other things should I check since this is a brand new and almost default set up?

Thanks and other than that its cool.
Title: Re: AHP turns one appliance on for no reason
Post by: Charles Sullivan on September 12, 2006, 10:31:20 PM
One of my appliances is always on when I come home from work but I have no timers set for it.  The other one( I have only 2 )never comes on accidentally.
I did a scan on the X10 network (Find other Computers) and it did not detect any conflicts around the house..
What other things should I check since this is a brand new and almost default set up?

Thanks and other than that its cool.

Try reprogramming AHP from scratch - with only one timer it shouldn't take that long.

What happens if you exchange the two modules - does the problem follow the module or stay at the location?


Title: Re: AHP turns one appliance on for no reason
Post by: JimC on September 13, 2006, 06:47:23 AM
nextccie,

If the problem persits after trying Charles suggestion you might try using a different unit or house code. That worked for me when I had a similar problem. :)

What are you controlling with the module? If you do a search of these forums you will find other posts where, with certain types of loads, modules would turn back on.
Title: Re: AHP turns one appliance on for no reason
Post by: steven r on September 13, 2006, 09:29:32 AM
...What happens if you exchange the two modules - does the problem follow the module or stay at the location?
I'd try this 1st. A similar test would be to set an extra module to the same code and see if it triggers also.

Also check all your AHP macros to see if you have any commands following a dim command. I haven't tested it recently but there has been a know bug that causes a stray signal to be sent. I had a light on C5 that keep coming on till I added a 1 sec delay after all my dim commands.