I have mostly Insteon devices, with the exception of a PSC01 used with magnetic sensors to detect the garage door status, and an X10 transformer that both powers my Ademco Alarm and sends out X10 signals based upon triggers specified in the alarm's control panel.

On or around July 8th (from what I can tell in the logs), I stopped receiving most X10 signals...only a few about the garage and only one way "Garage Door Off" (but no "Garage Door On"). By the 10th, I haven't received any X10 signals from either the PSC01 or the ADEMCO Transformer.

I did recently load 1.8.1 (not sure when, but probably the night it came out). Is there anything I could check to determine what is going on?

I did a little more testing. I thought I would take on of my INSTEON devices (a SwitchLinc V2) and enable it to run in X10 mode. In doing so, I factory reset the SwitchLinc and then attempting to give it an X10 address by pressing the top paddle for 10 seconds to put it into linking mode, and then using Indigo (v1.8.1) to send the X10 address three times. The device is not receiving the X10 signal.

Next I took the PSC01 and set it A13 and sent A13 3 times by crossing the wires. The SwitchLinc V2 linked to the PSC01 and whenever I crossed the wires and uncrossed, the light would toggle on/off. This leads me to believe the hardware (the PSC01 and the ADEMCO Power Supply) are actually okay.

Could this be an issue with my PowerLinc V2 Controller even though the INSTEON stuff has been working and continues to, or could it be something in Indigo?

I think insteon works a little different from X10, so if you have powerline issues Insteon won't be effected but X10 will.

I called Smarthome Tech Support yesterday and he said that if the INSTEON commands are working, that the controller should be fine. If neither were working, he would suspect the controller.

X10 signals are getting sent and received just fine - just not by the PowerLinc and Indigo, so I don't know which is to blame.

All this started around the time I upgrade to 1.8.1

Does anybody know where I can download version 1.8 of Indigo to rule that out?

I think the odds are pretty unlikely this is related to your 1.8.1 upgrade or to Indigo. What about plugging the PSC01 (or any other X10 transmitter) directly into the same outlet as the PowerLinc V2 -- can the V2 then see the commands from the PSC01? I suspect you have some type of X10 signal problem that is showing its ugly head now.

You can download v1.8.0 here if you want to give it a try.

Regards,
Matt

I agree it's a signal problem. I've had many instances over the year with localized signal issues (having one right now actually). Since installing filters at key locations it's been reduced considerably.

Matt,

Thanks for the link to 1.8 - I will try that when I get home. I haven't had any signal issues to this point. I did try plugging the PSC01 in to the passthrough outlet on the PowerLinc but Indigo didn't register anything when I had it this way.

One other test to try: plug the PSC01 into the pass through outlet of the PowerLinc as you did before, but also plug the PowerLinc into the filtered (not pass through) outlet of a FilterLinc. You obviously won't be able to control modules well in this scenario because the FilterLinc blocks X10/INSTEON frequencies in both directions, but it will isolate your test case (PowerLinc V2 + PSC01) from other external signal problems.

Matt

Matt,

Indigo v1.8 didn't change anything, as you suspected. I don't own a FilterLinc so it will be hard to test that scenario. Here is a little more information that may help. When I plugged the PSC01 back into the passthough on the PowerLinc V2, and then I proceed to cross the wires, simulating an open and closed circuit, the PowerLinc LED would blink a few times and then go back to solid - difinitely indicating it is "seeing the signal", right? Indigo didn't log anything though, and the light I have temporarily set to that X10 address did not turn on or off. I really appreciate your help with this. Hopefully I will figure this one out soon.

UPDATE: The PCS01 DOES WORK when plugged in to the passthrough on the PowerLinc (at least at the moment). I am turning on and off a light though the Indigo logs are not registering anything. Would it normally log activity / signals in general?

Very interesting.... my guess is that your PowerLinc is malfunctioning in such a way that only X10 receiving/transmitting is effected. Just like Smarthome's support, I'm surprised by this. There have been cases with the older PowerLincs where the X10 transmitters/receivers fail but the unit continues to function (Indigo can communicate with it), but I would have expected that both INSTEON and X10 would fail together on the V2.

Anyhow, just to make sure it is bad hardware, send me an email (indigo-support at perceptiveautomation.com) offline. I'd like to do a bit more troubleshooting off-forum just to rule out an Indigo bug before you get a new unit.

Regards,
Matt

I am having the same problem, is there any update on what could be causing it?
I have mostly Insteon devices except for an X-10 in-line appliance module that controls my landscape lighting and a Hawkeye Motion Detector that controls my garage lights. About a week or so ago my landscape lights stopped coming on via the timed event in Indigo AND my garage lights would not come on. I assumed that the X-10 modules had gone bad so ordered a new Insteon InLineLinc and some ICON relays. Installing the InLineLinc solved the problem with the landscape lighting and The ICON relays gave me control once again over my garage lights. So today I started playing with the Hawkeye detector. I have it set to A5 and created an event trigger in Indigo to respond to an X-10 on on A5 with the action to turn on the Insteon ICON relay that controls the garage lights. It didn't work. I set up an old X-10 appliance module to A5 and it will activate when the Hawkeye detects motion. I however cannot control the X-10 appliance module via Indigo. It acts like it thinks it can but nothing happens. All the Insteon devices still work fine. I switched out the 2414U with my old 1132U and the X-10 works again. That leads me to conclude that the problem is withthe 2414U controller. Sound reasonable?
Should I order a new 2414U?
Thanks for any help you can provide. Can't wait until someone comes out with Insteon detectors.
Stebo

Before someone points it out, I know that I could probably set the ICON relay's X-10 address to A5 and get the Hawkeye detector to control it, essentially bypassing Indigo and the 2414U, but I was trying for a more elegant approach.
Also, I want to use the Hawkeye to alert me when there is motion in the garage by creating a second Indigo trigger event that will turn on an indicator light and make an announcement.
Thanks again for any help.
Stebo

Stebo,

I am the original poster. I ended up calling Smarthome and they ended up shipping out a replacement Powerlinc V2 which solved the problem. They hadn't really seen it before, but X10 wasn't working at all through the Powerlinc but the INSTEON stuff continued to work. I verified the Powerlinc was the issue by setting up one of my INSTEON LampLincs to an x10 address, and then setting up another X10 device to respond to that address directly (as opposed to issuing command through PowerLinc). That worked which confirmed my suspicions about the PowerLinc. Hope this helps...

How strange. Looks like my PowerLinc V2 is experiencing the same thing. I've contacted Smarthome about a replacement.

gregjsmith wrote:How strange. Looks like my PowerLinc V2 is experiencing the same thing. I've contacted Smarthome about a replacement.

I have also started having this problem. I have contacted Smarthome for a replacement but they did say they have never heard of this problem. These problems seem to coincide with me going from 1.8 to 2.0 beta but when i tried going back to 1.8 it did not fix the problem.