Geddy

@BrianN324 you mentioned this. I wonder if you set a static IP on the device itself and it's outside the DHCP addressing for the new router. This was very common for users that setup the ISY994 a long time ago as that was once the suggested rout of keeping the IP address stable. Currently, the suggested option would be through IP Reservations at the router level. And why UDI removed this ability in the Polisy and eisy devices. If you try the above options and still cannot "find" the ISY perhaps review this from the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY If you can't remember what the IP you used for the ISY994 there might be no other option than resetting it. Hopefully you have a backup of some sort, but if you haven't accessed the ISY994 in a while it might be last ditch effort to reset it. If you know DHCP table used in the old router you could set that temporarily in the new router and perhaps the device would connect on bootup. Then remove the static IP setting in the ISY994 configuration tab and allow automatic DHCP. Unplug the ISY994. Then reset the router to how it was before this and let everything else connect to the router before powering up the ISY again. Depending on how long ago you replaced the router maybe you still have it and can power it up (not connected to the internet or anything, but enough to connect the ISY994 directly to it and maybe plug a computer directly to it to attempt to access the ISY994 that way. (If the above changing the current router DHCP table is not an option for you) One other option I can think of, and would only work if the device is connected to your network is to ask if you have it connected to the UD Portal (my.isy.io). If you have an active portal license for it see if it is showing connected to the portal. If it is then you can use the remote access address from the portal information section to attempt to add that "Admin Console URL" to the IoX Finder window you posted above. Then use your UD Portal credentials to access the ISY994. PS: If you do have the portal access it shows you the "Internal IP" as well. But I think the device has to be connected to the current network, and if you're IP isn't within the DHCP table of the new router it might not be making that connection.

@Bert2013 Probably the same issue reported in this thread:

This was mentioned earlier and resolved….see this post:

Not sure, that’s a question @Michel Kohanim or @Chris Jahn could answer, but it’s been something I have experienced with the eisy for the last few months and hasn’t bothered anything. Especially since they’re both auto discovered. I think it’s become more the norm following the “not found” issue that was fixed in the start.jnlp update recently.

This is normal and not a concern. ISY Finder is listing both the local IP address and local domain address when auto discovered.

@andrew77 take a look at the Coffee Shop area. There have been a few discussions about this question there.

@nowandthen see @Techman and @DennisC posts above. This should fix the “not found” issue. This was reported fixed in another post. The “https://eisy.local:8443/desc” is auto found and cannot be removed. It’s normal for how IoX launcher finds the eisy as long as your router supports local addressing this way.

@CoolToys look at the bottom of the list (I think). It’s whatever name you’ve given your eisy. It probably isn’t just ISY now. Neither the Polisy or eisy “shipped” with the query program as a default program. Many have just gone without, but many will add it (like yourself). It is used to update status for devices. If you don’t have an issue of out of sync devices you might not need it.

@wmcneil best bet is to contact UDI directly to ask them. https://www.universal-devices.com/contact-us/

@andrew77 this is an issue that others have commented on. I think there is an update if you run Upgrade Packages again. I know @DennisC had the issue and think he said it was resolved recently…maybe he can confirm. Otherwise, I think things work okay, but it is an odd error to have randomly.

@Jimini if running Polisy or eisy the process is simple: Open admin console and log in click on configuration tab click “upgrade packages” allow the pop up to remain on the screen Another pop up should appear after the process runs suggesting to reboot click “reboot” button while system is rebooting clear Java cache (checking all 3 boxes) download new start.jnlp from wiki or UDI Site (click on My ISY) run start.jnlp to put new IoX launcher on desktop Should be able to run IoX Launcher and your device should be found. If it doesn’t then try adding manually with IP or qualified name (see wiki for more info of adding manually) Once logged back into admin console check Help -> About to confirm firmware updated.

@bcdavis75 The issues you're having sound like it needs more attention than in this thread and possibly even a new forum post. I would suggest you open a support ticket with UDI to get to the bottom of your issues. https://www.universal-devices.com/my-tickets

Try to go to: https://##.##.##.##:8443/WEB/sysconfig.txt (replacing the #s with your Polisy IP address.) Then search for "UDX". It should read: udx-3.5.1_4 Polisy/eisy Admin Service When you said you "manually rebooted" did you pull power to the Polisy or use the "Reboot" button in Admin Console?

@CKlamkowski This new error looks similar to an issue had in this post: Please see if anything mentioned there works out. If not please start a new post in the OpenWeather area.

@andrew77 yes, if you right click on "My Programs" (or anywhere in the programs list) a menu option is "Find/Replace". You can search for device or you can search for raw text. If you've already deleted the old device it probably won't show up in any programs as it would error out. If you used the same name for the new device and didn't "replace device" (On the device you have an option to "Replace {device} with") it probably didn't put the new device into the old programs (I'm not sure if it's going to randomly restore a device if you removed it then added a new device and called it the same). Another option is to look at the summary tab and see if there's a recent run program (when you wake up). It's possible a recently run program will show you what's turning that light on if it's indeed a program.

@toddlock is there anyway you could add a Ring camera (Floodlight or Spotlight)? You could then use the Ring node server and the motion from that to trigger other device. The Ring lights can be another deterrent or you can set them not to come on and only blast the sprinklers I have a floodlight cam that triggers lights on motion in the middle of the night. So far it has worked really well.

@btreindershonestly, with it being a current version and Polisy I might suggest opening a support ticket in case there is an unknown issue in the 5.6.4. Uncertain what might be in the ZYCFG folder. Since Zigbee and Zwave are still being flushed out it might help UDI in some way to have this documented and troubleshooting steps they give.

@smileyw since we didn't get an update from OP on this issue it's not clear if they got it fixed with a support ticket. When you get the issue resolved please post an update to help others if it happens in the future. Having used PG3x on multiple browsers and even different computers (Win10 and Mac (with very old macOS)) I'm not sure why it wouldn't load for some (randomly). Only thing I can think of is to be sure you clear the browser cache, don't run any pop-up blockers or plugins that might be blocking sites.

Please open a support ticket with UDI to see if the can track down the cause of this. What is your current version for Polyglot? What device are you using? What browser are you using? Have you tried a different browser? What computer OS are you running? Perhaps @RedReiter83 can come back and update this situation. It's been two weeks. Certainly if they opened a support ticket this could have been resolved. And just out of curiosity if you browse to this site what shows up for you: https://polyglot.universal-devices.com/

@btreinders maybe @gregkinney can help you out as he just wrote something to do this. The underlying issue is that this shouldn't be necessary and issues should be addressed with the node server developer and/or UDI rather than thinking that just a random/nightly restart will "resolve" the issue. Not only would it help your situation, but could help the community as a whole for more reliable node server implementation. I run the Hue node server on eisy (PG3x) and don't have issues with it at the present time. In some early PG3x versions there would be issues after eisy update/reboot, but not in the last few months have I experienced a problem with it not running after eisy restarts.

@737simguy but you're still waiting to do a power cycle when you get back to the machine, right?

Sure thing. Looks like you've done almost all you can do to eliminate issues from the eisy side. Now you've just got to modify your future notification process to get timely notifications. Or modify your expectations of using antiquated options. And as I said above if you're experiencing that currently it might not always be that way. And everybody is encouraged to use an external account setup rather than the UDI Default account as a step to avoid such "volume" type delays if VZW imposes such. You've got to temper your expectations when it's a known issue and not just a sudden issue that you just happened to have been impacted by "recently". Good luck!

@mbking are you running any 3rd party anti-virus or firewall software? If so, disable anything running. If possible completely stop those systems (don't just snooze the anti-virus or firewall). Clear Java Cache (again) - make sure you select all 3 boxes (this removes the desktop icon for IoX Launcher) Delete UD*.state files (again - just to really clear stuff out!) Perform a full uninstall of Java (maybe using the Java removal tool on their site to remove any old versions of Java). Reinstall the current version of Java - if using Chrome to download it the best option is to perform an offline install (From here - https://www.java.com/en/download/manual.jsp) Run "start.jnlp" (make sure anti-virus and firewall programs are OFF) Run IoX Launcher Report back if this fixes it.

Yeah, you might have been "lucky" for a long time. It's not just UDI though, it's industry wide. And why you were "immune" to it longer than others is simply luck of the draw. What's strange is most seemed to report the issues during season changes (i.e. they had notifications when temp got too low (or too high) and realized they weren't getting alerts anymore). Sounds like you get alerts all the time and they just recently slowed. The update that @DennisC mentioned in the first was an patch that UDI released (no official announcement was made...just a comment in the IoX support thread. When local to the eisy please use this URL and look for "ISY-" and make sure it says at least 5.6.4_7 (as of today) https://eisy.local:8443/WEB/sysconfig.txt It's very possible that the eisy was sluggish and delaying the broadcast of alerts. If you do feel that it's still laggy and you've attempted other methods of not using the UDI default mail system and/or not sending email to text then you could attempt a support ticket to see if there is a way to test if it's the sending or receiving of the notification. Ultimately, there are different (most consider better) options than what you have "always used". It's just a learning curve to how to implement the changes. I find that if I don't get the results I expect from the forum search bar I use Google Site search. Searching like this would give a lot of results for your issue. Even just using site search for "vtext" gives a good idea of the issues others have had.

@apostolakisl what version of Windows were you updating?