MWareman

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

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.

My 5.1.16 keeps missing scheduled events - and I rely on leak sensors... Do we know if 5.0.16B is likely still this week? Michael.

I have 5.0.16 currently - and twice over the last week I’ve had to restart ISY because time based programs stopped triggering (time offset from sunset). However, I have Flood sensors likely affected by the bug. So, I’m awaiting 5.0.16B before upgrading to the latest.

Hit the ‘Send Spokens’ button..

I run Asterisk on a Pi(3). Other than rebooting for kernel updates occasionally it’s been 100% reliable - without underclocking. In total, I have several Pi’s running well (things like Nodelink, the Unifi controller, dedicated DNS servers, ElasticSearch dedicated master node etc). Sounds like either the power supply is not reliable - or you are using a poor quality SD card. Don’t cheap out of these and the Raspberry Pi will be very reliable.

If you have a room named in ISY Portal (assigned to devices) and a room of the same name in Google Home - the devices will be put into the room automatically. The room itself will not be created (to my knowledge). So, create empty rooms in Google Home then try the sync all devices.

Are you absolutely sure your initial variable assignment does not contain the ‘F’? If it does, it likely won’t work. With network and email substitutions this is common and UDI now allow to append .RAW (to get the number without any extra characters). Not sure how to do this inline though - but you could create a network rule to set the variable.

True. But you cannot change the color. If you have a need/desire to be able to adjust the color of the light you pretty much have to go the smart bulb route.

Without seeing your Tasker profiles it’s difficult to decode what you are meaning. I’ve never sent email to Tasker - so I don’t really know what profile elements you are using to have Tasker react to email. Are you able to post some examples so I can see what is meant? Behind the scenes - network rules will be faster than email - because network rules are a tcp socket made real time - and email is store and forward. Sometimes, the difference may be negligible. Other times, noticeable. It depends on many things outside of the scope of this forum.

Pushover posted a write up on the issue... https://blog.pushover.net/posts/2019/10/october-24-25-ddos-attack

Personally, I prefer notifications. They are ephemeral and don’t clutter up an email inbox. Notifications are generally faster to arrive as well and don’t rely on the email client having to poll a mailbox.

That's interesting. Thanks for pointing that out. I think something may have changed in the ISY (since that wiki was written back in 2014). GET is correct for sending to AutoRemote. I'll update the Wiki page accordingly to match current reality. Edit: Wiki edited. Thanks for the report. I added additional clarification about variable substitution and interaction with 'Encode URL' as well since when that page was originally written that was not possible.

By Pushover URL - I mean the NR pointing to Pushovers API: https://pushover.net/api#messages Pushover has a library of sounds baked in. https://pushover.net/api#sounds As long as one of the sounds fits - then Pushover will be better. If you want full control over the sounds played - then you will need to use Tasker/Autoremote.

If using the Pushover URL - then Pushover is playing the message and popping up the notification. No Tasker or autoremote needed. If using the Tasker / Autoremote method - the you need to write a Tasker profile that triggers on the incoming AR message and runs a task that plays your notification (and pops up your message).

If you want to try having Pushover natively notify you (instead of needing Tasker to intercept) - the try setting the priority to >0, and the sound to something. token={token}&user={user}&priority=1&sound=falling&message={message} 1 causes Pushover to make a high priority notification, and 2 causes the message to repeat the notification until it's acknowledged. This can only be done from a NR AFAIK. Tasker intercepting incoming will require a different triggering profile that what you used for email. I've never configured Tasker to trigger from incoming Pushover pushes (it just seems redundant). For using NRs to send data to Tasker - this is the wiki I refer to: https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification:Tasker

I use Autoremote (a Tasker plugin) and use NRs to send messages to it. Tasker then acts on incoming messages to Autoremote without issue. I put this recipe on the wiki as well. Is that what you are doing? A better alternative may be to send the Pushover message with a parameter to play a sound. That way it’s not dependent on Tasker.

In my case - I had Darksky, Push and Ring in PGC (slots 2,3,6 respectively). These all show in my Polisy in the same slots (as unmanaged). Like you - expected. I also have ISYLink in slot 25. That also shows correctly in Polisy. I do have WeatherflowPGC in slot 2 on PGC. However - on Policy slot 2 shows "Solaredge" as unmanaged. That's new (I don't have a SolarEdge). There does not appear to be any way to get rid of it as Polisy is not the master for the poly. I just tried adding WeatherflowPoly again - same error 128 from the 'git clone'. I tried the MQTT poly just in case - same. Error 128.

‘Unmanaged’ are when Polyglot detects ISY slots have a Poly in them, but it’s not managed by this instance. This could be another Polyglot install - or PolyglotCloud. In my case, I had the expected unmanaged polys from PolyglotCloud. That being said, I also gained the SolarEdge poly. No idea where that one came from.

Hmm... cannot seem to add any nodeservers. When I try to add one - nothing shows up in /var/polyglot/nodeservers Permissions of the folder look right. But the clone of the repo did not work: 2019-10-26 12:00:05 - error: NSChild: WeatherFlowPoly cloneRepo: Non-zero exit code: 128 2019-10-26 12:00:05 - error: NSResponse: Success: false - cloneRepo: Non-zero exit code: 128 2019-10-26 12:01:53 - error: NS: Error getting server.json required fields. name and executable are required. - Error: ENOENT: no such file or directory, open '/var/polyglot/nodeservers/WeatherFlowPoly/server.json' Another one: 2019-10-26 12:06:07 - error: NSChild: WirelessTag cloneRepo: Non-zero exit code: 128 2019-10-26 12:06:07 - error: NSResponse: Success: false - cloneRepo: Non-zero exit code: 128

NRs are faster because they are essentially real-time. Email uses store-and-forward queuing. Additionally - Pushover (and others) popup on mobile devices notification system - while email may or may not. Overall - the triggered activity => eyeball time is way faster with Pushover, Pushbullet, others as compared to email. As I mentioned above though - the way ISY processes substitutions in email and NRs is very different. Some substitutions are not supported in NRs (in particular the # substitution to represent the triggering device) because NRs are not processed synchronously on ISY - so by the time ISY performs the substitution it does not know which device triggered it.

Also in the wiki is documentation on substitution variables... https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables Date and time will be problematic for network rules - as to comply with URL requirements certain characters must be URL encoded - and ISY itself does URL encoding in the admin console as NRs are saved (rather than at runtime). So, time and date substitutions will not normally succeed in network rules.

Changing the 'admin' password in the Polisy GUI does not change it at the OS level. I don't know if that's intentional though - but you probably should have a way to address that. Otherwise - all Polisy users are gong to have a known admin credential open to local SSH. I'm only sending a single DNS service to my LAN devices - but POLISY is trying to use Google's DNS service by default (the local DNS host is third on the list). Is it safe to modify /etc/resolv.conf? [edit: Nope. This get's re-written each reboot] I also noted that 'reboot' still needs the admin sudu password. For a client device like this - the user probably shouldn't have to 'sudo' to issue a 'reboot'. I see that the polyglot user home directory is "/var/polyglot" - but the polyglot instruction is not quite accurate for the placement of the .env file. Instructions say "~polyglot\.polyglot\.env" but the actual placement on Polisy is "~polyglot\.env" I set the custom SSL variable and place my SSL certificate into /var/polyglot\ssl\custom - after a restart it's using my own SSL cert. Polyglot *really* should implement a UI for doing this... (and, as mentioned before - consider LetsEncrypt as an option!)