oskrypuch Posted April 16, 2011 Share Posted April 16, 2011 Well, just replaced a keylinc that had its tables scrambled, that was a story and a half. In any case, all is working EXCEPT the new keylinc is not responding to LED brightness commands. v5.1 2486D, originally a 6 key switch. It DOES respond to BEEP. Dimming the keylincs in the bedroom is critical for WAF. Is it a firmware issue? I have tried factory reseting, then setting to 8key ops, and then restoring from ISY. No change. * Orest Link to comment Share on other sites More sharing options...
fitzpatri8 Posted April 16, 2011 Share Posted April 16, 2011 Check the keypad's owner's manual, you can make that adjustment manually in the meantime. Link to comment Share on other sites More sharing options...
oskrypuch Posted April 16, 2011 Author Share Posted April 16, 2011 Only an issue for some firmwares? My other keylincs with the current 3.1.2 beta do dim/brighten. Will check the docs for the manual adjustment, thanks. * Orest Link to comment Share on other sites More sharing options...
fitzpatri8 Posted April 16, 2011 Share Posted April 16, 2011 Hold on...what version is the ISY reporting for the new keypad? Link to comment Share on other sites More sharing options...
oskrypuch Posted April 16, 2011 Author Share Posted April 16, 2011 Ha, I think you are on to something. The LED brightness non-responding unit shows 2486D KeypadLinc Dimmer v .00 The others show ... 2486D KeypadLinc Dimmer 6 Buttons v.35 and v.36 I did add the errant dimmer using the New Insteon Device, specifying a 2486D. Do you need to use autodiscover to show the version? * Orest Link to comment Share on other sites More sharing options...
LeeG Posted April 16, 2011 Share Posted April 16, 2011 Yes, to the question of getting the version number. Likely the ISY is using the old I1 technique since it does not have the firmware version. Running the event viewer with device communication events while updating LED level will confirm that. EDIT: there could be a problem using Auto detect. If that is a 6 button KPL by manufacture the cat/subcat will indicate a 6 button KPL even if configured to 8 buttons. Not sure if device add looks at the actually KPL configuration to determine 8 button mode when using auto detect. Link to comment Share on other sites More sharing options...
oskrypuch Posted April 16, 2011 Author Share Posted April 16, 2011 This is a 6 button kpl by manufacture. So, is that a problem if configured for 8 buttons, as it is? * Orest Link to comment Share on other sites More sharing options...
oskrypuch Posted April 16, 2011 Author Share Posted April 16, 2011 On writing a ... All ON' On 0 / off 0 (Backlight Level) to the device in question, the event log indicates ... [All ] Writing 2 bytes to devices * Orest Link to comment Share on other sites More sharing options...
LeeG Posted April 16, 2011 Share Posted April 16, 2011 Not sure if that combination is a problem. In Auto Detect mode the ISY uses the device cat/subcat value to determine what type of device is being added. The KPL does report itself as a 6 button KPL as far as the cat/subcat value regardless of whether it has been configured as an 8 button KPL. The effect may be that the ISY does not know to use I2 to configure the backlight level. I have a 6 button KPL that I added as you did manually as an 8 button KPL. I'll run a test, removing it and add it back using Auto Detect. The question is whether the ISY will ignore the 6 button cat/subcat value in favor of the 8 button configuration information. I'm concerned the ISY will add the KPL as a 6 button KPL with 5 unique nodes rather than with 8 unique nodes if using Auto detect. I'll post back later tonight after running the test. EDIT: note that the event viewer trace has to be run with Device communications events selected to know if I1 or I2 configuration is being used. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.