MWareman

Just know that only on or off is supported. Direct Dim commands are not supported by Insteon scenes (and therefore cannot be called via Google Home or Alexa for that matter)

I have a dpdt relay connected to my Doorbell with a 24vac coil powered by the doorbell transformer. One pole connects to the chime, the other to my Elk (on a non-alarm input). This could easily be an iolinc. This triggers an ISY program that calls a network resource. The URL is on a Rpi and it runs a .php script. That PHP scrips grabs an image from a Foscam I have looking out of my sidelight - and calls the Pushover API to send my phone the image. It works fairly well overall.

If the ‘Room’ assigned to a device in the ISY Portal matches a ‘Room’ available in Google Home - then you won’t have to do this. It will happen automagically for each device. If the room name does not have a match, it will be unassigned in Google Home and you will have to manually assign it. At least it did the last few times I relinked.

FYI - Mobilinc Connect requires a license fee as well. Both it and UDIs Portal are subscription based. Like UDI - it’s to offset the cost of running the cloud resources necessary for the integration to Google Home and Alexa work. You can avoid fees by using free services (like ifttt) but I know that can be significant processing delays thru services like that. It’s also much more effort to setup. In my opinion, the cost of admission is well worth it.

I haven’t. Mobile, I use Agave which uses a websocket subscription - and this can be proxied. Otherwise, I use ISY Portal - and when remote I connect the Admin Console via that. Michael.

All tests matched your steps - so if this confirms 1.1.3 then I'm good. Hopefully the PGC version display bug can be fixed soon. Michael.

Just to be clear, the images are taken from the git repository. How can I check the actual version installed as it reports in the UI as 1.1.0? Michael.

Interesting - package.json lists version 1.1.3: https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/package.json server.json (https://github.com/UniversalDevicesInc/ring-nodeserver/blob/master/server.json) contains version 1.,1.3 and profile_version 1.1.0: Is this just a display bug in PGC? Michael.

On start: logBucket: 'pgc-prod-logbucket-[REDACTED_DATA]', url: 'https://github.com/UniversalDevicesInc/ring-nodeserver.git', isyPassword: '[REDACTED_DATA]', development: false, language: 'node', userId: '[REDACTED_DATA]', 'https://[REDACTED_DATA].execute-api.us-east-1.amazonaws.com/prod/api/sys/nsgetioturl?params=[REDACTED_DATA]', timeAdded: 1561760405240, oauth: '<oAuth config>', isyVersion: '5.0.15', longPoll: 120, name: 'Ring', pgUrl: shortPoll: 60, timeStarted: 0, version: '1.1.0', id: '00:21:b9:00:f0:9c', netInfo: nodes: '<nodes>', publicIp: '3.89.244.35' }, { publicPort: 30492, { oauth: customData: httpsIngress: 'https://pgc-ns-ingress.isy.io/ns/[REDACTED_DATA]/', '[REDACTED_DATA]', created_at: 1579398192, { access_token: token_type: 'Bearer', '[REDACTED_DATA]', refresh_token: This was after receiving the code from Git. Clearly - it's identifying as version 1.1.0. And: After restarting it and it came back up - still 1.1.0: Michael.

You are still applying the spoken to a scene - and scenes still cannot be set to anything other than ‘On’ or ‘Off’. Remove the spoken from the scene and apply it to the light itself. Then write a program to trigger of the status of the light and turn the kpl button on if the light is >0 or off otherwise.

I'm seeing the same thing. The usual stop/start does not bring in the new version. @bmercier ?

@Michel Kohanim has found and fixed the issue I was having with udx - and my beeping has stopped and I can now access Polisy's settings screen. In my case - I had a purchased SSL certificate - it's private key is 4096 bits. The udx binary was not expecting that - causing it to throw an error on start. 4096 bit keys are now being properly accommodated. This is resolved in udx version v1.0.26_8. Thank you! Michael.

Personally - I spent the time (years ago) leaning the clunkiness of VI - simply because it's universally available. This has never let me down. Honestly - it's worthwhile at least learning the basics... https://developer.ibm.com/tutorials/l-lpic1-103-8/

Thanks! Via ticket, Michel has found a parsing error in UDX that looks to be the likely cause of my issue. Hopefully, it’s the cause of others issues as well... and an update takes care of it.

Before the ISY Portal existed, I used an Apache server and the proxy module to allow token based authentication to the REST API without having to reveal the admin password to third parties. I wrote it up here: https://wiki.universal-devices.com/index.php?title=Apache_Reverse_Proxy The ISY Portal is now better alternative. Certainly, less complex to get going...

You are correct. The Java based admin console uses the SOAP interface - and UDI is reimplementing everything with REST so that a native HTML5 admin UI will become possible - and the need for Java will (finally) die. I thing that this is one of the functions still only available over SOAP - but I’ve been wrong on this before as REST endpoints are being added with every release - and not all appear to be well documented yet.

I believe this is achieved via the SOAP API rather than REST....

@larryllix Did you import a custom SSL cert into Polyglot? I did - and just wanted to see if this was common between us.. Thanks! Michael.

Thank you! I just responded. Since the top suspect appears to be the MongoDB - is there a way to definitively determine this? We tried 'deleting' it and letting it recreate - but the issue was still there. Also - there appear to be no operational issues with Polyglot (other than the Polisy settings daemon not working). Wouldn't MongoDB corruption affect Polyglot in other ways? Michael.

@larryllix - Is your Polisy beeping every few seconds as well? If so - your symptoms exactly match mine...

Sent! Thanks..

Michel, Thanks for the suggestions. I do have a bigger network than /24 - so although there is no indication of any failure to connect to ISY I added that line to the .env. It did not change the status (even after rebooting Polisy). So, onto the MongoDB possibility. The status command showed MondoD was running. So - I stopped it and then renamed the old data folder. After rebooting Polisy the issue returned. I had to put back the original MongoDB directory because all the nodeservers went to an ‘Unmanaged’ State - but the fact there is no apparent behavioral difference between a virgin database and my original one suggests no corruption. The UDX binary still cannot make a secure connection to MQTT and the Polisy is still beeping. Michael.

Sorry for the delayed response. Sporadic internet access for a few days... Polyglot is 2.2.8. Also, Just now, I couldn’t logon to the web UI (the logon button did nothing) and I had to reboot Polisy to be able to logon. Michael.

Sorry - just saw this. The schedules were time based. Things like '1 hour before sunrise' would stop working - and I'd have to reboot ISY. This was on 5.0.16 (not A or B). I just ungraded all 3 to 5.0.16B and I'll report if I see the same thing or not.

The firmware 10.0.16B is reporting inconsistent version numbers. On my.isy.io - it reports 5.0.16 (ALL 3 are 5.0.16B): ISY Finder (via start.jnlp) reports 5.0.16B for all 3: And if I retrieve http://isy.domain.com/admin.jnlp and use that - the 5.0.16 admin console is run (this is with a fully cleared Java cache): ISY Finder cannot launch the admin console (this is under Iced Tea on Ubuntu): https://isy.universal-devices.com/994i/5.0.16B/insteon.jar https://isy.universal-devices.com/994i/5.0.16B/ce.jar https://isy.universal-devices.com/994i/5.0.16B/chart.jar https://isy.universal-devices.com/994i/5.0.16B/fp.jar https://isy.universal-devices.com/994i/5.0.16B/RXTX.jar java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.universaldevices.isyfinder.ISYUILoader.launch(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.launch(Unknown Source) at com.universaldevices.isyfinder.ISYFinder.access$7(Unknown Source) at com.universaldevices.isyfinder.ISYFinder$8.actionPerformed(Unknown Source) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) at java.desktop/javax.swing.AbstractButton.doClick(AbstractButton.java:369) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) at java.desktop/javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632) at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342) at java.desktop/java.awt.Component.processEvent(Component.java:6397) at java.desktop/java.awt.Container.processEvent(Container.java:2263) at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307) at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772) at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745) at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) Caused by: java.lang.IllegalAccessError: failed to access class com.universaldevices.ui.UPnPClientApplet$27 from class com.universaldevices.ui.UPnPClientApplet (com.universaldevices.ui.UPnPClientApplet$27 is in unnamed module of loader net.sourceforge.jnlp.runtime.JNLPClassLoader @31687759; com.universaldevices.ui.UPnPClientApplet is in unnamed module of loader java.net.URLClassLoader @73a7280) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) at com.universaldevices.ui.UPnPClientApplet.main(Unknown Source) at com.universaldevices.client.ui.UDClientApplet.main(Unknown Source) ... 45 more If I download https://isy.universal-devices.com/994i/5.0.16B/admin.jnlp locally - and run that I get a the old ISY Finder that does not populate (expected). I hit 'add' and type http://isy3.domain.com and the USL and UUID populate: Double-clicking this launches the admin console - and I (finally) get the 5.0.16B admin UI: Main 3 questions. 1) Is start.jnlp launching for others (I assume so - and this is likely an Iced Tea / Ubuntu issue)... 2) If you clear your java cache - and launch the admin UI from http://isy.ip/admin.jnlp (replace isy.ip with your ISY IP address) - does it launch the correct version of the admin UI? 3) Does the 5.0.16B firmware contain the wrong admin.jnlp (5.0.16) on it's image? Personally - I *always* pull the admin.jnlp from the ISY itself to avoid the cloud dependency - and this is the very first time I'm getting a different version of the admin UI from /admin.jnlp than is running on the ISY itself... Michael.