firstone

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.

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.

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.

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.

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.

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.

This is PG3 log. I need a lot for AVServer itself. You can generate log package. PM that to me, please.

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.

https://github.com/firstone/av-remote-poly#lg-tv-web-os-devices if TV doesn't prompt to accept connection it will not work.

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.

Check log files in /var/log. You should be able to grep on DHCPOFFER I think.

I would check polisy and dhcp server logs and see what's being offered and assigned. I don't believe polisy does any kind of special ip address caching, nor it would be proper behavior. Unless it's somehow misconfigured to static maybe.

Probably should be done by your dhcp server - there should be a way to give static dhcp lease for a particular mac.

If it's universal remote, then it's not a function of a remote but rather specific code set you're using. Changing to different code set should fix things. If you're comfortable ssh-ing into eisy and running python script, you will be ok.

Number one thing to try is to use another simpler remote - like TV remote, and see if this clear things up. Some code sets do not send key press finish events and it breaks things. On PC it reacts but doesn't necessarily send all correct signals. Next step, if you're comfortable doing it, I can give you a test program in python that you can run on a pc or eisy. That will show exact signals your remote is sending.

Holidays either come from python lib, which has a lot defined. https://pypi.org/project/holidays/. Or you can set up your own by date. With that in mind, above use case is not something this was written for. It's more like day based. Something like if Today is a holiday, do not lower thermostat. Or if tomorrow is a holiday, keep outside lights longer. The more important part is its dynamic. You can turn it on of off. For example, you can set up WFH for Mon and Fri. But I can say "Alexa, turn tomorrow on" and tomorrow will become WFH, running all WFH schedules. Something like that. For above use case I'd just use regular schedule as others have said.

Latest code is here https://github.com/firstone/av-remote-poly/tree/dev/esp8266/RESTRemote

Updated it to version 6 but cannot test and do not guarantee that it works. Only that it compiles.

I've just downloaded IDE version 2.2.1, selected Generic ESP8266 module, loaded .ino and it compiled. Not sure why it's not working for you. I have ArduinoJson 5.13.1 installed.

I don't think it's being widely used, if at all. To be honest, I haven't touched it for a while. I will try to get it recompiled when I get a chance but can't promise any timeline. If you figure out required changes, PM them to me, please. Otherwise, I'll update when I can.