Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Bug?: i3 4 button KPL showing 1 too many nodes

Featured Replies

We would need to see the scene setup. The issue with the "old" method was button "A" and load "1" where always grouped together. While this worked if button "A" was the linked to load "1" in "Flags" it broke if the load was changed to another button.

It could have been that the links were incorrect, due to the "bug" in before the fix which was causing issues.

In any case it sounds like it is working now?

  • Author
1 hour ago, Javi said:

We would need to see the scene setup. The issue with the "old" method was button "A" and load "1" where always grouped together. While this worked if button "A" was the linked to load "1" in "Flags" it broke if the load was changed to another button.

It could have been that the links were incorrect, due to the "bug" in before the fix which was causing issues.

In any case it sounds like it is working now?

I just noticed we have moved on to page 2 and didn't your post. Look at the previous post which I changed to state what I believe is the issue, at least on my computer (Windows 10 using Firefox). I also cleaned up the post before that, since so much of that was trying to figure out the problem.

I have both new i3 keypads working as intended.

Thanks for hanging in there with me.

Edited by nowandthen

@Javi Sorry for the delay in responding, but I’ve done some more testing and am still seeing some unexpected behavior with the I3 keypads. 

Here's the basics ... I have two I3 4-Button keypads that work in tandem to control two loads and several scenes together.  Here is how the switches and associated scenes are set up:  

Keypad 1 (MBath Lights New) setup is:

  •  Button A (LOAD):

    • MBath Lights New (Ctrl/Rsp)

    • MBath Combo New (Responder)

    • Upstairs Lights (Responder)

  • Button B:  

    • MBath Towel Warmer (Ctrl/Rsp)

  • Button C:  

    • MBath Combo New (Ctrl/Rsp)

  • Button D: 

    • MBath Fan New (Ctrl/Rsp)

    • MBath Combo New (Responder)

Keypad 2 (MBath Fan New) setup is:

  • Button A

    • MBath Lights New (Ctrl/Rsp)

    • MBath Combo New (Responder)

    • Upstairs Lights (Responder)

  • Button B:  

    • MBath Towel Warmer (Ctrl/Rsp)

  • Button C:  

    • MBR Closet (Ctrl/Rsp)

    • Upstairs lights (Responder)

  • Button D (LOAD): 

    • MBath Fan New (Ctrl/Rsp)

    • MBath Combo New (Responder)

Scenes:

  • MBath Lights New

    • MBath Lights New (Controller)

    • MBath Fan New A (Ctrl/Rsp)

    • MBath Lights New A (Ctrl/Rsp)

  • MBath Fan New

    • MBath Fan New (Controller)

    • MBath Fan New D (Ctrl/Rsp)

    • MBath Lights New D (Ctrl/Rsp)

  • MBath Towel Warmer

    • MBath Fan New B (Ctrl/Rsp)

    • MBath Lights New B (Ctrl/Rsp)

    • MBath Towel Warmer (Controller)

    • Shelly 1 Mini (Responder)

  • MBath Combo New

    • MBath Combo New (Controller)

    • MBath Fan New A (Responder)

    • MBath Fan D (Responder)

    • MBath Lights New A Responder

    • MBath Lights New C (Ctrl/Rsp)

    • MBath Lights (Responder)

 

Here’s the odd thing I am seeing:

When I turn on/off button D on Keypad 1 (MBath Lights New), it should turn the fan scene on/off, but it also turns the LED for button B (towel warmer) on/off.  It doesn’t change the actual scene that turns the towel warmer load on/off – it just affects the LED on that button.

If I turn on/off button D on Keypad 2 (MBath Fan New), it should also turn the fan on/off, and it does, but it does not affect the LED for button B on Keypad 1.

As far as I can tell, I don’t have anything configured for an interaction between Keypad 1 buttons B and D, but the system does show some kind of interaction there.

BTW, I previously deleted these two keypads and associated scenes, and recreated them from scratch to go through the re-enrollment process for I3 devices on eisy (per the wiki).  Also, checking the device Configuration --> Show Device Links Table for both switches shows all links as “Identical” when I Compare them with what’s in the eisy.

I’m sure this is probably challenging to follow but let me know how I can best help if further info or logs would be helpful.   

17 hours ago, dwengrovitz said:

@Javi Sorry for the delay in responding, but I’ve done some more testing and am still seeing some unexpected behavior with the I3 keypads. 

Here's the basics ... I have two I3 4-Button keypads that work in tandem to control two loads and several scenes together.  Here is how the switches and associated scenes are set up:  

Keypad 1 (MBath Lights New) setup is:

  •  Button A (LOAD):

    • MBath Lights New (Ctrl/Rsp)

    • MBath Combo New (Responder)

    • Upstairs Lights (Responder)

  • Button B:  

    • MBath Towel Warmer (Ctrl/Rsp)

  • Button C:  

    • MBath Combo New (Ctrl/Rsp)

  • Button D: 

    • MBath Fan New (Ctrl/Rsp)

    • MBath Combo New (Responder)

Keypad 2 (MBath Fan New) setup is:

  • Button A

    • MBath Lights New (Ctrl/Rsp)

    • MBath Combo New (Responder)

    • Upstairs Lights (Responder)

  • Button B:  

    • MBath Towel Warmer (Ctrl/Rsp)

  • Button C:  

    • MBR Closet (Ctrl/Rsp)

    • Upstairs lights (Responder)

  • Button D (LOAD): 

    • MBath Fan New (Ctrl/Rsp)

    • MBath Combo New (Responder)

Scenes:

  • MBath Lights New

    • MBath Lights New (Controller)

    • MBath Fan New A (Ctrl/Rsp)

    • MBath Lights New A (Ctrl/Rsp)

  • MBath Fan New

    • MBath Fan New (Controller)

    • MBath Fan New D (Ctrl/Rsp)

    • MBath Lights New D (Ctrl/Rsp)

  • MBath Towel Warmer

    • MBath Fan New B (Ctrl/Rsp)

    • MBath Lights New B (Ctrl/Rsp)

    • MBath Towel Warmer (Controller)

    • Shelly 1 Mini (Responder)

  • MBath Combo New

    • MBath Combo New (Controller)

    • MBath Fan New A (Responder)

    • MBath Fan D (Responder)

    • MBath Lights New A Responder

    • MBath Lights New C (Ctrl/Rsp)

    • MBath Lights (Responder)

 

Here’s the odd thing I am seeing:

When I turn on/off button D on Keypad 1 (MBath Lights New), it should turn the fan scene on/off, but it also turns the LED for button B (towel warmer) on/off.  It doesn’t change the actual scene that turns the towel warmer load on/off – it just affects the LED on that button.

If I turn on/off button D on Keypad 2 (MBath Fan New), it should also turn the fan on/off, and it does, but it does not affect the LED for button B on Keypad 1.

As far as I can tell, I don’t have anything configured for an interaction between Keypad 1 buttons B and D, but the system does show some kind of interaction there.

BTW, I previously deleted these two keypads and associated scenes, and recreated them from scratch to go through the re-enrollment process for I3 devices on eisy (per the wiki).  Also, checking the device Configuration --> Show Device Links Table for both switches shows all links as “Identical” when I Compare them with what’s in the eisy.

I’m sure this is probably challenging to follow but let me know how I can best help if further info or logs would be helpful.   

Before attempting to debug any issues, if these were created prior to the lates update the scenes may have been created with the wrong mappings. Try write updates. I think this works but I only have 2 i3 Keypads, and pervious scenes were wiped during testing. So I am not 100% sure write updates works, it may required deleting and recreating the scene.

  • Author

@ dwengrovitz

Of course follow Javi's suggestion first.

What I was seeing was the programming of some buttons did not get written or didn't take by the switch. I ended up going through each button in the scenes and watched to see if the "Do not make changes..." message pops out when I make a change to the button (basically re-entering what showed to be already there). On some of my "problem buttons" (two or more leds lit at the same time), the message popped out. After that, the buttons behaved correctly.

Throughout this process, I also deleted scenes, deleted devices, air gap reset devices, and created new scenes. I still had to do repeat passes through the buttons in the scenes to get them to take. But I did get them working correctly.

On 11/7/2026 at 12:06 PM, nowandthen said:

@ dwengrovitz

Of course follow Javi's suggestion first.

What I was seeing was the programming of some buttons did not get written or didn't take by the switch. I ended up going through each button in the scenes and watched to see if the "Do not make changes..." message pops out when I make a change to the button (basically re-entering what showed to be already there). On some of my "problem buttons" (two or more leds lit at the same time), the message popped out. After that, the buttons behaved correctly.

Throughout this process, I also deleted scenes, deleted devices, air gap reset devices, and created new scenes. I still had to do repeat passes through the buttons in the scenes to get them to take. But I did get them working correctly.

Thanks @nowandthen. I followed that same procedure and, while it was a bit laborious, it did end up fixing the problem I was having with a keypad button LED turning on/off when it wasn't expected to. I think the only thing I added to your process was viewing the device links, comparing it to what was in the eisy, and doing a restore device if the comparison showed anything other than "Identical".

@Javi - I did find one odd thing in the UI when trying to configure responder settings in a scene. In some cases, the UI performed as though it didn't know what the settings were and, even after I updated them, it defaulted to something other than what had been previously set. I captured it in a short video to show what I experienced.

  • Author

Every time I set a responder setting, it always shows i_relay or i_dimmer even though I set it to Insteon earlier. It would be nice if it showed the settings that were last setup. To me, the key is if the "don't make changes.." pop out comes out on the lower right side, if it does it is updating. If it doesn't, I am guessing that it was already set to Insteon, 1 retry, etc.

Showing the current settings when you open the responder would be nice. It would make it a lot easier to see what it was previously set to, rather than having to set them again with the hope that it was previously not set correctly.

But it's not that big of a deal for me. Once I finally get the keypad working correctly, which is the real issue here, I'm unlikely to come back to it.

Edited by nowandthen


Thanks for the video.

On 11/9/2026 at 5:25 PM, dwengrovitz said:

Thanks @nowandthen. I followed that same procedure and, while it was a bit laborious, it did end up fixing the problem I was having with a keypad button LED turning on/off when it wasn't expected to. I think the only thing I added to your process was viewing the device links, comparing it to what was in the eisy, and doing a restore device if the comparison showed anything other than "Identical".

@Javi - I did find one odd thing in the UI when trying to configure responder settings in a scene. In some cases, the UI performed as though it didn't know what the settings were and, even after I updated them, it defaulted to something other than what had been previously set. I captured it in a short video to show what I experienced.

15 hours ago, nowandthen said:

Every time I set a responder setting, it always shows i_relay or i_dimmer even though I set it to Insteon earlier. It would be nice if it showed the settings that were last setup. To me, the key is if the "don't make changes.." pop out comes out on the lower right side, if it does it is updating. If it doesn't, I am guessing that it was already set to Insteon, 1 retry, etc.

Showing the current settings when you open the responder would be nice. It would make it a lot easier to see what it was previously set to, rather than having to set them again with the hope that it was previously not set correctly.

But it's not that big of a deal for me. Once I finally get the keypad working correctly, which is the real issue here, I'm unlikely to come back to it.

Submitted fix id: /eisy-ui/pull/158

Issue retries needs to be omitted (link def changed) for same device controller responder combos. Did not make it into the next release, so likely in subsequent.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.