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.

oberkc

Members
  • Joined

  • Last visited

  1. Well, not totally useless. I observed that there seemed to be a relationship between the device type and X-10 code. It appears that the 02 represents house code B. 01 represents house code A, 03 represents house code C, etc... I am one of those. It does
  2. I tried following these instructions as well, and also found the third step elusive. Having said this, the suggestion above from @Guy Lavoie seems to work for me. In different words... from the menu, go to protocols>>Insteon>>add new Insteon device. Give it a name, and X10 control in the address field (such as A1). Leave the third "auto discover" field as is. Choose "OK". If your experience is like mine, you will get an orange banner advising you that it is saving the device. After the popup menu asking whether you want to rename the device or not, it shows up under nodes as an unknown device with an address something like ff XX XX 1. The address format matches some of my old X10 devices created many years ago using the x10 module option and admin console. (see attached image where the last device is my newly-added x10 and all others before it were carry-overs from the admin console). Reminder: the original ability to create an X-10 node and name it was only an option if one purchased the X10 module and added it to the ISY and the admin panel. Otherwise, the only way to transmit an x10 command was via a program. The ability to transmit x10 codes appears to currently remain available in the EISY-UI in programs as well. While I have not tested this (currently don't use X-10), it appears to me that X10 capability still exists fully in the current EISY-UI world.
  3. It may depend on how the keypadlinc is set up. Did you use mutual-exclusive relationships built into the keypad? If so, then I suspect that the backlights will be correct only at the device. I would have responded the same as Javi...I don't believe that remotely controlling a device (whether from the admin console or mobilinc or udmobile) would ever trigger a scene response. As far as I remember back, Insteon devices only act as scene controllers when physically toggled locally. As Javi pointed out, the potential workaround would be to control the scene, but use the individual device as a status indicator.
  4. Yes, you need the Yolink hub. Additionally, you would need the Yolink plugin for PG3 (or the EISY-plugin). I don't remember the details, but I recall that it took a few steps to get working. I don't recall any surprises. I started with the original "hub", then migrated to the "local hub". If I recall correctly, the local hub required a different plugin as well. Both worked reliably and the local hub continues to do so. Your choice of hub, as far as I can tell, depends entirely on how important is it to you that your system can operate without an active internet connection. I use motion sensors, moisture sensors, and a power strip. It is among the plugins that I consider rock solid.
  5. oberkc replied to oberkc's topic in eisy
    It makes me wonder about the purpose of the "delete" option and whether the new EISY-plugin is actually working.
  6. oberkc replied to oberkc's topic in eisy
    Sorry to hear this. So that you know, I have again migrated (some of my) plugins to "plugin", but have not yet deleted them from PG3. After a few hours, everything is still working. I will keep you informed.
  7. oberkc posted a topic in eisy
    A few days ago, I migrated most of my plugins from "legacy" PG3 to the EISY Plugins. Most worked well with a couple requiring extra steps to get working. Since they were now working in the new EISY plugin, I chose to delete from PG3. Soon thereafter, all of the nodes associated with the various plugins were gone. Ultimately, I was able to restore a recent backup and the PG3 was repopulated with the configuration prior to migration, and all the programs and scenes containing the plugin nodes were restored. Has anyone else experienced this problem? Was this problem associated with my decision to delete the migrated plugins from PG3? Has anyone else deleted migrated plugins from PG3? Other thoughts?
  8. I believe that is done by creating" an empty" widget and then using that empty widget to create the spaces you desire.
  9. oberkc replied to SHM's topic in YoLink
    I will add that mine local plugin quit working when I migrated to the EISY "Plugin" from PG3. I migrated back to PG3 and it is remains non-functional, with all node and controller fields blank. I have restarted the PG3 node server and rebooted the EISY. Still no luck. Update: I rebooted the PG3 node server again and it seems to be back online.
  10. Yes. I am confused, then. The registration page shows 10 - 11am (presumed and confirmed PST). The Email response shows 10 - 11 EST.
  11. I have had similar experience with the single thread device with which I am experimenting. I also have similar experience with matter-over-wifi devices. I have never satisfied myself that I know the root cause. For now, I am not adding any more matter devices.
  12. I assume all posted times, including at the registration page, are PST
  13. I have not experienced this problem. My plugins always restart and work fine after power outages or other unexpected reboots. A while ago, I recall a few plugins that may not have worked after a power outage, but I percieved this was the result of a plugin restarting faster than the associated hub (hue plugin restarted faster than did the hue hub, for example). I have not noticed such problems recently, however.
  14. Are your ue devices integrated via the hue hub? If so, I thought one could create a group in the hue app, which would show up as its own single node in the EISY. I am wondering aloud if this single node could be controlled as you wish.
  15. Twice a year this topic arises. Give it an extra day and (if your experience matches mine) it will fix itself.

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.