firstone

I will try to update my polisy to 5.9.1 and see if I can reproduce. But you can also put node server into Debug mode, restart and PM log package to me. Maybe something simple.

I don’t think ISY994 implemented security. I do not recall having to enter any codes. I’ve have older and zwave plus working with 994 but then had issues with polisy. But HA with modern usb stick will definitely have security.

The issue I've had was with ZP lock and newer firmware, FYI. Here's what you can do to troubleshoot it, if you're so set up. If you have another z-wave controller and have HA set up, you can try to enroll the lock into HA and see if it works correctly. From there you can generate the log files for enrollment and UDI maybe can see the difference. Some of these devices do not follow standard to a tee and sometimes half implement protocols. Which is why my "older" firmware was fine but newer wouldn't work. Schlage support was of zero help.

When you see this, you should usually see the notice on dashboard saying "Please press the button on the Hue Bridge(s) and restart the node server within 30 seconds". If you're not getting a notice there would be something wrong on pg3 side. But either way, try to do it.

Default timings are 500, 500, 50. Long poll and short poll are not used. To troubleshoot reliability, put plug in into Debug mode, do 5 quick presses, then 5 press and hold. Send log package to me, I will take a look.

I've tried installing it now again - it finished installation properly but gave some UDX error. Will try to work it out with UDI. Once installed, I was able to start it with no issues. Seems fine.

Unfortunately, I can only support devices I have or used to have. If it's something very simple like Denon or Onkyo, where you have a very limited set of commands with no authentication, I could do it. But Samsung TV is likely to have overly complex (and completely unneeded) protocol.

Set "Release threshold" to 50. I will release a new version with lower default value. Seems it's causing more problems than it solves.

I will take a look. I haven't changed anything for quite some time so possibly some new change in pg3 is causing it.

If IR signal is good, when everything works, it will work 100% of the time. Try one thing: go to settings and change "Release threshold" to 50. Restart and try. If that doesn't work, reach out to me in PM and we will get it working.

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.

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.

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.

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.

@Bug994PM me and we can troubleshoot it. I don't think it's working correctly for you.

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.

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.

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?

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.

Try to log out and login again?

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. 😳

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

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.

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.

Try 3.2.18. The notes specifically mention fixing authentication button.