[ANSWERED]: My rouge x-10 updates in my log

I'm getting a ton of unknown x-10 logs in my mostly indigo system
Such as....

Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

And I have no devices assigned as F10, F11 or F12

Any ideas where to look or how to resolve?

Thanks

Rick.

[jay (support)]

A couple of thoughts based on prior experience:

• You have an X10 or INSTEON module that's failing and is broadcasting trash - I've had this happen several times in the past.
• You have some other device spewing garbage that sometimes looks (to the interface) like X10 signals
• Your interface is failing

My guess is the first one. I had very similar symptoms a couple of times several years ago - turned out to be failing SwitchLincs. One was a very old X10 SwitchLinc and one was an INSTEON SwitchLinc.

I had a similar situation where on my chosen house code had a couple of the just the odd numbered X10 addresses (thought that was strange in itself) with mystery on/offs constantly. I never did figure out why.

I never though of a failing device (since all my X10 devices seemed to work) and assumed it was something else generating codes that were perceived as X10.

IIRC I think I just made dummy devices in Indigo (i.e., mystery F12 device = "Bogus X10 Device F12" or something) and then just didn't use those addresses for any real X10 devices. I did this so it was easy to identify related log data and to know not to ever use them otherwise.

This was a drag before I got a W800RF32A and was limited to a single house code with a standard, single house code receiver. With the W800RF32A receiver I can use every house code and number simultaneously, so I have tons of codes to choose from.

Mike

Now to figure out how to isolate the issue. Jay I have over 85 devices, it there a easy way to figure which one could be failing. Be it a X10, Insteon for the interface?

I also thought WagnerOne's post might help and reconfigured my W800RF32A to not receive anything from house code F or below. That didn't help.

One other note it happens consistently 37 seconds.

Any help would be appreciated.

Thanks

Rick

[jay (support)]

Turn off each circuit one at a time until the messages stop. That will help isolate it at least to a circuit. Then I'm afraid it's one at a time until you find it.

Jay, I think still have not corrected this problem as I'm not looking forward to switching off every breaking in the house one at a time.
Any other suggestions or clues?
Would you expect these X-10 update can only come from X10 devices?
I've set my interface to ignore the F channels but they still appear in the log.
How can I test the interface to see it it's the issue?

The updates are appearing even more rapidly ...
Nov 22, 2014, 9:07:43 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:08:20 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:08:57 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:09:34 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:10:12 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:10:49 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:11:26 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:12:03 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:12:40 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:13:17 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:13:54 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:14:31 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:15:08 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:15:45 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:16:22 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:16:59 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

Nov 22, 2014, 9:17:36 AM
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on

I think this is the weekend to try to tackle this issue.

[matt (support)]

Discconect your W800RF32 from your Mac. Do the commands still appear? If so, they aren't coming from the W800 hardware.

If they are coming from the power line, then most likely it is a faulty X10 module or the PowerLinc (or CM11/CM15) is malfunctioning, but it could be power line noise.

Unfortunately, the only way to know for sure is to start turning off circuit breakers and/or swapping in a new PowerLinc. There is no internal diagnostic test that any of the interfaces support, and thus nothing Indigo can tell you other than that the interface is saying it is seeing all those X10 F10/11/etc commands. They may not really be there though if it is noise or the PowerLinc is malfunctioning.

Hey Matt,
Thanks for the reply.
I did disconnect my W800FR32 which is connected via a Keyspan serial adaptor.
The rouge X-10 updates still appeared.
So now you say the next three possible sources are...
1) Power Line Noise - I have filter links installed to help suppress noise.
2) A faulty X10 Module - I only use X10 RF devices - Motion detectors and door switches
3) A Bad PowerLinc - I have a PowerLinc 2413USB running version V1.6

Do you have a suggestion as to which one I should attack?
The X10 RF modules? or The PowerLinc 2413USB running version V1.6

As always your help and knowledge is greatly appreciated.

[matt (support)]

There really is no easy way to do this. As Jay suggested,, I would start with turning off circuit breakers. If one of them stops the problem then you know the problem module (or source of power line noise) is on that circuit and you can narrow it down further.

If you have a spare PowerLinc then you can swap that in to see if the problem goes away. If it does then the problem is obviously the PowerLinc. If you don't have a spare then there is no quick way to determine if the problem is the PowerLinc.

Hey Matt,
Thanks for the reply.
I did disconnect my W800FR32 which is connected via a Keyspan serial adaptor.
The rouge X-10 updates still appeared.
So now you say the next three possible sources are...
1) Power Line Noise - I have filter links installed to help suppress noise.
2) A faulty X10 Module - I only use X10 RF devices - Motion detectors and door switches
3) A Bad PowerLinc - I have a PowerLinc 2413USB running version V1.6

Do you have a suggestion as to which one I should attack?
The X10 RF modules? or The PowerLinc 2413USB running version V1.6

As always your help and knowledge is greatly appreciated.

I vote for #3 - I'd say your 2413 is failing.

I had similar issues with mine when it died, then came back to life, then died , came back to life. it was replaced on warranty as it was within the 2 year period.

Since replacement I have not seen any X10 messages in my log. (I have no X10 in use)

I'm back at it.
I've replaced my 2413 and still have the same
Received X10 F13 off
Received X10 F12 off
Received X10 F11 off
Received X10 F10 off
Received X10 F13 on
Received X10 F12 on
Received X10 F11 on
Received X10 F10 on
issues.

I sure don't want to go thru the entire house trying to isolate one switch.
I have just about every switch as an Insteon.
No X10 switches only motions detectors and door contacts.

Any new ideas?

Thanks

Rick

[jay (support)]

No easy solution unfortunately. It's very likely one of your devices starting to fail.

Will air gaping them work to take them off line and determine which one?

[jay (support)]

Yes.

I had a very similar situation. When I turned off an Insteon LampLink, it would mysteriously come back on in about 20 seconds. The log showed not only the module being turned on but a "Received X10 P1 Off" event. Since I had just added the light, I reasoned that the LampLink module was failing so I replaced it. No good. Next, I replaced the Cree LED bulb... that solved the problem. Something in the bulb was affecting the LampLink.

It might be interesting to note that when the new lamp mysteriously came on after I turned it off, another light elsewhere would come on to about 50% also.

Simply switching out the LED bulb solved my issue.

Enjoy,



Dana Haynes
Accularian's Macintosh Support
http://www.lookatmymac.com