Harold

Sorry if I was not clear. I have a 99i. Is there an upgrade to 994 hardware.

Is there any upgrade path for 99i owners to the 994i? Would it make sense to do it if there was a path?

Is this possible on the 99 version as well?

1 - Replace the keys and install switch. 2 - Pull out the disconnect tab at the bottom (it will stay out - go have a beer) for maybe 5 seconds - more is OK. 3 - Hold keys main and H, push the tab back in. Don't depress it. Just put it back where it was. Wait for noises. If you had a lot of these and followed the beer step, find a sober assistant. 4 - Set Admin console to "Start Linking". 5 - Depress the same tab into the switch. Hold it for 5 seconds or until it makes a funny noise. 6 - Finish the linking task in Admin. 7 - Rejoice. You just bypassed a day of exasperating work.

That is what I thought.

I am hurting my head. I thought I had figured out how I wanted to make a consistent button assignment on keypad controllers by function. What I forgot is that button #1 always controls the load of the switch it is in. Be gentle. This is my first attempt at doing this sort of thing. I do have some issues about logical functioning in the programming screens/paradigm. A once removed language that implemented functions vs what is currently used for programs/scenes would, I think, be real useful. Data in screens is limited. Ability to change things in the screen in which they are displayed is a bit spotty (i.e., more options should be included). The ability to manipulate (or even enter) data shown in the Topology screen seems to be non-existent. Screens use a lot of space to provide less information than is useful/necessary. Why is there not a screen for programming that shows both name and address? It does not appear that you can edit a scene. Delete yes; alter no. Remember I am trying to to this for the first time using available documentation. I am having difficulty in following the logic of the programming/control interface architecture. What I was trying to implement is to make the first button (#1/Main) control the light of the major area you are entering. This is what I did for the manual switches there are replacing. I did this by making a scene and putting button 1 of the 3 or 4 keypads in the first scene. This scene to correspond to the lighting group based on the desired assignment I explained above. Of course this screws up things since each #1 button directly controls the connected load as well as any other buttons in the scene. It was a pretty stupid oversight; but my thinking is that it should actually work that way. I know it is way to late for Insteon to change this behavior but it would simplify the human interface to have all buttons be able to be disconnected from physical control. Like the local load could be able to be mapped to say hex I. I don't think there is any way to eliminate the native control response for button 1. My solution is to implement my preferred scenario starting at button #3 (C hex). This essentially removes two of the keypad buttons from my available buttons. This presumes I want to start on the first left hand button for consistent usage. Thoughts? Short form question: Is there a way to isolate button 1 from the function of turning on the locally connected load?

Everything is fine. It was just having reset pressed.

NO! That was the problem. I misinterpreted/misread the instructions.

The buttons are not changing to 8. ISY firmware current. I have left the reset tab out for minutes. In for a long time with upper left and lower right buttons depressed before and during pressing in the reset tab. No matter how long I keep the reset depressed the switch does nothing apparent. When I release the reset, in a couple of seconds it turns on the load and lights the top two buttons. Cycling makes no difference. It is still operating as a 6 button. Toggling alternately activates the top and bottom two button lights.

I have a bunch of controls that were initially configured as 6 key. I put the 8 key keypad set on. I have tried multiple times and with some variations in technique, and I just can't get them to be recognized on the ISY as 8 key. I have pulled out the the little pin that powers off the keypad. Then pressed in the pin while holding keys main and H. It just is not working for me. Can anyone supply the correct process steps?

OK. Probably not the way I would have designed it, but what is;is.

That makes sense. I had assumed that the PLM would buffer.

Thanks Lee. I wonder why they made the speed so low and did not allow it to be adjusted. Certainly the chips can do better. And I can't help thinking the CPUs can handle more. It may not matter; but why limit it to the way it was 10 or more years ago?

I just received an Insteon 2413S to replace a 2412S that another thread here has determined to be broken. I have a couple of questions. 1 - What frequency does the Insteon RF use? I have seen mention of issues with wireless telephone interference in posts on this site. But I believe Insteon uses a 900 MHz band signal and all my phones are DECT 6. The DECT 6 frequencies are not in the 900 MHz band. Is that correct? 2 - No documentation I have found indicates that the wire link between the 2413S and the ISY-99i can be an Ethernet cable as it was on the 2412. The cable provided with the 2413S has a DB connector at one end and no documentation that talks about the ISY. Is an Ethernet cable between the 2413S and the ISY-99i port Port A correct? 3 - There are essentially no RS-232 chip sets that are not faster than 19.2. Is there a way to increase the speed of the link between the 2413S and the ISY-99i?

Thanks. I looked in there but just did not see it.

How much current does the ISY require? I believe it is 12V; how much current? Second question. Is there any significant reason I should upgrade to an ISY-994 Pro? As far as I can tell, it lets me plug other radios in, but I don't see anything else.

Thanks. When I was looking for trouble shooting info I missed that table. I will try a new Ethernet cable first. Assuming the PLM is broken. Is there any significant advantage to also upgrading the 99i to the 994i? I currently have the ISY 99i/IR Pro. I did not see anything different looking at the product descriptions except being able to plug in different radio cards. The cable was fine. I need a PLM. An interesting thing I noticed while looking at Smarthome. They actually still sell a 2412 PLM, but it is N - direct Ethernet connection. That would be a useful interface if the ISY could use it.

The white led on the PLM is on. I have removed the PLM from the power outlet for several minutes (several times) and re-inserted. The Rx light on the ISY is on. It seems to me that it was normally on, but I am not sure. It has been awhile. I also tried a factory reset on the PLM. No change except all the Insteon devices are now gone (as expected). Somewhere I think I have an old Smarthome X-10 PLM. If I could find that, is there anything that it might be able to do to help diagnose what is happening?

My Insteon has been sitting here for a couple of years. I am not using anything except links set directly from the installed switches. I have a PLM 2412S and Isy 99 installed. They have been working fine, although I have not used them other than to find all the installed Insteon devices. From time to time I have updated the I99 firmware. I have multiple access points installed. I just updated to the current RC. When I start the Isy all the installed devices are shown in red. It says I am in safe mode which is usually caused by a bad PLM (or connections). If I use tools, diagnostics, plm info/status I get nothing at all. No response. I just did a factory reset on the PLM. As I anticipated (perhaps in error) the list of devices is now empty, still no response to the info/status command. I have read a bunch of threads on the site. One resembled my problem rather closely, but ended in "it works now". Is there a way to test/evaluate the PLM? To the best of my knowledge I have not changed anything that is likely to affect this interface since the last time I used it. I have no trouble lights on the Isy. Power and Rx are lit. I would prefer not to just buy a new PLM to see if it helps. Particularly after reading a rather long thread about the 2312 vs the replacement device. Any suggestions?

I am reasonable sure I saw a program contributed that dealt with this task. I have tried a bunch of searches in this forum and the one on education and programming with no luck. Does anyone know off hand where this link/program might be?

Michel, Yes it is a Pro. I had to completely rebuild the computer after a motherboard failure and just lost track of the cable. I used it previously to resolve some issues of addressing and get things going. I would be grateful for a replacement rather than trying to find it. I really do have a large number of accumulated RS232 cables from the age when they were the primary interface. And I tossed the cable into that batch which has also been relocated. I just did not think bout the different cable when my computer fell apart (twice within a month). I would very much appreciate your sending me a cable. It will save me a whole lot of tedious searching. I will send you a PM with the mailing address. Thanks, Harold

Am I correct in assuming at this point that there is no way to visually identify the nul-modem cable shipped with the ISY99? Assuming this is true, may I suggest that you make them identifiable.

I have already done the factory reset. I thought the factory reset would put the user/password back to the factory default. The problem is that the ISY99 just does not seem to appear in my network. It is not that the console software can't log in, it can't find the ISY. Windows networking does not see it either.

Sorry, my original post is not particularly informative. I am trying to use a terminal emulator through the RS 232 connection. The RS232 null modem cable is what I am talking about. I can't find the ISY99 on the LAN so I am trying to get in and configure it.

It is an ISY99. I just need to know if the cable is marked or visually identifiable in some way. I have a lot of cables in a box. Your nul-modem cable is one of them. Checking the pin connections on each cable until I find it will be annoying. No real walking to do at this point. Maybe after I get the terminal to talk to the controller I will still have a problem, but I think if I just get that going I should be OK.