AZPhil

@lilyoyo1, @kclenden, @MrBill: Thanks for all your help. I have it working correctly now. I first ran the "Generate Topology" tool to provide an easy-to-use reference for reconstructing the button allocations. Then removed the device from the ISY, factory reset it, and re-added it to the ISY and renamed everything to their previous names. Then relinked the buttons per the previous topology. That fixed it. I pretty much assumed that was the way it worked. The log shows no communication traffic. It just shows the commands that were issued. All of the links were set up correctly. There was just something hidden that was preventing "G" from responding to network On/Off commands. My mentioning the labeled "type" in the admin console was a red herring. I believe the KPL did originally have a 6 button face which I replaced with an 8-button face. However, I have three 2334-2 KPLs configured with 8 button faces and all three are recognized as "Keypadlinc Dimmer 5 Buttons" in the admin console in addition to three others that are configured with 6 button faces. Nevertheless, when linked, the console generates the number of buttons that are actually configured to work for each device. My guess is the console program simply pulls text from a type table based on a part number it reads from the device.

I'm not sure this is the correct place because I don't know if communications is the issue. Every Insteon device in the home is dual band, so virtually all signalling is done by RF. Device with a problem: An Insteon KPL (2334-2, V.45, configured as 8-button pad - although ISY console labels it as 5 buttons.) All of the buttons on this pad work fine except the "G" button. Several of the buttons on the pad control scenes that have multiple controllers, such as buttons on other keypads. All of the scenes and controllers work correctly except for button "G" on the controller in question. The G button works perfectly as a controller but refuses to act as a responder. Meaning, when a different controller is used to turn on the scene controlled by button G, the LED on button G does not go to "ON" state (although the console shows it as ON), and also if it is manually turned ON, it does not go to OFF state when a different controller turns off the scene. All cases are set up identically. A device or group of devices is assigned to a scene. Buttons on multiple keypads are added to the scene as controllers as well as the devices themselves if they are single control devices. All of the controllers also act as responders when the scene is controlled elsewhere. This particular scene contains a pair of wall sconces in a hallway that were originally wired with standard 3-way switches using a "traveler" wire at each end of the hallway. The "master" switch (the one with a direct "hot" wire) now has an Insteon 2477S relay as controller, and the "slave" end has a 2487S configured as a 5 button KPL. The "Hall" scene contins both of these as a controller, and four other KPLs each have a button that is added to the scene as a controller. When the "hall" button is pressed on any of the controllers, the lights come on and all of the LEDs associated with hall scene controllers light up. Except button G on the subject pad. Yet, G works perfectly as a controller, and all associated LEDs elsewhere light up to indicate the state of the sconces. The event log seems to show the signals being sent and the ISY console says the button is in the correct state. Except it isn't. Color me baffled.

Never mind. Restore Device seems to fix it. This seems kind of bizarre, but evidently 2342-2 remotes must be restored following a PLM reboot...

I have several programs whose "IF" clause is based on mini controller button pushes. These programs have been running correctly for several years. On 11/25, the ISY and Insteon PLM were moved from one room to an adjacent room together with all network related gear such as router/modem etc. Since the move, all Insteon activity is working EXCEPT programs that rely on mini controller button pushes. Those have ceased working from mini controller action. The programs still work from the admin console if the "Then" clause is manually requested, but not when the associated button is pushed on a mini controller. This behavior occurs even with the mini controllers sitting on the same desk as the Insteon PLM sitting less than a meter away. How do I restore previous behavior? (Using ISY994i with Insteon 2413S (dual band) PLM. ISY is at level 4.8.)

Never mind. Restore device X removed the links to the nonexistent device from both the ISY and device X. Whew. It would be nice if the manual or the wiki noted his.

You guessed it. The nonexistent device is a 2413U controller that was used with HL. I have mini keypads that blink red furiously after every button push because they never get acks from that now nonexistent PLM. I removed every device from every scene of that PLM (in the isy994i console), then removed every scene. Many links are marked deleted (22 flag) but numerous live links remain in device link tables, all of which are also in the ISY tables. (A2, AA, E2 flags to turn scenes on or off) Seems like the obvious way to eliminate the ghost of the dearly departed would to simply mark every link with a 22 flag.that has its ID But how? I have looked high and low for obviously needed link table management functions, but if they exist they are well hidden.

I compared the links table yesterday. Every entry was marked either "Identical" or "Identical/Ignore". There were 108 entries. I presume the "Ignore" entries were entries marked deleted that were previously used by the PLM connected to HL. I didn't consider that a problem except for clutter in the . Since the reset+restore, there are now only 62 entries, all of which are marked "identical" except the final, all zeroes entry. I think the error was not the links table, but was probably some internal thing related to my not doing the manual 6==>8 button-pressing procedure before loading up the links. Whatever. I noticed this morning something I hadn't noticed before. A few seconds after pressing any button on the KPL, the LED behind the set button would flash once in color red (very dim). Since the KPL was reset, the LED now always flashes green (fairly bright, much more noticeable than the red). Clearly the red LED was trying to tell me there was an issue. Wouldn't you think the brighter light should be the error light? Insteon engineers evidently do not agree. BTW: I added the complementary program that turns the master button ON when at least two of the lamp modules are ON. Duplicated the OFF program with "COPY", renamed, changed "is" to "is not" in the IF clause, OFF to ON in the THEN clause. This all "works a treat" now. I gave up trying in HL. The lack of an "OR" capability made things just way too complicated. Master MBR Button On - [ID 0009][Parent 0001] If ( Status 'MBR Dresser Lamps' is not Off And Status 'MBR Bed Lamps' is not Off ) Or ( ( Status 'MBR Bed Lamps' is not Off Or Status 'MBR Dresser Lamps' is not Off ) And Status 'MBR Corner Lamp' is not Off ) Then Set Scene 'Scenes / KPL MBR Scenes / MBR--Master Button' On Else - No Actions - (To add one, press 'Action')

Factory Reset + 6==>8 + Device Restore did the trick. The program now works! I first tried just performing the 6==>8 change procedure. Scene still failed the diagnostic test. Then I removed the button from the failing scene and added it back to the scene as a responder. The scene then passed the diagnostic test. However: Still no joy on turning off the button with the program. (Program ran, status True, LED still on.) So, failing the scene diagnostic really was not the issue. Then I bit the bullet: Factory reset; Perform the 6==>8 procedure; Restore the device. Voila! Program ran and turned off the LED. Problem solved! Seems like factory reset is the solution to most unexplainable issues. The program: MBR KPL D Button Off - [iD 0006][Parent 0001] If ( Status 'MBR Dresser Lamps' is Off And Status 'MBR Bed Lamps' is Off ) Or ( ( Status 'MBR Bed Lamps' is Off Or Status 'MBR Dresser Lamps' is Off ) And Status 'MBR Corner Lamp' is Off ) Then Set Scene 'Scenes / KPL MBR Scenes / MBR--Master Button' Off Else - No Actions - (To add one, press 'Action')

Fascinating. I would never have figured that out as the cause of the issue. I will mess with that tomorrow. Thanks a heap!

Sun 06/11/2017 05:29:06 PM : [GRP-RX ] 02 61 27 13 00 06 Sun 06/11/2017 05:29:07 PM : [CLEAN-UP-RPT] 02 58 06 Sun 06/11/2017 05:29:07 PM : [iNST-SRX ] 02 50 3D.8D.2A 44.30.E6 E5 13 FC LTOFFRR(FC) ----- MBR--KPL-D-button Test Results ----- [Failed] MBR KPL.D (3D 8D 2A 4) ----- MBR--KPL-D-button Test Results ----- Sun 06/11/2017 05:29:14 PM : [iNST-TX-I1 ] 02 62 00 00 27 CF 13 00 Sun 06/11/2017 05:29:14 PM : [iNST-ACK ] 02 62 00.00.27 CF 13 00 06 LTOFFRR(00)

I will start with the log, and proceed from there. Something like the really detailed logging in HL would be nice. Where do I find the program log? Seems to be well hidden!

In point of fact, as I reported, I had already tried manually turning the scene on and off with the console. That worked fine. I wasn't previously aware of the "run then" feature. Thanks for that tip! Just tried that, and the button turns off. However, when the full program runs when triggered by a button change event, only the reported state changes, not the actual button. Very confusing. Some kind of timing issue maybe?

isy994i, running 4.5.4. The objective is to manage one KPL toggle button under program control. The button to be managed is a controller of a scene that has several devices as responders, as well as several several KPL buttons that correspond to the responding devices. When the button LED is turned ON because of the button having been pressed to turn on the multidevice scene, several other button LEDs on the same KPL turn on to reflect the ON state of the device each of the buttons controls. In effect, the button is question acts as a master button. But a master button becomes superfluous when only one device and its dedicated button are all that remains. Therefore, when the master is currently ON, the desire is to turn the master button OFF after some devices in the scene have been turned off under separate button control. Having read through various "howtos" in this forum, my understanding is that the correct (and apparently, only) way to turn a KPL button on or off under program control is to create a scene containing the button and have the program turn the scene on/off. Therefore, a scene was created which contains the button in question, and only that button. Note: The button is a responder in exactly two scenes: The single button scene, and the master scene for which the button is a controller. With the button scene selected in the admin console, clicking the "on" and "off" controls at the bottom of the window turns the LED on and off. (I visually inspected the KPL after each command.) I then manually pressed the master button, turning on the master scene, and then repeated the test in the admin console. Same result: LED turns off and on under console control. So far, so good. Turning the button scene on/off turns the button on/off. On to programming the button state. A program was written to turn off the scene when a button turns OFF while the state of other devices is OFF. The "Then" clause is of the form: "Set Scene '(the button scene)' off" The program appears to work perfectly. When the program is triggered and the "If" clause evaluates as true, the button is turned OFF as evidenced by the admin console reporting both the button scene state and the button state itself changing from "ON" to "OFF". The problem is, despite the "off" state of both the button and the button scene as reported by the console, the actual LED behind the button remains quite visibly on at 100% brightness! Also, the toggle state of the button is exactly as it appears visually, not as reported in the console. Pressing the button turns OFF the master scene, and the button LED. Pressing it again turns on the whole master scene. From all appearances, it seems as if the isy is marking the scene and device states as off as commanded to do by the program, but the isy is not sending an appropriate command to the device to actually turn the LED off, or change the toggle state of the button. I don't want to simply manage a state variable, I want to actually toggle the button on or off, together with its LED. And I certainly don't understand having both a scene and the only device in the scene being reported as being in the OFF state when visual inspection clearly reveals the actual device is ON. What am I missing? Perhaps of interest, perhaps not: The KPL device is a 6-button 2334-232, converted to an 8-button KPL when installed.The actual device is marked Rev. 7.7 datecode 4315. HL correctly identified it as a 2334-232 with 8 buttons. The device reported itself in HL as 0x01.0x42.0x45. The KPL is identified in the isy admin console as "(2334-2) KeypadLinc Dimmer 5 Buttons v.45". Not sure why it is identified in isy as having "5 buttons". However, the isy correctly set up the 8-button KPL as having 8 named buttons. All of the 2334-232 KPLs (most being used in 6-button mode) are identified the same way, The "LED Brightness" button control on the device page for all of the KPLs reports both "on level" and "off level" as having value "0". I would expect this button to report the actual LED brightness as currently set in each KPL.