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.

dwengrovitz

Members
  • Joined

  • Last visited

  1. 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. Responder Settings Capture.mp4
  2. Yes - the plugin requires configuration. There's additional info when you click on "More Info" on the Plugin About page in the Plugin store, including a working JSON example for integrating Claude. One thing that is a bit different for this plugin from several others is how the configuration parameters are setup. Best I can tell, the only parameter is "Configuration" and the full set of JSON with all of the additional config parameters gets put into the Values field next to that.
  3. @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.
  4. I will do some more testing (most likely tomorrow) and will let you know if I encounter any issues.
  5. Yes - my Insteon environment is almost exclusively I3 devices, and after going through the rather painful process to delete and reinstall every one of them (per the info on the Wiki), the I3 keypads were definitely not behaving as expected. I may have incorrectly pointed to 1.4.8 as the fix for the problem, as I just updated all of the eisy code hoping to get some fixes for I3 devices even if they were still in the process of being developed.
  6. I have a bunch of I3 devices, including several I3 keypads, so I've been following this thread closely. I was having some odd behavior with two keypads not working quite as expected, so I tried the code from the staging repo (yeah - I know - the message says don't use that unless requested by UDI support). In any event, 1.4.8 does seem to make a difference for me with the buttons now controlling various loads/scenes and button LEDs turning on/off as expected.
  7. If I've migrated plugins from PG3 to eisy-ui, do I need to keep the ones that show as migrated on the PG3 Dashboard? Or can I just delete those?
  8. dwengrovitz replied to DNewkirk's topic in eisy
    @DNewkirk I don't have a direct answer to your question about how well the I3 devices are supported under AC, so feel free to shame me for providing a suggestion, but I do have a good number of I3 switches on an eisy running beta code. From what I've seen, the I3 devices seem to be much better supported in the browser versus the old AC, so much so that I've stopped using the AC altogether. Given the AC is going away, and you also have at least one I3 device, I might suggest considering your migration to eisy-UI sooner than later. It takes a little getting used to, but it's pretty functional now and the I3 devices seem to be well supported there, especially with recent updates specific to the I3 (as shown in the release notes - see screencap below). Also - see https://wiki.universal-devices.com/Insteon_-_i3 for more details specific to the I3 devices.
  9. Yes - I've rebooted multiple times. The problem still exists for me on eisy-ui beta 1.4.2. The system looks like it's busy doing something, but no data ever gets displayed. See screenshot below ... eventually, the orange box goes away and the white remains, with no link data displayed.
  10. dwengrovitz replied to GHenry's topic in eisy
    Perhaps that's coming in a near release? I'm using the latest beta eisy-ui (1.4.2), and there is a Configuration Option under the System Settings that allows specification of location and display of time.
  11. @IndyMike Thanks. I opened the event viewer in the AC and it does see the links via in the Admin Console, but the new eisy-ui doesn't appear to show them.
  12. I tried Show PLM Links Table on eisy-ui (beta 1.3.11_1), but all I see is this ... should it be displaying actual data or are my links really hosed?
  13. I'm running the latest eisy-ui from the beta repo. When we previously updated the device code via the Admin console, it almost always required a reboot. However, when updating the code via eisy-ui, it generally says the update is done (but doesn't say anything about reboot). Can someone clarify what to expect re: code updates and reboots when using the new eisy-ui? Should I reboot or not after an update, or will the UI always tell me when a reboot is needed? Also - if one elects to manually reboot - the status message displayed is yellow on a white background (when in light mode) and is pretty much impossible to read (as shown below).
  14. I'm seeing this same issue on my system. I haven't made any changes in PG3x, and I've restarted the eisy and Admin Console multiple times. I don't think this has anything to do with restarting after making changes.
  15. Yes ... this was absolutely the case. I ended up removing the Genie skill from Alexa to help minimize any confusion. We'll have to do more testing to see how that goes over time.

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.