Tmc

Thanks Indy, I'll try the Excel Import sometime. I finally replaced my 2412S with the 2413S PLM the other day. After that I was able to get my new 6 Button Keypad added to eisy and programmed as I wanted. But I have been a bit disappointed, I was hoping the new PLM would clear up my 10+ devices eisy is Unable to Communicate with. If anything, now there seems to be even more devices gone deaf and dumb. Is it possible there are older devices that the 2413S can't communicate with? Would I be better off going back to the 2412S?

Okay, did a Restore of my 18 yr old 2412S PLM. The address of the deleted device no longer appears in the links table, as expected. What I didn't expect is the number of links increased from 331 to 347. I don't need an explanation, it's just interesting. I still intend to replace it with my new 2413S PLM. Probably tomorrow. I'll use the procedure provided by Techman. Thank you for that!

IndyMike, What you're doing is interesting, but way past my understanding. I do have a couple questions. 1. Your screenshot of your links table is quite different than mine. Looks like a spreadsheet view where you have the filter buttons at the top. Mine looks like: 2. When I save the table I get a pdf file that doesn't make any sense to me. 3. Link 325 (71.22.A6) is the device that I deleted. 4. About a week ago my PLM Links Table had 418 Links. Today it shows 331 links. I didn't add or remove any devices. Why would the table change so much? Still haven't attempted replacing the PLM or Restoring it. May try the Restore first, maybe today.

Thanks IndyMike. I will look for the "22". I have replaced quite a few broken devices over the last years, but never have I done a PLM Restore. That might clear up a few other communications issues I'm having (hence deciding on a new PLM). I will try that before I replace the PLM and see what happens. But I'll have to do that tomorrow as I've run out of time today. Thanks everyone for your help!

The device was not removed from the old PLM. Haven't tried switching to the new one yet. Thanks for moving my query, I'm not fluent on what the IoX is.

I was having trouble adding/programming a new "Dimmer Keypad, 6-Button,2334-232" to my eisy. From other contributors I hear this is really a 5 button device, which is why a 6-button isn't listed in the Add Device Table. I find that really confusing, but that's not my question. I am going to replace my 18 year old PLM 2412S with a new PLM 2413S and decided to Delete the 2334-232 and try adding it again with the new PLM. I ran a PLM Links Table and was surprised that the Insteon address of the device still appeared in the PLM even though I Deleted it from eisy. Is that correct, addresses don't get removed from the PLM when a device is deleted from eisy? Thanks for your Thoughts.

Sorry I didn't help. There's a "My ISY" button on the UDI Home page. Maybe that would get you a matching version of the Admin Console. Otherwise hopefully someone more experienced can help you. Good luck!

Did you delete Java Apps too? Doing that dumps the ISY Finder App so you have to download a new one that matches your updated firmware.

WOW! That explains almost everything! Even the problems I had back at item 5. in my original post list. Is this documented somewhere? At my work we'd call this "Tribal Knowledge." So yes, I was able to program other controllers and get Ramp Rates I wanted. Using the ISY Console doesn't trigger the changed Ramp Rate. It won't surprise you that MobiLinc won't trigger it either, since it uses the console control. Okay, so I moved the FanLinc Light Ramp Rate slider from about 26 seconds to 1 minute. Here is the Event Log: Tue 05/07/2013 09:16:02 PM : [ 21 D8 26 1] RR 12 Tue 05/07/2013 09:16:02 PM : [iNST-TX-I2CS] 02 62 21 D8 26 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Tue 05/07/2013 09:16:02 PM : [iNST-ACK ] 02 62 21.D8.26 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Tue 05/07/2013 09:16:03 PM : [iNST-SRX ] 02 50 21.D8.26 11.D0.DD 23 2F 00 (00) Tue 05/07/2013 09:16:03 PM : [std-Direct Ack] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Tue 05/07/2013 09:16:04 PM : [iNST-ERX ] 02 51 21 D8 26 11 D0 DD 17 2F 00 00 01 0F FF 00 A2 00 11 D0 DD FF 1F 01 43 Tue 05/07/2013 09:16:04 PM : [Ext-Direct ] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 05/07/2013 09:16:04 PM : [iNST-TX-I2CS] 02 62 21 D8 26 1F 2E 00 01 05 0C 00 00 00 00 00 00 00 00 00 00 C0 Tue 05/07/2013 09:16:04 PM : [iNST-ACK ] 02 62 21.D8.26 1F 2E 00 01 05 0C 00 00 00 00 00 00 00 00 00 00 C0 06 (00) Tue 05/07/2013 09:16:05 PM : [iNST-SRX ] 02 50 21.D8.26 11.D0.DD 27 2E 00 (00) Tue 05/07/2013 09:16:05 PM : [std-Direct Ack] 21.D8.26-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 I have no idea what that means. Hope you do. After I did that, I unpluged the fanLinc and plugged it back in within 3 seconds. As you suggested, the 1 minute Ramp Rate is now effective from both the ISY console and MobiLinc. I've been using ISY-99 for about 4 years. I have never run in to this until after I upgraded the firmware to 3.3.10. I'm not sure what I was running before that. Think I upgraded about a year earlier, so not real old. Do you have a fix in mind for this? I saw you don't intend to provide any more updates for -99 units. Too bad. If I can run any more tests for you, let me know. I have a workaround now, just cycle power on units. For the InlineLincs I have installed, guess I can just cycle the circuit breaker. Thanks for pointing me in the right direction. -Tim

Lee, I have not been using a separate controller, just the ISY console to set the FanLinc Local Lamp Ramp Rate, and using the console to turn the FanLinc Lamp on and off after each attempt to change the rate. After attempts to set multiple different rates I used Tools and looked at the Device Table and Compared it to the ISY table many times. The tables always matched, and they never changed from one rate to another. When attempts to change the FanLinc local value appeared not to work, I also did a "Restore Device" a number of times, to no avail. I have not used the Event Viewer. I will do that, hopefully tonight, and post my results. I'll post the links tables too. Thank you for the suggestions, -Tim

Background; may or maynot be relevant: 1. Fall 2012 some major transient fried 25% of my controllers, most on same circuit. 2. Winter 2012 installed Leviton 51120-3 whole house transient protection. 3. January 2013 updated ISY-99 Firmware to version 3.3.10. 4. Started perodically replacing fried controllers. 5. Had trouble programming Ramp Rates on some devices, but didn't investigate. This weekend Prepared to install a brand new FanLinc. I have it mounted on a test board where it is powered and attached to 110 vac lights representing the motor and light. I do this so I'm not running up and down a ladder while programming, and if any problems. ISY discovered the FanLinc with no problem. Motor control works with no problem. The light will turn On and Off from ISY okay. The problem is changing the Ramp time from ISY has no effect. I use the ISY Admin Console from 2 different computers, one direct LAN and the other Wifi. Both seem to work okay, but just to be careful I cleared the Java cache again on both PCs. No improvement. From another post suggestion I did the "Query Insteon Engine" for the FanLinc. It is v.41 I believe. That had no effect. The most surprising effect is that if I unplug the FanLinc from house power, then plug it back in again, it magically uses the most recent Ramp Rate that I tried to program. Even though that rate was not working before I unplugged the FanLinc. Do you have any thoughts on what might be going on here, and what I can do to fix it? Thanks, -Tim Carlson