I am currently running an ActiveHome Pro system which has been in service for 15 yrs. It consists of 10 timed lights, several macros (trigger definitions), and approx. 10 lamp modules and spot lights. I provide this background to hopefully get away from "noise on the line", etc. type discussions. I now would like to use Indigo but have hit a major problem.

With the exception of manually starting one lamp module, I cannot get any other module to illuminate. All of my items downloaded to the controller (the Insteon one recommended) and the log says the lights are lit. My system is basically all X10 based. When setting up
the devices none of them were precisely identified in the selections, but I tried using other items with no success. I am hoping I have one systemic problem which can be fixed! Thank you


Stuart

So, when you try to control a light from Indigo you see the command in the event log but the light doesn't respond? It sure sounds like a signal issue. You were using some other X10 interface with ActiveHome Pro I assume - have you tried that interface with Indigo? If Indigo doesn't support it, have you tried ActiveHome using that interface in the exact same wall socket that your INSTEON controller is plugged into? What PowerLinc model are you using?

With ActivceHome I am using a CM15A interface which Indigo does not recommend be used for Indigo. I purchased an Insteon 2414U to use with Indigo (exactly what is recommended). I have not tried using the CM15A in Indigo, which is supported but not recommended, nor have I tried the 2414U with ActiveHome.

We are Indigo - our recommended interface is the 2413 BTW not the 2414. In any event, the CM15 should work fine with your X10 devices so I'd suggest that you connect it and see if you can control your devices with it. That will rule out a problem with the 2414.

I am annoyed regarding the recommended interface. I didn't pull that model out of the air, it is troughout your documentation, stating to obtain the 2414 to get the performance required when downloading. I suppose I need to go plead for an exchange from Machousestore.com to obtain an exchange.

I won't be able to do the test this afternoon. It takes time cleaning out the ActiveHome and loading Indigo (well, a little time) but my system is due to start its cycle shortly, and I don't want to disrupt it. I will have it done by tomorrow. Thank you for your assistance.


Stuart

If you're using the interface in standalone mode, which you didn't specify as a requirement, then the 2414 is the only option that's still being sold that Indigo supports. We don't support the CM15 in standalone mode. Unfortunately, it's quite old so it doesn't support the newer INSTEON extended commands. The newer PowerLincs don't support standalone operation.

Regardless, you shouldn't attempt to return anything until you can figure out what is going on with the communication. Use the CM15 to help determine if it's a location issue or if the 2414 isn't working in your environment. Once you determine that, then you'll have a better idea of what to do about the problem.

I attempted to download my values to the CM15A but the Software would not accept them stating "the CM15A was not supported." That was strange since the Software accepted the CM15A as a valid interface when I began. Anyway, since I could not download my values I decided to manually try to turn on the lights which were attempted with the 2414. Unfortunately, the lights failed to illuminate exactly like they did with the 2414. Once again the only module which I could get to work was a lamp module.

I anxiously await your next suggestion.


Stuart

Note above I said that the 2414 is the only shipping interface that Indigo can upload to - we don't support uploading to the CM15. I wanted you to try the CM15 to determine if it is a signal issue or an issue with the 2414.

Your test pretty much proves that it's a signal issue. Since neither the CM15 nor the 2414 can control your X10 devices from that outlet then there is something interferring with the signal. Check out the signal troubleshooting page for common causes and solutions to signal issues.

I am currently operating an X10 system over the same wires (I.e. house) using the ActiveHome software. I don't experience the type of issue you discussed. Now that you know about my current system do you still feel the same about my problem with Indigo? Thank you



Stuart

Are you operating the exact same CM15 (that you tried with Indigo) from the exact same outlet (as used by Indigo), with the exact same electronics/computers plugged into the same outlets throughout your home?

When it comes to X10 signals, the signal path makes all the difference in the world.

But to answer your question, if some of your modules work (your lamp module in this case) but other modules do not work then, yes, it is a signal problem.

Yes, everything was the exact same (it was the perfect comparison). Because the comparison was so telling (I.e. the exact same modules did not work with both interfaces and the same
module was the one that functioned), and coupled with the fact that other company X10 software has functioned in my house leads me to believe that I have an Indigo software issue. It just seems that Indigo should eliminate the possible software issues before asking me to initiate such a tedious and time consuming activity given the known facts. Please let me know what further you can investigate or explain how my reasoning might be weak. Thanks.


Stuart

Hi Stuart,

Indigo tells the interface (PowerLinc or CM15) to put the command on the power line, then it does so. After Indigo has sent that command to the interface, the process is out of Indigo's control. The commands to send X10 ON and OFF commands are simple. There is only one way that Indigo can tell the CM15 or PowerLinc to send such a command.

You have said that you have a lamp module that works, but other modules do not work. That indicates that Indigo is communicating with the interface (PowerLinc or CM15) correctly and the command is being put on the power line. The only difference between the module that works and the ones that don't work are the signal paths and the what electronics/appliances might be interfering with the commands. The way Indigo tells the interface to put the command on the power line is identical -- the only difference will be the X10 address.

Unfortunately, other than telling you that it is a power line noise issue and suggesting that you troubleshoot that, I have no other tips for you. However, I can tell you that I have worked with numerous (literally hundreds) of users troubleshooting such problems and based on what you have told us on this thread you have a signal problem.

I finally got the modules to start responding by turning off the TV. However, the All Off and All Lights Off commands on the Device page in Indigo did not operate as intended (i.e. the lights did not turn off). When I took my hand held remote controller and hit All Off, the lights went out. Any ideas why the computer commands would not function?

Also, are you able to clear the Interface of any data? When I want to download my real schedule I would want to delete what currently resides in the Interface. Is there a way to actually see what is in the Interface other than using the logs? Thank you.

Hi Stuart,

Does the Event Log show that Indigo is sending the X10 All Off and All Lights Off commands for the specific house codes used by those modules? If so, then that command is being put on the power line and there is some power line noise issue preventing it from being received by the destination module.

Indigo always replaces all the logic/schedules on the PowerLinc when it uploads. Whatever was previously on the PowerLinc is replaced. If you want to clear it completely using Indigo, then inside the Upload Settings dialog unselect all of the triggers and schedules so that the previous schedule is replaced with nothing.

Indigo does not have a way to visually see what triggers/schedules are on the PowerLinc. It logs what it uploads, but that is all.