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.

firstone

Members
  • Joined

  • Last visited

Everything posted by firstone

  1. PM me and we will get it working. Seems like your remote is not triggering Flirc keypresses. Otherwise, you would see nodes under main controller. If your remote does not use "original ISY994 codeset", you need to teach its commands to Flirc. We can test it on any computer.
  2. If you install HA elk integration, it will work directly with ELK. No need for pg3 plug in. Most likely HA isy integration does not have full support for such a complicated device but you can try to ask the author in HA forum.
  3. Yes I’ve used it in a polisy via USB from the start. It allowed me to put it near basement ceiling and get a better reception.
  4. I don't think anything out there does better Insteon integration. So unless you're willing to throw away your 50 Insteon devices, probably don't overreact and use UD's best feature - support. Open a ticket, give them time to work it out. Firmware instability is unfortunate, and, hopefully UD can address this in the future by not doing auto updates and/or controlling it better. But as a developer I can tell you this, no matter what your best effort is - the only way to avoid bugs is not to make any changes. This might have worked well with original ISY, but with constantly moving pgx and zwave, etc work, this, unfortunately, is not the case.
  5. @Bug994PM me and we can troubleshoot it. I don't think it's working correctly for you.
  6. Issue he was having manifests in missing key presses. If you look at keys in AC and don't see them register remote presses. If you see reliable Pressed/Held, this is not the same issue.
  7. Control should work. I know I've tested that in the past. Possibly need to increase threshold a bit in order for program to catch it. You can play around with it, if you want. If you can't get it working, let me know. I'll try it when I get a chance.
  8. firstone replied to loougood's topic in eisy
    eisy is basically a pc with full operating system, usb, etc. It's not suited for connecting sensors. It doesn't have analog (or digital inputs). What you need is something like Arduino. And even then - sensor will only provide voltage. You'd need to correlate voltage to actual level. For instance xxx millivolts to yyy PH level. Even then, some measures are temperature dependent. So unless you know how to translate that, seems like too much work. You're better off betting a controller from aliexpress that already does it and connects via wifi. And if you could do it, would you mount eisy in a box by your pool?
  9. As per above: 1. add https://my.isy.io/api/cloudlink/redirect to Authorized URLs. 2. Use generated client ID and client secret in plug in configuration. If it's not working, PM me, I can give you a python script to maybe do a bit of troubleshooting.
  10. Try to log out and login again?
  11. I've had to hunt down JRE 8 and it works now. Not sure why newer JDKs 22 do not work with javaws. Last time I've programmed in Java, 7 was just coming out. 😳
  12. Not sure if it's related to Apple silicone or Sonoma. Seems like javaws just doesn't work. I've installed OpenWebStart and it seems to start Finder and shows my units but crashes opening A/C. ... 43 more at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) at com.universaldevices.client.ui.UDClientApplet.main(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) Caused by: java.lang.IllegalAccessError: failed to access class com.universaldevices.ui.UPnPClientApplet$29 from class com.universaldevices.ui.UPnPClientApplet (com.universaldevices.ui.UPnPClientApplet$29 is in unnamed module of loader net.sourceforge.jnlp.runtime.classloader.JNLPClassLoader @64685525; com.universaldevices.ui.UPnPClientApplet is in unnamed module of loader java.net.URLClassLoader @3dd4cb54) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:744) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87) at java.base/java.security.AccessController.doPrivileged(AccessController.java:400) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:747) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:98) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87) at java.base/java.security.AccessController.doPrivileged(AccessController.java:400) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:714) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:720) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:775) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4828) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2780) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2310) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4516) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4575) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4948) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4828) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2324) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:4996) at java.desktop/java.awt.Container.processEvent(Container.java:2266) at java.desktop/java.awt.Component.processEvent(Component.java:6386) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3398) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6621) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1073) at java.desktop/com.apple.laf.AquaMenuItemUI.doClick(AquaMenuItemUI.java:157) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1029) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:374) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:407) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2314) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1972) at com.universaldevices.isyfinder.ISYFinder$9.actionPerformed(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.access$7(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.launch(Unknown Source) at com.universaldevices.isyfinder.ISYUILoader.launch(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Method.java:580) at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:118) java.lang.reflect.InvocationTargetException
  13. Google will no longer authenticate logins because I've reached unverified maximum. And verifying it is not an easy process. As a workaround, I'd updated to version 3.0.1 (which is in Beta store for now). You will need to create your own set of API credentials and set client ID and client secret in settings. Also have to add https://my.isy.io/api/cloudlink/redirect to Authorized URLs.
  14. I would advise to remove plug in completely and try again. I've just done clean install, clicked "Authenticate", it took me to google page, I've clicked Accept, it worked and pulled my calendars. If that doesn't work, maybe close browser and/or clean google API cache/cookies. Seems to be something is happening on your side. Maybe something related to your generating access tokens. Not really sure. PG3 probably logs authentication. Not plug in but PG3 itself. You might need to put it into debug mode. Also, maybe some setting on your google account that specifically disables authenticating with calendar? I have a simple test python script you can run on your computer. PM me if you want to try that.
  15. Try 3.2.18. The notes specifically mention fixing authentication button.
  16. Which version of pg3x are you using? I think there have been some recent changes to authentication and it might have affected it. I will need to take a look. Normally, you just click and button and it will take you directly to google login page. No other steps are necessary.
  17. I'm using GLEDOPTO Zigbee3.0 RGBCCT. I have it paired with Hue hub via hue node server but you can probably connect some other way. Hue also sells LED strips on its own but pretty expensive.
  18. Newer ones will not work - they don't use webos or same protocols. If I ever buy a new one, I'll try to add it but hard to do it blind.
  19. When you migrate, you switch from 300 or 500 series, which doesn't use security communications to likely newer z-wave that uses S0 (I think). I'd remove it and add it again - you will need to enter DSK code to finish pairing. You might not need to move it near eisy as newer z-wave modules have much better range.
  20. Test program is separate from node server. We can use it to rule out remote code set issues, communication issues, etc. Basically if test program will work, node server will also work. So if you still want to give it a shot, PM me.
  21. This is PG3 log. I need a lot for AVServer itself. You can generate log package. PM that to me, please.
  22. Are you capable to ssh-ing into eisy and running commands? I can PM you test program. You're a second person having this issue - the only thing I'm thinking about is that Flirc changed firmware or hardware somehow and it doesn't function as expected.
  23. https://github.com/firstone/av-remote-poly#lg-tv-web-os-devices if TV doesn't prompt to accept connection it will not work.
  24. Before you start playing around with code sets, I'd still recommend trying some tv remote - just to see if it fixes things. Also, maybe try rebooting eisy just in case. If you haven't rebooted since you've installed, it could be permissions issue that would also cause lost signals.
  25. Check log files in /var/log. You should be able to grep on DHCPOFFER I think.

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.