Geddy

@iggies on what device are you trying to upgrade the firmware? You need to clear your java cache. Download the file @vbphil linked to above. Run the downloaded file. In clearing the cache make sure you select all three boxes (see below). Also, review this section of the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Since you say the UD logo comes up, but nothing else you might need to remove the .state files found in the directory referenced in the wiki. (I just checked...still accurate as of Windows 10)

The move from 4.x to 5.x was a big step so any move to 5.x to be able to use UD Mobile will require some time to get things sorted out. There have been a lot of posts about this, but simply saying...read the 5.3.4 release thread. Skim it and look for pitfalls. The simple answer to your question: Go directly to 5.3.4. Do NOT think about anything else. You don't have Z-wave so you don't need to worry about the warnings on 5.0.16C. Don't even consider installing some random version of 5.x and then thinking you will upgrade to 5.3.4 if it went better than expected. The best, and perhaps safest thing is to bite the bullet and install 5.3.4. Now, here are some pitfalls to watch and hopefully minimize your "pain" (interaction) in the update process. Backup current system - yes, it tells you to do this in the release thread, but do it again just to make sure you've done it. On the ROOT folder of the Programs tab right click and select "Copy to Clipboard" (it's the LAST option in the menu). Paste the programs into a (plain) text editor (like NOTEPAD for Windows). DO NOT PASTE IT INTO WORD OR OTHER WORD PROCESSING PROGRAM - it could auto format text and you don't want that. MAKE NOTE of any "Disabled" programs - on some occasions when you go to 5.x all programs become enabled so you will need to disable any permanently disabled programs you have. If you have any "adjust scene" programs you will need to correct those once you update. Be sure when you're done that you properly clear your Java cache (checking all three boxes in the process!) Download a fresh start.jnlp file from UD website or the wiki site. (I usually tell people before doing this to delete any OLD start.jnlp/admin.jnlp files from anywhere on the computer as sometimes OLD files will be used, and you need a fresh file that you just now download. This should get you there. Give yourself some time to accomplish this. Don't expect to have it done in 5 minutes, but it usually shouldn't take too long either. Hopefully you're currently running 4.9 (last 4.x version released). If you run into issues you can download 4.9 again from the previous release area and restore your 4.9 backup and be up and running quickly. Post back and let us know how it goes.

I experienced a similar situation trying to update the Polisy. Take a look at this solution posted by @Michel Kohanim to help. Step #2 helped resolve my issue.

@Voluntario What are you running the Node Server on? You mention ISY 5.4.3. That would be ISY on Polisy (IoP). Do you perhaps mean a standalone ISY994 running firmware 5.3.4? What weather node server are you wanting to install? They all setup a little different. Are you trying to run PG2 on a rpi (raspberry pi) or are you running PG3 on Polisy? There's no longer Polyglot Cloud (it shutdown last February). And now PG2 (Polyglot 2) that is able to run on non-Universal-Devices hardware is no longer supported by UDI, but would still be available if you had the ability/skills to run/setup. You can find more about that process in the Polyglot area. If you indeed have a Polisy you can run Polyglot v3 (PG3) and install any of the available weather node servers to fit your need. All will/should have a "more info" link to documentation that facilitates the setup process. If you do mean that you have a standalone ISY994 (running Firmware 5.3.4) note that PG3 can push node server information to the ISY994. You would need to have either the Polisy (no longer available for order) or eisy (just released and currently shipping) and run PG3/PG3x and setup the node server to push weather information to the ISY994. Final note: The current version for ISY on Polisy or ISY on eisy (both now referred to as IoX) is 5.5.

Yes. It does. Can confirm after setting mine up today. You had good experience with that upgrade. I had to go a more brute force approach, but got it upgraded without much fanfare. Thanks to @Beaker for his thread that @Michel Kohanim posted steps that resolved my issue. 👍

@smokegrub are you connecting locally or remote? Are you sure you're on the same network as an ISY? What computer OS are you running (Win, Mac, other)? If the portal is able to connect you either have to add them manually (if you're local) or almost certainly need to add them manually if you're remote. Otherwise, if you've saved the finder information in the past you can reload a saved state file (File might look like this: ISY-Finder.<Day Date Time>.state) Have you updated Java recently that it might have lost key files/history? It might be good practice to clear Java cache and download a fresh start.jnlp (IoX Launcher) to put a new icon on the desktop and try finding them again when it opens up. Usually this happens to me when I'm connecting while remote. Since finder doesn't find anything on the local network it wipes out previous entries. I have to add the ISY manually or reload a saved finder profile.

Interesting. I haven't had problems supporting it, but I only support for me and my in-laws. It's simple, easy and works. Even able to access it easily from halfway around the world. Seems like your experience has been more challenging. One great thing about the stability of the ISY system has been its reliability. So really haven't had much need to change it over the years.

Nope. Just another user, like yourself. Thus the suggestion to contact UDI through their site. That's always the most direct route. Especially during times like this where their attention is placed more on getting devices and getting things to other users.

Since I don't use IR I guess you're right. Nothing "receives" this. Perhaps you can contact UDI directly via their web contact options to express your thought over missing IR. Figured it was answered fairly obviously above and in the years since Polisy was released. Didn't see the need to beat the dead horse.

IR was removed in Polisy and not available in eisy. There are alternate options using node servers and IR devices as @lilyoyo1and @gzahar point out above. Doubtful it would ever be added back in.

Yes, for admin console access...just as ISY systems all have. It's been said that UD Mobile will certainly be an option and the goal is to have a Windows and Mac (M1/M2 chip) version (already running on macOS). Admin Console with IoX Finder (as we all know and love) will remain for quite a while.

@PGannon have patience! Original expected ship date was 12/27. @Michel Kohanim posted that they got a shipment in early and processed orders. Perhaps based on quantity received only a portion of orders were able to ship EARLY. Others will process as supply allows. It's the holidays! Do you really want to be spending time tinkering with home automation? The process UDI has usually will send an alert when a shipment is sent, but you can also keep checking your order status and it should update soon enough. Note too that the holiday shipping crush and now the nation wide winter storm will probably have elongated negative impact on shipping. Just let the process work. Happy Holidays!

@SSamuels I guess I'm glad it's working, but what you're saying is working now is not the issue you posted as your thread title. You were saying that PORTAL was down. And the file of screen shots showed that the Polisy was "offline" according to the portal. But now you're just saying that Polisy works with node servers. What happened to your Portal issue? You've simply ignored that. 😠 I'm so confused by what you think your problem was and how it magically resolved itself. Glad it did though. So guess you didn't follow any suggestions. It's just a Christmas Miracle. 🎄 You still need to use a different version of Java (current version is 8, update 351) not sure what you're saying is version 1.8.x. 😕

Locked thread as original question had been answered. Tagging onto old threads tend to cause questions (and solutions) to be hidden. Use the "Start New Topic" button to begin a new post.

I think you need to update Java. What OS are you using? If Windows the Java version downloaded from Java.com should be Version 8 Update 351 (currently). Step 1 - clear Java cache (select all 3 boxes so it removes IoX Launcher from desktop) Step 2 - remove/uninstall the current Java version and possibly run the remove all old Java versions (see Java.com site for this process). Step 3 - download Java from Java.com Step 4 - download new IoX Launcher from UD site (see wiki for link) When you get current version of Java and get logged into Admin Console make sure FW and UI match (Help -> About). Set memory setting again if needed….I’ve not needed it on current desktop or laptop Win10 systems.

Sorry...can't help specifically for Android devices. Perhaps others can. I know for the iOS world the Alexa app has some included geofence options to trigger lights when users arrive/depart depending on how the routine is setup. But I know others say that Android has been known to kill the background running apps so I'm not sure if that's a viable option. I think there has been some talk about tasker running something that's triggering as you enter/exit the geofence. Actually, I remembered a post earlier this year and found that @Jimbo.Automates posted this note about using wifi to trigger tasker. Not sure if this still works, but perhaps reading the comments in that thread would help. I know @Javi has commented that geofencing is in the plans for UD Mobile, but think it's still a ways off from being implemented. Hope that helps.

@SSamuels why hide generic screen shots in a PDF? Very unhelpful to have to download a file to only have screen shots. You can paste screen shots directly into your post (if on a computer). When posting you can double click the image after pasting it to make it smaller on the post and still be clickable (by the reader) to see a larger image (that has better quality than the images in your PDF). When you're logged into the Admin Console (locally) click on the configuration tab. Is Portal showing active? You might need to revoke and then re-add the IoP to the Portal to send approval to the device again. Please review: https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cannot_Communicate_with_ISY_Portal

@EWhite a bit confused by your post. What is it you're trying to accomplish? What do you mean by "basic location services"? Yeah, what you describe will fail because ping is probably unreliable for what you might be attempting to use it for. Need more information to be able to help give options for what you're trying to monitor/do.

@waffles was going to reply sooner when I saw this, but was on a mobile device and was difficult to type. Was going to suggest doing just that. Especially the trouble devices. Typically I suggest people log into https://alexa.amazon.com/ (Smarthome -> Devices) and remove devices from there then tell Alexa/Echo to discover devices and try it out. If still trouble then remove again (if they appeared on the site again) and then perform a refresh/sync from UD Portal (button on the far right) If it was a few weeks it's possible that it could have been during one of the few outages that hit earlier this month. Then @bmercier suggested to re-enable the skill to re-link the portal account should have fixed it.

The email information you reference is with regard to z-wave migration from 500 series z-wave to ZMatter board. That's still in development/review. I'm not sure about an upgrade path for smart meter and might be something you have to contact UDI directly. Probably best to go through sales for this, or you can open a support ticket. sales@universal-devices.com Support Ticket process -> https://www.universal-devices.com/my-tickets/

The only way I'd see to be able to remotely restart anything would be through the admin console in the Polisy System Settings there is a "Reboot" button. I presume that would reboot the entire Polisy device. As @Bumbershoot points out you'd need to have port forwarding open to possibly connect to the device itself. Otherwise I've seen some comment on using Teamviewer to connect from a remote location to the local network (i.e. leaving a computer running 24/7 w/ Teamviewer running). You would then access it as though you were local. Otherwise, you would need a router that could handle inbound VPN system to put a remote computer on the local network.

Don't sweat it. Remember you can RENAME the device/item whatever you want it to be. You've left the default name of Polisy. The image you posted came from somebody that named it IoX. Just don't rename it "silly blue box". It will crash and take over your house and never give back control! If you're waiting for the eisy to show up then I'd sit tight on what you're running. Let things settle a little bit before you upgrade and have to fix what had been a working system just to convert to an entirely new system.

@Silversop As @lilyoyo1 pointed out, but might have referenced too generally is that what you've done is add the z-wave controller to your Polisy. That will only add z-wave devices to the ISY on Polisy (IoP) system. That will not feed/push devices to the separate controller (your ISY994). For you to have everything in one ISY system you would need to migrate the Insteon to ISY on Polisy (IoP) per the information in the wiki (Polisy User Guide) . Otherwise, you could run IoP only managing the z-wave network from there. Just know that the IoP and ISY994 systems do not talk back and forth so you wouldn't be able to maintain Insteon+Z-Wave devices with one program. Once you migrate to IoP then all Insteon and Z-wave devices would be on the same ISY system (IoP). Please make sure that you have been updating your Polisy along the way. If it is very out of date you might need to open a support ticket to get assistance bringing it current. Please pay special attention to the section about if your Polisy OS is below version 13 (in the wiki). Just for reference, log into Polyglot (hopefully V3) and take a screen shot of your version. I believe the latest version should show 3.1.16 for Polyglot (PG3 version). Should be http://polisy:3000 or http://##.##.##.##:3000 (where the #s are your ACTUAL IP address for your Polisy).

Might be best to wait and see how the migration process works out before planning further move. From the comments it sounds like they're very focused on getting z-wave migration worked out as soon as possible. 🤞

Should be a 300 series z-wave controller. You can go to 5.x, but the highest you could go would be 5.0.16C. Be careful if you plan to upgrade to that version because there were big (perhaps HUGE) changes from 4.x to 5.x. Make sure you read the steps if you do decide to update, but at this late game it might not be of value to you to upgrade. There's not much ability gained going to 5.x (5.0.16C in your case) without running a Polisy for PG3 (or rpi locally for PG2) to have access to run node servers. I don't know about eKeypad, but I also use Mobilinc and it works fine with 5.x (I'm running on 5.3.4 on ISY994). There seems to be issues with Moblinc on ISY on Polisy, but haven't attempted that route so can't comment further. Though it does sound like the developer for Moblinc might update the product to be able to be used with Polisy/eisy in the future. You should check with them for support options moving forward. At this point I might suggest just getting the eisy + ZMatter board and starting fresh. It's quite the task to update to 5.0.16C and then another task to learn the eisy+ZMatter system (once eisy is even out). You would be better served starting fresh (IMO) and also learning UD Mobile for the remote access. It's certainly become the go-to app for many around here. The ultimate question is what devices are you connecting to? If 100% of your z-wave devices are 300 series then you can use those, but it will be limited. If no devices have been updated to 500 or 700 (zwave plus) devices then you've got bigger issues than trying to figure out what controller you want to use. Note too that Elk is no longer handled as a module, but as a node server. So if you don't have a Polisy you wouldn't be able to connect to the Elk until you have eisy and IoX running and install the Elk node server. The Elk module would still work in 5.0.16C as it wasn't until you went to ISY on Polisy (now IoX) that you lost the modules. I'm not sure what "ISY Module" is. Do you mean ISY Portal?