dleduc

I have now successfully migrated. I did attempt to follow the migration instructions, but I originally failed. It seems like my key failure was in failing to update the Firmware of my 994i. I think that I might have tried, but when you click on the link you get the forum entry that tells you about the upgrade without actually seeing the upgrade. You have to scroll down and read the whole message which is what I failed to do. Also, the first few words on the page are nothing about needing this upgrade to migrate, it starts out by saying "This build is just a small update. It contains a fix for unit conversion in program conditions." That is hardly a message that encourages one to read on. In any case I seem to be successful. I did notice that some of my lesser used devices have apparently died since I last used them so they will probably need to be replaced. Just one more quick question, is the web page access to the 994i no longer present in the eisy? It doesn't seem to be. I used to use it a lot when I was sitting at my computer and wanted to turn something on or off.

I was following the migration procedure. However, when I got to "select update packages" I could find that nowhere on the menu. I have found that now and done it. I also could see no obvious way to update the firmware on my 994i since the pages that I went to basically said that it was superseded. Given the encouragement from these posts, I tried harder and I found and applied the firmware update. Reading on from there it basically says backup the 994i and restore on the new eisy which is what I did minus the firmware upgrade. I see the boldface that says a migration backup is different from a regular backup, but I don't see any way to make a migration backup. The instructions also imply that this step only applies if you have zWave which I don't. Since you encourage me to ask questions before proceeding, I am doing that. Is there some special migration backup that I am not seeing?

It seems like I am not the only one having migration issues, but I can't sort through 1000 responses to try to match my particular issue. Setting up my new eisy threw me for a little bit since I had already tried to unsuccessfully use UD mobile to talk to my isy 994i. However, it eventually let me add a new device and setting up the eisy was easy. What is not easy is migrating my devices from the 994i to the eisy. I only have Insteon devices so that minimizes some potential problems. From what I could read the best way was to restore the configuration from the 994i to the eisy. This does bring over all of the programs, but none of the devices. Also the programs have all placeholders like "Response type 10" instead of the Insteon commands that were there formerly. I then tried restore devices and it runs to about 4% and quits and no devices appear. I also tried restore PLM and it has an equally short and ineffective result. I have tried this with both a brand new USB PLM and the existing serial PLM that I have used with my 994i. I also have a few other issues, but I will begin with just this initial setup stuff. Can anyone help me get through this initial growing pain? Thanks.

Let me add a little more information. I I look at the event viewer I see a ST 255 when I turn it on and 6 seconds later I see a ST 0 I've attached a picture of the activity from the Event Viewer. I basically understood the ST 255 and ST0, but I don't understand all that is going on in the more detailed view.

My Appliance Linc v38 used to work fine for several years. A couple of weeks ago it started turning off after 5 seconds if I turn it on using Alexa, MobileLinc, or the PC console. If I hit the button on the device itself, it stays on until I turn it off. I don't see any programs turning it off. Does anyone have any ideas or has it just given up the ghost?

Thank you Brian! I think that I have it working as it should be now. I had tried a test wire that I just tried to touch the little screw with, but I was resisting actually inserting wires into the mounting slots. I did this with two wires that I could connect or disconnect at will. The setup that I have has the thermostat and I/O Linc in one room, the computer in another room, and the thing I was trying to control outside in my greenhouse making it hard to check responses. With the two wires I was able to pug in the I/O Linc next to my computer and watch the response on the screen. I finally settled on Latching: Continuous, with only Key beep and LED on TX checked. I then took the I/O Linc outside next to the device and made sure that it responded as I wanted. finally I connected the I/O Linc back to the temperature sensor and tested and it failed because the I/O Linc was plugged into a power strip that had a surge suppressor. With it plugged directly into the wall, it appears to be working. However, one comment that you made about linking devices with the set button instead of with the ISY994i. I have linked the devices to the ISY994i by using the Link Device or add a new device, but I had not seen a way to link them together with the ISY9941 which is why I did it with the buttons. With your comment in mind I went back to reread the manual and see if there was some way to do this. What I found is that I can link them by putting them in the same scene. This works fine, but is that the only way to make them linked on the ISY994i? It is the only way that I have seen to populate the membership panel. Thanks again for all of the help and inspiration.

I have what should be a simple application, but it is not acting like I logically think it should. Is my logic faulty or do I have a defective device? My application is simply that I have a temperature sensor in my solar hot water collector and when the water reaches a certain temperature, I want to turn on a pump to circulate the water and store the hot water. The part that does seem to be working fine is that I have a a temperature controller that closes a circuit when the temperature is reached. The problem must lie in the other components of my system. I have the output of this temperature controller connected to the ground and sensor inputs of an I/O Linc - Insteon Low Voltage/Contact Closure device which is plugged in to an unswitched outlet. My pump is connected to Insteon On/Off Outdoor module model 2634-222. I have linked the sensor device to the on/off module by holding the set button on the sensor for 3 seconds and then holding the set button on the on/off module for 3 seconds. They appear to be linked since the flashing light on the sensor goes off when I hold the button on the on/off module. However the software on my isy 994i does not show any links on the membership panel. When the temperature controller closes its circuit, the green light on the terminal portion of the i/o linc lights up indicating that it knows the circuit is closed. However the isy994i software shows that the sensor is still off and conversely when the temperature sensor turns off the i/o linc stays on. The on/off module does not appear to respond to anything from the i/o linc. The other variable in all of this are the options for the i/o linc sensor. I have it set to latching: continuous since what I want is for the device to be on when the temperature is high and off when it is not. Does anyone have any thoughts on whether I am doing anything wrong or if the device is defective? Thank you.

Last night I eliminated the last X10 device plugged into my house and I wanted to give it a day to see what the log looked like. Unfortunately, I am still getting the flood of X10 status requests. These happen before I ever turn on my device and for a long time after it is turned off so it does not seem to be the culprit. Brian 's post made me think about the coupler/repeater and I think that I might have put one in in my X10 days, but today I pulled the cover off of my circuit breaker panel and could not see it. I think that it was a box wired to 2 circuit breakers and I don't seem to have anything like that in my box. In fact I looked at an old key to my circuit breakers and one of the circuit breakers that used to be connected is unused and the other controls some different lights. However, I did notice something about the status requests: today they started at 10:28 and ended at 16:14; yesterday they started at about 9:30 and ended at about the same time. I have solar power and this is likely the period of time when I am selling back to the utility although it could be something else. There really shouldn't be any lights on and my air conditioner, refrigerator, or freezer do not run constantly so they seem unlikely culprits. It seems likely that these X10 signals are noise getting interpreted as X10. Is there anything else I can do to clean up this and make all of my Insteon devices more reliable? Thanks.

Thank you Brian and Paul. I suspected that the storm of X10 requests is my problem. I have no X10 devices that are supposed to be J. The newest piece of electronics that I have plugged in is the water valve. The first thing I did is disable programs that might use X10 and it didn't seem to help.Tomorrow I will get a normal 3-way switch (I've corrected my terminology) to replace the X10 that is wired in and see if that has any effect. In the log that I checked today the water valve worked correctly in spite of the flood of X10 messages, but there was a change, not all of the X10 messages were X10 status requests and several were letters other than J. I do intend to convert fully to Insteon, but the remaining X10 wiring is not right for Insteon and it is now too hot in the attic to pull wire until next winter.

I recently added a new Insteon On/Off module to water my side garden along with a simple program that turns it on and off every day. However, the water often does not turn off. If I look at the log, a sample of which I have attached, it shows an error when it receives the off signal. For now, my workaround is that I wrote another program that runs a few minutes after the original program that sends multiple off commands and one of those manages to get through and turn it off. This leaves me with some questions. Why is it failing? Do I have a defective module or is there some other reason? One thing that I see in the log of some concern is that there are large number of status requests for X10 devices. I don't know why it is doing that, but I could see that maybe the network traffic is interfering with the intentional signals. I still have two legacy X10 devices in my house. One is unplugged and the is on a 2-way switch that would require significant rewiring to convert to Insteon since it is wired as a 2-way switch. I could convert it back to a manual switch if that would help. ErrorLog.txt

The absorption of the X10 signals is interesting. I've decided that I just need to not rely on X10 now that my house is mostly Insteon.

Of course after all that it worked just like it is supposed to! The only problem that I have is the the ISY-99i doesn't always see the X10 device, but that is something I can work on.

I have just converted from X10 to Insteon so I still do not have all of the Insteon controllers that I might like to have, I do have the ISY-99i and I wrote a little program to listen for an X10 command and then do something. What I have done is put all of my lighting devices into a scene. I can turn them all off or all on from the ISY interface with a single click. What I also want to be able to do is use my old X10 controllers (All lights on, All lights off) buttons to turn all the lights on or off. I like to do this when I go to bed or leave the house and have done it for years with the X10. My on program looks like this: If X10 'A/All Lights On (5)' is Received Then Set Scene 'All lights' On Else - No Actions - (To add one, press 'Action') The log file shows the X10 command being received, but the program doesn't do anything. I have alternatively written the program with the then action being a list of devices to turn off and that works when it gets the X10 command (not always), but shouldn't the scene version work?