nowandthen

Wow! That's an amazing program! Very nice!

After adding the Insteon I/OLinc, we continued to have erratic program behavior. After many hours of fussing around it occurred to me to use an Insteon controlled light instead of an X-10 light. Hallelujah! The program worked reliably ,well I did have some minor tweaks but no more weirdness. My advise, get rid of X-10 wherever and whenever you can. If you have weird behavior and X-10 is in the mix, try substituting Insteon devices and see if the problem goes away. We are now using the Insteon I/OLinc and an Insteon light switch. X-10 Powerflash removed from service. Switchlinc light switch moved to another location that will see more typical commands (not on/off every second). I really need to find a good explanation of how the ISY "thinks". I clearly do not understand when it tests IFs etc. Thanks again for your help!

I would never have figured that out. Thanks Lee!

I see it. Thanks Lee! You are the man!

Once again Lee falling on his sword for the rest of the ISY community. What a guy! I think I can just unplug my ISY and PLM just before Sunset, plug it back in some time after sunset and see if evening lights catch up. Going to my friends this evening so I can't test tonight, but will try tomorrow night (Sunday) and report back as well.

Thanks Lee and Brian. I just spoke to my friend. I suspect the flooding of x-10 on the powerline is the problem. He does have a booster/coupler. I have an I/O Linc. We will change out the X-10 powerflash with the I/O linc tonight, then write a program to flash the hall light. More X-10 going bye-bye. Thanks again! Todd

Ok so I have a program that says turn porch light on at sunset. Say the power goes out 30 minutes before sunset. Then 30 minutes after sunset the power comes on. If my program says turn porch light on at sunset and I have Run at Startup enabled, then the Isy when power is restored will test that program and turn the porch light on because the IF is true. Correct?

I don't see an obvious way to set a range of dates for a program to run. Is there any way to do this? For example, to set a range from December 1 to January 7.

Anyone?

I sold my 99i to a friend. I reset the 99i and loaded the latest firmware 3.2.6. Generally, I have been able to train him on how to make programs. However I cannot figure out one program that will run for a while then stop working a few hours later. This is the program: If X10 'B13/All Units Off (13)' is Received Or X10 'B13/All Lights On (5)' is Received (we added this late last night and it appeared to fix it but it quit working a while later) Then Wait 12 seconds Set 'Family Room / Front Entry Hall' Off Else - No Actions - (To add one, press 'Action') If we select "run then" then the program seems to work for a while, (half hour or so), after which it will not run. B13 is an X10 Powerflash PSC01 set to mode 2, which sends an all units off all light on repeatedly. It is connected to his house alarm. When the alarm is tripped it sends B13 All lights on all units off repeatedly. When someone enters the alarm code the power flash stops sending the on/off X10 code. The idea is the hall light flashes while the alarm is tripped (he has a deaf roommate) and then stays on for 12 seconds after the alarm code is entered (powerflash stops sending codes) then turns off. However the hall light will not turn off. Executing a "run then" then testing the program works, however some time later (a few hours?) the program stops working. ??? Powerflash is set to: "Output Mode 2: Engaged: Sends an X10 ALL LIGHTS ON / ALL UNITS OFF Command, continuously, called Flashing, (sets off X10 Siren after a few cycles) Disengaged: Flashing stops, All Wall Switches and Lamp Modules will remain ON (X10 Siren stops after a few seconds)" We added the "or" to the IF line and thought we had it fixed. I went home but low and behold, several hours later it would not run. I tried status and control settings to no avail. When I watch the programs summery screen, I see "running then" and I see start time reset every couple of seconds as the powerflash sends B on and off. When the If was only set to B off it would not run the program at all even though the last command from the powerflash should be a all units off. (Update, the command from the powerflash leaves lights on, but we have the or statement and it still fails to run). When we added the "or" line it ran. I thought we had it. But he called this morning and said it didn't run later that night or this morning. I don't understand why we can get it to work for a little while then it won't work any more. Any ideas?

Reading the user manual, it sounds like checking this option will make the ISY run the checked programs upon a restart. So if the power goes out, then comes back on, the ISY will run any checked program, and in effect test the If statements, what should have been turned on will be turned on, what should have turned off will turn off, etc. Am I understanding that correctly?

I just reset the old 99i. Programming is all gone. That's good. Was surprised that it retained the latest software 3.2.6 (I updated before taking it out of service). Also the X-10 module shows up in the Help About. Does this sound right? I expected a factory reset to revert it back to some version it was originally programmed with but then again i suppose it should only keep the latest version. I Thought it would loose the x-10 module but it didn't. If this is as it should be then I am ready to take it to my friends house and set it up there.

Received the 994i today. Swap went without a hitch. I kept my old PLM. My friend will be happy to get rid of his old x-10 controller. Hopefully his x-10 "weirdness" will be a thing of the past. ISY + Insteon = much improved reliability, not 100% but much better. Thanks for the advise and instructions.

Thanks Michel! I will do that once I have the 994i up and running and then reset the 99i. As always great service and great user support!

Thanks Michel. Thanks apostolakisl. So I'm looking for my X-10 auth code. I checked my email folder of license keys and didn't see anything from UDI. I also looked in my usual download folder for the ISY, and my other ISY folder but didn't see anything there. What would I have received to enable X-10? I'm generally very good about saving these things. Todd

Thanks to both of you. Sounds pretty easy. I'm going to let my friend have the X-10 module along with the 99i. I'm not sure what the web server section of the ISY is, so i guess I'm not using it. Use my computer to talk to it, otherwise it doesn't do anything else over the web (that I know of). If I use the new PLM then I suppose I need to wipe the old PLM, right? Most likely I'll just keep my PLM, no reason to make things more complicated than they have to be.

I own an ISY99i with the dual band PLM. It has the x-10 option. I have a friend that I am trying to get moved over to Insteon. He still has X-10 and an outdated unsupported controller. I have almost completely replaced my X-10 with Insteon. I think the best way to get him going is to sell him my system and I would buy the ISY994i with dual band PLM currently on sale at Smarthome. I don't need x-10 anymore but he does. Technically what do I need to do to do this? Should I keep my PLM and give him the new one? Where do I go to find out how to swap out a 99i for a 994i? I assume the x-10 option is linked to the serial number of my 99i. In other words in order for him to take over my x-10 option he needs my 99i right? The programs and settings are in the ISY, right?. How do I transfer the programs etc to the 994i? Is this like replacing an iPhone? I back up the ISY before removing the 99i, then reload the program to the 994i? Thanks for any advice and tips. I don't want to mess up my system.

Great! Thanks!

What happens if I unplug Insteon lamp modules and/or other Insteon devices that I only use for holiday displays? Will the ISY "complain" about not being able to communicate with them? I've left some lamp modules and motion sensors enabled but would rather unplug them and remove the motion sensor batteries. If the ISY does complain, what is the best way to deal with modules that are only used during short periods of time?

I figured it out. I opened the event viewer, I could see repeated K16 commands. A Leviton 16400 controller was the problem. Turning off the breaker for that room stopped the x-10 K16 command. The ISY then completed it's house keeping and seems to be happy now. Moderators, feel free to delete this thread.

When I log on to the Admin Console, the main window opens then a 'System Busy" window opens. The ISY takes quite a while to get to 100% and when it does it starts over. Any idea what is going on? I disconnected and reconnected power to the ISY to no avail. Restarting the console just puts it back in this loop.

Thanks Lee!

Thanks again to everyone that replied! Happy to report I can now program the on level and ramp rate of the Icon dimmer switch via the ISY. I couldn't get it to work yesterday so I removed the switch, factory reset it again, then installed a Switchlinc in its place. Partly to confirm that I wasn't doing something wrong and partly because I wanted a programmed switch in that location. So I do not know what version was reported by the ISY yesterday. All of that was before my posts here, thus before software update. Since then I installed the latest software. I reinstalled the same Icon switch. The ISY reports it as v.39. So here is what's different from yesterday: 1. I upgraded the ISY from 2.8.16 to 3.1.17 2. I added the device in a slightly different manner. Yesterday I used Link Management, Start Linking, choose "Add devices found in links and remove existing links". I also used that for the Switchlinc which did work, so I'm not sure this was the wrong way to add a device. Today when adding the Icon switch I used Link Management, New Insteon/A10/X10 device, choose "Add devices found in links and remove existing links". Lee triggered my memory when he said use auto discover which was not an option in the first method I just described. That method seems to require that I manually enter the Insteon address. The first method automatically finds the address of the device. (Of course the device was put in to linking mode for both methods). So either 2.8.16 was the problem or the way I added the device was the problem. Don't you hate it when people change to variables at the same time? Should I make a note to myself to only add devices via New Insteon/A10/X10 device? Or is that method OK and most likely it was the software?

Good to know that they are programmable like the Switchlincs via the ISY. I did the remove, factory reset, and add back by auto discovery last night to no avail. I will try it again after I upgrade to 3.x.x. As suggested. Come to think of it, i upgraded from 2.8.10 to 2.8.16 not too long ago. I'm sure i could program the Icons in the past, maybe that upgrade messed something up. Keeping my fingers crossed. Will report back but may be a few days. Thanks for the replies!

I always seem to struggle when adding devices. But I'll save those questions for other threads. Q: Are the Icon switches 2876DB not able to accept programming from the ISY? Only Switchlincs 2476D's? I am unable to set the on level via the ISY (on level (applied locally) and have it respond accordingly when I turn the switch on (at the switch). With the Switchlincs, I can set the on level (applied locally) and ramp rate (applied locally) via the ISY and the switch will respond accordingly when I turn the switch on and off (at the switch). I'm not talking about scene control, I'm simply setting the device parameters by selecting the device under My Lighting. If this is a limitation of the Icon switches then I won't buy any more of them. I'm running ISY V2.8.16 Thanks.