Balok Posted February 14, 2016 Share Posted February 14, 2016 I had a six button keypad (2334-232). Button D on it was the sole member of a "follow scene". It was meant to follow my living room light, controlled by a dimmer 2477D. One program ran when the Living Room Wall Switch 'Status' was "not off" and turned the follow scene on. The other ran when the Living Roomn Wall Switch 'Status' was "off"; it turned the follow scene off. The idea was that that button "D" would track the state of the Living Room Wall Switch even if it was turned on by a scene to which button D did not belong. Button "D" was also a controller of a scene to which Living Room Wall Switch belonged. The Living Room light could be turned on using button D, Living Room Wall Switch, or from a scene activated from a different keypad, or programmatically. The idea was that button D would track the state of the Living Room even if it was later added to other scenes. And this worked fine. Then I converted the 2334-232 to eight buttons using the conversion kit Smarthome sells, removed it from the ISY and then added it back in, and - I thought - put everything back the way it was (working from notes). The ISY thinks the keypad is working properly; when I turn off the Living Room Wall Switch from inside the Admin Console, the button on the keypad shows off. But it is still lit. When pressed, it goes out. I'm not sure what the problem is, here. If someone with some experience in follow scenes or converted keypads has seen something like this, I'd appreciate hearing about it. Or maybe I'm trying to do something too complicated and there's a better approach. Thanks. Link to comment
oberkc Posted February 14, 2016 Share Posted February 14, 2016 "The ISY thinks the keypad is working properly; when I turn off the Living Room Wall Switch from inside the Admin Console, the button on the keypad shows off. But it is still lit. " That statement makes me suspect communication problems, or link record errors. I would be comparing link records between keypad and ISY, perhaps restoring the device if necessary. Do you have latest software for ISY? Link to comment
Balok Posted February 14, 2016 Author Share Posted February 14, 2016 I'm running 4.2.30. I've experienced no reported errors. I tried using Restore Device (from the Admin Console) on all involved devices under the theory that one of them had become corrupt. This behavior started when I converted the 6 button keypad to an 8 button, which makes be suspicious that either there's some kind of error there, or some kind of problem with the way the ISY handles converted keypads. I notice, for example, that it continues to call the keypad a "(2334-2) KeypadLinc Dimmer 5 buttons v.43". However, when I added the converted device the ISY correctly detected 8 buttons. In addition, the 8 buttons all work (can be added to scenes and can then control them properly). Link to comment
LeeG Posted February 14, 2016 Share Posted February 14, 2016 The KPL is manufactured as a 6 button device. That is why the ISY indicates it as a 5 node device. If properly converted to 8 button mode it will have 8 nodes. Should be on 4.3.26 which is an Official release, or 4.4.3 RC1. One of the possible issues is the button D on a 6 button device is button F on an 8 button KPL. If the Programs are referencing button D the wrong button is being referenced. Are the Programs referencing button D or button F? Link to comment
stusviews Posted February 14, 2016 Share Posted February 14, 2016 When you convert from 6-button to 8-button, the designation of the buttons change. The On-button splits int o A & B, A becomes C, B becomes D., C & D become E & F, respectfully and the Off-button becomes G & H. You need to check each and every former scene involving each button. The easiest way to do that is to select each button and review the Membership panel located on the right side of the screen. Link to comment
Balok Posted February 14, 2016 Author Share Posted February 14, 2016 The KPL is manufactured as a 6 button device. That is why the ISY indicates it as a 5 node device. If properly converted to 8 button mode it will have 8 nodes. Should be on 4.3.26 which is an Official release, or 4.4.3 RC1. One of the possible issues is the button D on a 6 button device is button F on an 8 button KPL. If the Programs are referencing button D the wrong button is being referenced. Are the Programs referencing button D or button F? Yes, that's what I assumed about the name - it's just an artifact. The ISY does see all eight "nodes" or buttons, so I am sure I have converted it properly. I checked the release notes to see if an issue of this sort was mentioned, and it was not. I generally do not upgrade software unless I am trying to fix a problem that I know the upgrade addresses. Upgrading "because it's there" has disappointed me on a few occasions, and broke me of the habit years ago. I did check the program to ensure it was addressing the correct button. I'm certain that's not the issue. Link to comment
Balok Posted February 14, 2016 Author Share Posted February 14, 2016 When you convert from 6-button to 8-button, the designation of the buttons change. The On-button splits int o A & B, A becomes C, B becomes D., C & D become E & F, respectfully and the Off-button becomes G & H. You need to check each and every former scene involving each button. The easiest way to do that is to select each button and review the Membership panel located on the right side of the screen. This check was among my debug efforts, yes. All the buttons command their scenes/devices properly, except the one that's supposed to respond to the follow scene. Link to comment
oberkc Posted February 14, 2016 Share Posted February 14, 2016 Sounds like it may be time to consider the possibility of a comm problem. A simple experiment would be to find an extension cord and plugging into an outlet on the same circuit as the keypad and temprarily plugging in the plm to that. Were that to solve the issue would be an indication of a communication problem. Link to comment
Balok Posted February 18, 2016 Author Share Posted February 18, 2016 It is not a comm problem. I temporarily reassigned a button on an eight button keypad that's in a table enclosure, positioned it as electrically close to the wall-mounted keypad as was feasible, and it behaved correctly. In addition, all other buttons on the wall mounted keypad work fine and reliably. Finally, the wall mounted keypad used to work fine, until I changed it from a six to an eight button keypad. Something about doing that affected the way the keypad handles this kind of scene. It's not a big deal; at some point I'll replace the six button keypad with an eight button keypad. I'm posting this mostly so that folks know that a six button keypad transformed to an eight button keypad is apparently NOT the same thing as an eight button keypad right out of the box. That, or there is some difference about how the ISY handles a six button keypad changed to an eight button keypad. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.