nowandthen Posted February 3, 2012 Posted February 3, 2012 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.
apostolakisl Posted February 3, 2012 Posted February 3, 2012 2876db is programmable from isy the same as a 2476d is. I don't know what your issue is. Perhaps a factory reset will get you back in order?
Teken Posted February 3, 2012 Posted February 3, 2012 I would ask you to first upgrade the ISY's firmware to the latest official 3.XX. As this has resolved a lot of Insteon issues as well as added support for various devices, and features. Next, I would ask you to remove the Icon device, perform a hard factory reset. Then, add the the Icon device via the automatic discovery. Then, try the same changes via the ISY Admin Center. Teken . . .
nowandthen Posted February 3, 2012 Author Posted February 3, 2012 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!
LeeG Posted February 3, 2012 Posted February 3, 2012 nowandthen Does the ISY show a firmware level for the ICON switch or is it v.00. If v.00 the ISY may be using the I1 technique to set On Level (applied locally) which can require a device power cycle to pick up. If the firmware shows as v.00 delete the device from the ISY and add it back using Auto Discover. Then try setting the On Level (applied locally) again. This should be done with the latest official release 3.1.17. If that does not work run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected and set the On Level (applied locally) to some new value and post the event log. Lee
nowandthen Posted February 4, 2012 Author Posted February 4, 2012 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?
LeeG Posted February 4, 2012 Posted February 4, 2012 Start Linking is fine. The device identifies itself as far as Insteon address and firmware level. I prefer New INSTEON Device so I don't have to go back and rename the node from its Insteon address to a meaningful node name but that is just personal choice. Start Linking is a good way to add a device particularly if you do not know the Insteon address and don't want to take the switch cover off. Lots of water under the bridge between 2.8.16 and 3.1.17. No way to know if it was the way the device was originally added or some ISY change along the way. The important thing is its working now.
Recommended Posts