Geddy

@mmb “EOL” usually means there has been an announced time of ending support. The ISY994 just went “EOL” after 14 years. Polisy has been unavailable for quite a while so I’m not sure when you bought yours, but it’s been out for almost 4 years and UDI has said they will continue to support it for at least many years (IIRC 3-5 years might have been mentioned). Meaning that would be supported for at least 7 years (at a minimum). Not sure what you are “annoyed” by given that amount of planned support. Considering some companies release devices and support much less time before a new product is released (I’m specifically thinking of router manufacturers). It’s amazing the life of UDI products and their (free) support for them. It’s not without their trying to get supplies to continue the Polisy line, but was better to explore other options and release the eisy. I think your original question was answered clearly. If you need more clarification the best way to ask this would be directly to UDI via their “Contact Us” options on their website. The forums are mostly user-to-user support. Providing the best guess from what many of us have read and inferred from other posts on the forums.

@TJF1960 not sure. But shouldn’t be an issue for those sizes. Make sure you zip them just to be sure they’re compressed as much as possible. Other option would be to open a support ticket (https://www.universal-devices.com/my-tickets) and attach them there, then PM @bpwwer your ticket number.

@TJF1960 send to @bpwwer via PM on the forums.

If you're using Windows and run start.jnlp and no icon is being added to your desktop this usually means you need to clear the Java cache and try again. In the past when Java updates it will remove the icon from the desktop and many have tried to add it by just running start.jnlp again, but it won't actually add the icon because Java thinks it is already there. So clearing the cache (selecting all 3 boxes in this process) should allow you to add the icon again next time you run start.jnlp. What "sensors" are you trying to control? As @MrBill states above typically "sensors" aren't "controllable". Since the problem above (not putting icon on the desktop) might imply that you haven't cleared the Java cache I'm betting that your Firmware and UI don't match (next time you're in Admin Console use the Help -> About menu and compare "Firmware" and "UI" versions. They should match, EXACTLY (even the time stamp). This is from a previous version for my system: What "instructions" are there? You might need to refresh your methods with the UDI Wiki paying specific attention to the eisy User Guide. https://wiki.universal-devices.com/index.php?title=Main_Page After you've reviewed the migration steps that @MrBill links to and further read some of the eisy User Guide hopefully you'll be up and running with the eisy. Finally: Not many people would risk downloading power point files. So in the future if you're posting images please save as image file types and only post images. Typically images or text files are all that are needed to help troubleshoot most problems around here.

Correct assumption...at least I assume as well. Looks like the internal card is no longer being offered on UDI's store site so maybe they're only selling the USB ZMatter dongle since that would work with Polisy and eisy options without having to open the case for the Polisy. Since IoX has always been geared only to Polisy and eisy then I would assume both units would be on this upgrade path and make all ZMatter hardware operational. Didn't appear to be at least according to the release: https://www.universal-devices.com/zigbee/ And in the announcement post: Unless wall switches are considered "modules".

@Michel Kohanim Nice stuff! Updated eisy from 5.6.2 just fine in a little over 3 minutes to first reboot. System seemed to go offline and/or reconnected the node servers during the process (got alerts on UD Mobile), but when logging into PG3x it showed I needed to reboot so went back to admin console (no notice to reboot) and rebooted. Reboot (button press in admin console) worked as expected. NOTE TO OTHERS: Lan access did require java cache clearing and new running of start.jnlp/IoX Launcher (https://isy.universal-devices.com/start.jnlp) to have FW/UI match. Didn't try cloud before clearing/reboot steps. System seemed to come up fine with node servers connected and working. Now if I only had zigbee devices to try!

You’re showing still on PG3x 3.1.33. This was a known issue with that version and fixed in 3.1.36. Best to press the button 6 times to shut down (power light should turn red after 30-60 seconds). Once red press it again to turn on. If it doesn’t shutdown then pull the power supply. Wait a little bit and power back up. Allow about 2 min to fully boot then try PG3x to see if you’re still on 3.1.33. Then use admin console and upgrade packages to get 3.1.36 installed. Will need to reboot once it is installed.

@someguy looks like you’re on a Polisy and running PG3. You’re probably on the most current version for PG3. The release you linked to is for PG3x that until recently was only for eisy. You can move up to PG3x, but if you are still using PG2 then you shouldn’t because that will be removed. You can always fine the current release announcements in this forum area: https://forum.universal-devices.com/forum/339-current-release-announcements/ The current suggested/recommended method for updating is always through admin console using the “upgrade packages” in the Configuration tab. You are on the most current version of IoX so you’re good there. (As of today!) You can find how to move to PG3x in the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x There are some posts about that from others that updated to PG3x so maybe read those posts. But just know there is no going back if you make the move and realize you didn’t really want to. Once you’re on PG3x you would run the “upgrade packages” and it should bring you up to 3.1.36 (current PG3x version).

Nothing I can do about it. That's something @bpwwer or @bmercier would know about.

@tmorse305 I don't think node servers auto update on restart anymore. There might be a different upgrade process. Look at the purchases area and it might have an "update" option. I wouldn't uninstall, but perhaps just reinstalling in the same slot would force the new version to install.

@LKO another option is checking out the Coffee Shop area of the forums. Some people are/were selling their old ISY994 (and/or some Polisy). Perhaps they still have them available if you just wanted to stay in the ISY994 product line. But, agree with @MrBill that eisy is the only current upgrade path. I would try a different power supply for the current ISY994 though as it could have taken most of any surge from a hit. But eisy has the same interface as ISY994 for java admin console and doesn't require cloud connection (although the UD Portal does add a lot of functionality). The eisy does add the ability to run node servers to add a lot of different systems into the ISY system for control and automation with one hub. It just requires a UD Portal account, but not a ongoing subscription to be able to buy/install most node servers. (Note: Some node servers might require a portal subscription, but I'm not 100% sure which ones - I think Ring might be the only one currently.)

@rick.curl I get the thought of #1, but when you think/consider what's offered in the Portal subscription for the price it can't be beat! ($20 for TWO years!) But maybe check the wiki for info about other remote connection options: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Remote_Connections NOTE: that the certificate portion is beyond the scope of support from UDI. So your VPN comment might be the best option for your situation. From my experience the Portal connection works great, and the likely hood of down time is fairly slim. How often do you really use the app to control something in the house while remote? I only ask because I almost never do. (That's the whole point of automation, right? Not to have to do something manually.) I'm surprised when somebody makes a comment along the lines of #2 above.

@Kevin N Welcome to the forums! The "Query All" program was the default/stock program in the ISY994 firmware. It was used to check status of all devices. It's not necessarily needed as long as you have good communication within your system, but it can be helpful if you have line noise or if the ISY994/PLM are missing commands or status updates. Since you just created the program and it was looking at the status the 3am query might have triggered if the status changed and the ISY updated and triggered the program. I don't have any of the devices you are using and would never automate my garage (for the fact I don't want something able to randomly open (or close) my garage). So I can't help with a suggestion of how to alter the logic so that doesn't happen, but deleting the 3am query all is fine...as long as you don't have other communication issues. You should also check if you have the setting of "query at restart" selected (on Configuration tab) as that could potentially trigger if the ISY994 reboots randomly.

@kzboray make sure you open a support ticket for this. It’s the best way to notify of bugs/issues that need to be targeted for updates.

@dennisric another option to the method @DennisC links to is dependent on how good you are with networking. You could change the DHCP table of your new device to match the old and your ISY994 should connect if it is in a valid DHCP range. Once you’re back into the ISY994 please remove the static option and allow auto DHCP. You can then change the router back if you want/need to. This kind of issue is why the preferred method was a router DHCP reservation rather than the Static IP being set on the ISY994. Too many people forgot this was set and end up having to reset the device without a current backup. Your issue has nothing to do with “June 1st”. It’s your network and as you stated you had the ISY994 set with a static IP.

@kewashi nice work! Just opened up a new discussion area for this: https://forum.universal-devices.com/forum/426-hubitat/ Good luck!

@Scott Korvek If you've attempted this several times and it still isn't updating you are probably best served by opening a support ticket with UDI and getting help that way. According to the wiki for this process it should be an automated process once the Polisy reboots. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Upgrading_to_PG3x The only other suggestion I would have is to use the Polisy IP address rather than the "polisy.local" url. Some routers might have an issue with "polisy.local" address. If you've been able to access the Polisy using that in the past then you should be okay, but if you've only ever used the IP address use that in the rest address and see if that triggers the flag correctly. If still not updating open a support ticket: https://www.universal-devices.com/my-tickets

In addition to what @DennisC suggests above another option would be removing the 300 series board, upgrade to 5.3.4, then migrate the Insteon devices. You have 16 Z-Wave devices, not sure how many programs are using them. Would it be a huge task to start the Z-Wave fresh? Depending on how many Insteon devices and programs you have it might be easier to at least migrate the Insteon portion and start fresh with the Z-Wave on the Polisy. I'm not 100% certain if removing the z-wave 300 series board is necessary in this method if you're not going to be using the Z-Wave, but it might cause issues with your existing z-wave. Just don't migrate the z-wave portion since UDI never recommended anything higher than 5.0.16C for the 300 series z-wave.

Yes, used 3 different computers. (2 locally and 1 physically remote location) Cleared java cache on all computers and downloaded fresh start.jnlp file. Not sure why some do while local, but it stems from when it first became an option with (then) ISY Launcher because the "cloud" version tended to load a little quicker than the local connection (no real proof that it did/didn't for me personally, but remember people commenting that way). Otherwise, the cloud option is only available when trying to connect to the IoX service while not on the same network. Some will use the (old) port forwarding method (not so safe), but most will use the UDI Portal connection method (using the UDI Portal credentials) to access the admin console while remote. Since it's been confirmed by UDI that there's an issue we just need to wait for the fix. Just a small bit of the Java console log: https://isy.universal-devices.com/iox/5.6.2/iox.jar https://isy.universal-devices.com/iox/5.6.2/ce.jar https://isy.universal-devices.com/iox/5.6.2/chart.jar Exception in thread "AWT-EventQueue-2" java.lang.NullPointerException at com.udi.insteon.client.InsteonOps.isControLinc(Unknown Source) at com.udi.insteon.client.InsteonOps.isInsteonController(Unknown Source) at com.universaldevices.client.ui.InsteonCellRenderer.getTreeCellRendererComponent(Unknown Source) at com.universaldevices.ui.driver.UDProductDriverCellRenderer.getTreeCellRendererComponent(Unknown Source) at javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(Unknown Source) at javax.swing.tree.AbstractLayoutCache.getNodeDimensions(Unknown Source) at javax.swing.tree.FixedHeightLayoutCache.getBounds(Unknown Source) at javax.swing.tree.FixedHeightLayoutCache.getBounds(Unknown Source) at javax.swing.tree.AbstractLayoutCache.getPreferredWidth(Unknown Source) at javax.swing.plaf.basic.BasicTreeUI.updateCachedPreferredSize(Unknown Source) at javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(Unknown Source) at javax.swing.plaf.basic.BasicTreeUI.getPreferredSize(Unknown Source) at javax.swing.JComponent.getPreferredSize(Unknown Source) at javax.swing.ScrollPaneLayout.layoutContainer(Unknown Source) at java.awt.Container.layout(Unknown Source)

You're lucky then. Can confirm cloud option doesn't work even if local. Tested earlier (while remote using portal login) with java console logger and it gives a lot of errors of "unknown source". UDI acknowledged there being an issue (per @TheA2Z post above) and plan to fix in upcoming release. When admin console loads it just loads the "File" menu, and even those options don't come up cleanly. @kzboray Seems this is an issue with 5.6.2 since also impacting your Polisy on that version. It does look like some reported this earlier this month so it's something that's been an issue for this release.

@naeblis So glad it was a "simple" fix! Glad you're back online and working. Good luck! Really glad that things seemed to go smoothly overall. Thanks for posting your experience!

@TheA2Z @Athlon I was able to test the "cloud" option to connect to Admin Console today and couldn't even get it to load the entire menu option to get the help -> about option to compare firmware. It does appear there might be an issue with the cloud connection function. Hopefully with the support ticket(s) in this will get addressed quickly. I was able to get help -> about to come up by using the keyboard (alt + h -> a) and get the same mismatched time stamps as above. For the time being the local connection method seems to work just fine. But, you've got to be local for that to work. If needing to access things while remote it does appear that UD Mobile works while away. Depending on what you needed to adjust though you might, or might not be able to handle it with UD Mobile.

@naeblis strange that everything was working then suddenly it doesn't seem to connect. It's possible that during the reboot something didn't load correctly. I'm sure you've probably tried to power cycle several times and it still isn't coming back up. It's possible it could have been in an update status depending on what you had been updating during your setup. It is possible to setup wireless connection, but you need to use UD Mobile with that (I believe), and I it's been a while since I tried it that I can't help with the direct steps to try. Read through the eisy User Guide in the wiki (https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide) and it should help you with the wi-fi setup. Ultimately, it might be best to start a support ticket just to be sure something else hasn't happened to the device: https://www.universal-devices.com/my-tickets What brand/model router are you using? The only other steps I would suggest is to power cycle the router. Unplug the eisy (both power and network cable), then power cycle the router. Allow the router to fully boot up. Log into the router, if you have an IP reservation for the old ISY994 or the new eisy remove them (both). Then connect the network cable to the eisy and router then power up the eisy. If it reconnects to the router then you can setup IP reservation again from the router. Also, are you using any Insteon devices? You mentioned getting all your z-wave devices back online. Just wanted to make sure if you have Insteon devices that the PLM is connected via USB to the eisy. The network jack on the eisy is just that...a network connection, not the PLM/serial connector like it was with the ISY994.

@naeblis welcome to the forums. I'll assume that "no longer showing online" means from the Portal when logged in. Are you able to access the device locally with admin console from a computer? Make sure that you can connect to the device locally. It's possible during the moving around or power cycling that it activated the wireless setup and didn't reconnect via the wired connection. Unlikely since I think when a network cable is connected the wireless is disabled, but could still have been bumped inadvertently to initiate the wireless setup. Check from your router if you see the mac address for the eisy as a connected device. Lastly, double check that the portal registration isn't pending in the admin console. Configuration tab -> Portals That should show "Online" and "Registered"

@TheA2Z @Athlon not sure how much Michel might actually be watching the forums currently so best way to report this as possible bug is through a support ticket. https://www.universal-devices.com/my-tickets/ Certainly the advised method to report bugs so they can be tracked and fixed internally is through support tickets. Be sure you attach screen shots of UI/FW information to your ticket.