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.

nowandthen

Members
  • Joined

  • Last visited

  1. At first I thought this was just an i3 issue. When programming a button, it always defaults to i_relay (sometimes i_dimmer) to which I have to change it to Insteon and continue programming the button. But... I'm creating a group (scene), it has 3 "regular" Insteon 8 button KPLs. Number of KPLs is irrelevant (I think). Most of the time when I program a button it offers Insteon and On/Off and number of retries is already set to 1. Fine. Easy programming. But... same KPL, same group, just moving down the list of button settings, and seemingly randomly when I program the button it offers i_relay, to which I have to change to Insteon in order to turn it off, then I have to set number of retires. What the heck is i_relay? I have no use for it, but I will assume others want it. For a "regular" Insteon KPL 2334-2 (and probably others) why am I getting "i_relay"? Does anyone want i_relay? Beuhler? I don't. My .02.
  2. 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.
  3. @ 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.
  4. 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.
  5. Summary: I am using the staging repo 6.1.2_14. i3 buttons seem to be fixed. The issue I believe is when changing a button in a group (scene), for example to be off, the eisy shows off but the device doesn't always get programmed. Watch for the side pop-outs saying system is busy. If it doesn't show the side pop-out then it didn't get programmed into the switch (my belief at time of this writing). Several rounds through each member of the group eventually got the switch programmed and the switch is working like I wanted. And by the way, I did not put button 1 in the group, just buttons A, B, C, D. But all buttons are in the eisy nodes list.
  6. Removed the contents. See next post.
  7. For the sake of others (and me) , you loaded the staging repo? Only the IoX under staging repo specifically says it fixed i3 keypad issues. 1.4.8 doesn't by itself address the i3 issue, meaning if you load 1.4.8 under production repo it does nothing to fix the i3 issues.
  8. For the sake of others (and me) , you loaded the staging repo? Only the IoX under staging repo specifically says it fixed i3 keypad issues. 1.4.8 doesn't by itself address the i3 issue, meaning if you load 1.4.8 under production repo it does nothing to fix the i3 issues.
  9. Collapse ALL and Expand All buttons added to eisy-ui 1.4.8. Thanks UDI!
  10. Are you saying I should try the Staging repo? That's the only package that shows "fixed i3 button issues". I guess I'm under the impression 1.4.8 ui fixed it. Sorry, I'm not a programmer so understanding all this is a learning experience for me.
  11. Yes. I rebooted, logged out and in. deleted the device, air gapped it, no luck Firefox seems to have some problems, in Chrome the red exclamation point goes away. So better there. However, for the life of me, I cannot get the buttons to respond as exclusive,, meaning only one button on at a time. Under some buttons, there is no Off or On option, only Link Type: Command, Default, Ignore and Command: Query, backlight, write changes. I used to be able to select each button, one at a time and set all others to off. I can this for buttons B, C, and D but not 1 or A. Initially they show "On" but once you select Query or backlight, or write changes, it accepts the setting but you can't go back, and those settings are not what I need. I need On and Off. Can we go back to the older version for this device? That one worked really well. I'm afraid to make any changes to the i3 keypads already in use for fear of breaking them. :(
  12. I updated to eisy-ui version 1.4.8. Was 1.4.6 Production repo. Get this error message when i click on any button of the 4-button i3 keypad. The keypad has a red exclamation point. Says query and/or power cycle. Did both. No love. Air gap reset. removed added, rebooted eisy. Nothing helps. :(
  13. Almost always, setting a number of seconds or minutes to 'Wait" does not update in the program. It simply shows "Wait" in the program. I keep trying, sometimes it will save, often not. Same with Schedules. For example, setting a time before or after sunset does not save. It will save as Sunset or Sunrise but offsets will not save in the program. I rebooted the eisy but problem persists. Edit: I use Firefox. If I open in Chrome they seem to save okay. So Firefox issue? I don't like using Google.
  14. Javi, As I am sure you know, production repo has not changed. Are you saying I should try Beta Repo (only eisy-ui updated) or even staging repo (more updates)? It says staging repo not to be used unless instructed by UDI. Edit: If I do try one of the others, can a user roll back to Production if something isn't working right?
  15. Working on Sunday!!! Unexpected dedication! Thanks!

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.