Geddy

@RedReiter83 just in case this might have been a glitch in 3.2.1 please update to 3.2.2 (just released today). After you update, try using a different browser. I always use Chrome and it works fine. I've never seen it not populate the pull down where "production store" should show. You're on Firefox. Perhaps you're running a plugin or something that's blocking some portions of the site from loading. Try in a private browsing session and/or try in a different browser. When I tried in Firefox (and in Chrome) it never allowed the dropdown to be empty. Are you running any other VPN or internet security software that might block web from loading all aspects? Last option is to click "System" -> "Switch portal profile" and log into the portal again.

Thanks @bmercier for the update. Was able to update with "Upgrade Packages" then reboot and all seemed to work fine. Haven't pulled the power yet this time as things seemed to sort out well on first attempt. (@MBell, I wonder if more time was needed between the reboot and when you tried to log into admin console again. I allowed about 5 minutes (give or take) because I got into something else before I came back to the update.) For those that come later here are two screen shots to watch for: After hitting "Upgrade Packages" you get this alert (I usually leave this on the screen and don't go back to working on the admin console while the update is running) A few minutes later I received this alert: After clicking "OK" to both alert boxes was at the Configuration tab in admin console and hit "Reboot". Admin console closed and I allowed ~5 minutes before trying to open/access admin console again. I then confirmed I could log into admin console then tried PG3x web interface and all was right in the world.

@Jim P do you have remote connection enabled on the UD Portal? Requirements from the Node Server: PG3 Remote connection must be enabled and active Settings are in Portal under Select Tools | Maintenance | PG3 Remote connection After you updated to 3.2.1 did you run the system "Re-install all node servers"? I know you can't get this one installed, but making sure you got the others installed to get the UDI Python interface updated that's a necessary path. Not sure if that's something too, but just wanting to make sure that part has been completed successfully. In the meantime, could you also try to install a free node server to see that it installs correctly? Maybe something like Ping...just a random one. Can be removed if it installs correctly if you don't want/need it. Or any other free one just to try to make sure something installs.

Interesting that it doesn't go to the desktop by default. It always has in prior Windows versions. I don't run Win11, but if it's like Win10 just drag it up to the desktop. Otherwise, clear the Java Cache (checking all 3 boxes) then run start.jnlp again. That should add it to desktop. If not, your settings might be blocking desktop icon creation. I've not ever seen others say it doesn't add it to the desktop in Win11. Glad support resolved the issues.

What do you mean "stuck" on 5.6.2? If you're having issues with the update process at this point please open a support ticket and get help that way. Otherwise please start a new thread to get direct help to your issue. @mikeorst same for you. If you're "stuck" either post a new thread to get specific help or open a support ticket with UDI to get their help for the update process. https://www.universal-devices.com/my-tickets For most users, it seems to be smooth updates from "recent" versions. Since the pace of updating is keeping steady being several versions back might make it a little more difficult to support directly on the forums. There are a lot of posts to check for tips/tricks of making the update take. Usually the simple solution (at least step in troubleshooting) is to: Press "Upgrade Packages" button Leave alert/warning on screen In a few minutes if you're using UD Mobile you might get alerts of device going offline, then online Sometimes another alert will pop up on the admin console window that updates are complete and a reboot is needed. Press "Reboot" button in the admin console. Wait for UD Mobile to notify offline/online status (again) Depending on your hardware, perform a multi function button shutdown (review wiki user guide for your device to find this process) Pull the power supply Wait 20-30 seconds Plug in Wait 2-3 minutes Clear Java Cache (while waiting above) Download new start.jnlp Run start.jnlp Run IoX Launcher Access Admin Console (LAN) [if local] Confirm UI/Firmware in Help -> About menu The issue has been that some older firmware the "Reboot" button press in Admin Console isn't fully triggering a full power cycle of the device. It's stopping most services, but not enough to fully update the system. Many have found that shutting down the device and pulling the power is the best troubleshooting step to take. I suggest shutting down the device first rather than just blindly pulling the power supply because sometimes updates either can still be running or something else is stuck and just pulling the power could corrupt those processes.

It's not a given to go directly to PG3x, but that is indeed the only one that is currently being updated. For the Polisy running PG3 the current version appears to be 3.1.21. So confirm you are running that version at least. Moving to PG3x means that if you have any PG2 node servers still running that you will lose those as PG3x removes PG2 from the Polisy. You still haven't said which node servers are giving you trouble. It might be best, since you haven't provide enough detail to really help troubleshoot your issue further, to open a support ticket and get help that method rather than multiple forum messages to not get much further into the issues you are having. You can read more about the process of updating to PG3x on the Polisy User Guide in the wiki. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide

@gregkinney randomly rebooting to try to restart node servers is not a suggested "solution" to the problem. Best to narrow down what node servers are giving you issues and troubleshoot why they're acting up. 1st step is making sure you are on the latest version of PG3. Are you running Polis or eisy? Are you on PG3 or PG3x? If on eisy and not on PG3x 3.2.1 then you need to upgrade to that and then REINSTALL all node servers (it's a menu option, and in the instructions found in the announcement post for 3.2.1). From there you should focus on one giving you issues, put that node server log into debug and then restart the node server. After it settles download the log and contact the developer of that node server either by posting in that area or perhaps via forum PM. Sending them the log privately is best to get them to review it specifically to your issues. If the developer of your problem node servers is not active on the forums then submit a ticket to UDI and include the logs with the support ticket and maybe they can help identify what's causing them to fail regularly. https://www.universal-devices.com/my-tickets

Maybe @bmercier can help here. Otherwise, perhaps open a support ticket and include a log file with the ticket. https://www.universal-devices.com/my-tickets What PG3x version are you running? You might want to make sure you're on PG3x 3.2.1.

@Eric best to submit a ticket to UDI to get this fixed with you. https://www.universal-devices.com/my-tickets First make sure you're following the steps here: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY I suspect you might have a license on the eisy. Bullet bolded below says not to have it licensed or only have a trial. If you've got a license on the eisy you will need UDI to help complete the migration.

@RedReiter83 on the right side there is a drop down box that appears blank in your screen shot. See if you can get that to open and select "Production Store". Then perform a hard refresh (Chrome is Ctrl+F5 (Windows)). Please also note that the current version for PG3x is 3.2.1 (as of this posting). You are showing 3.1.36. Not that it is directly related, but please update to the current version to make sure it's not a lingering bug. Report back after updating if you still have the issue.

For some reasons sometimes the "Reboot" in the admin console doesn't force a full reboot/power cycle of the device. Since you mentioned your eisy is in a difficult spot to get to if unplugging isn't easy if you can get to the power button (aka "Multi function button") you can use that to reboot (5 button presses) or shut down (6 button presses). Another option might be to put it on an on/off outlet (maybe not z-wave or zigbee) that can be controlled by a 3rd party app should the eisy become unresponsive. Some have commented about using a Kasa outlet to be able to use the Kasa app to cycle the device. Not the "cleanest" of ways, but an option. Finally, I think Michel's comment about a ticket might have been to help troubleshoot what happened so they (UDI) can learn from the issues from the update. Glad the power cycle worked!

Glad you got it working! Seems like could have been a corrupt Java install since removing it and all directories helped resolve the issue. As for the eisy not showing up it could be your network not allowing it to announce itself correctly. Once you add it though you should save the list in an easy place should you need to load it later. With the ISY Finder window populated with the eisy (and your ISY994 while it's active) just click "SAVE" and it will offer a file name like "ISY-Finder.Wed 2023.08.16 04.30.36 PM.state". Save that locally in a quick and easy to access directory. Then if the entries go away you can hit "LOAD" and find that .state file and it will get you back in business. When adding manually try to add: https://###.###.###.###:8443/desc <-- change all the # to your IP address for the eisy. https:// eisy.local:8443 /desc <-- remove the spaces I added (https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Can't_Find_eisy) Also, make sure that you set an IP reservation in your router for the eisy so it's not always changing IP address on you. My router usually has no problem with the IP address being found for the eisy, but is slow to resolve the eisy.local address. The ISY994 was able to set a static on the device, but that created a lot of issues for casual users over the years that UDI removed that ability in the Polisy and eisy so IP Reservations are the only way to keep it from getting a different IP when the network lease for IPs expires or network restarts.

If you're seeing something like this: You might need to delete the UD*.state files. First, stop all Java Web Launcher processes (i.e. make sure nothing showing IoX Finder or Universal Devices Administrative Console are active). https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored If there's not multiple .state files in your folder it might be worth performing a search for UD*.state on the root directory and/or making sure hidden files are shown (though these typically aren't hidden, but you never know). You keep mentioning "admin.jnlp". If downloading directly from the ISY that's fine, but please make sure you delete all OLD copies of that file anywhere on your computer. For the last five years IoX Launcher (formerly ISY Launcher) has been the suggested method to access the admin console. IoX Launcher is the process @Techman links to above "start.jnlp".

Seeing that this problem is over 3 months old, and applied to a different IoX and PG3/PG3x version, what is the "same problem" you are experiencing? Seems like there are multiple problems above so your statement isn't very clear to receive help. If you're unable to log into PG3x perform a full power cycle of the device (not just a reboot button push in Admin Console). Have you attempted an update recently that caused this issue for you? You're best off starting a new topic and describing your issue exactly so that you can get help for your current issue.

Probably best to follow the directions in the wiki for that: https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings The wiki is more the living documentation type so it's been updated to be more accurate. The Cookbook was written/released once and hasn't been updated. It's mostly just a copy of the wiki at that moment in time and relates to 4.x firmware (in most situations...if memory serves.). While a lot of the parts of the cookbook still apply some parts are very outdated and the wiki is the more current documentation to reference.

@someguy moved your post to the specific Rachio area since it's specific to that node server feeding info to IoX. Perhaps: close Admin Console, open PG3x web interface, Click "Restart" for the node server, open Admin Console, on the root of the node server if there is a "Query" button press that. Or perhaps right click the node server and select "Query". I've never had a need/want to delete a node so haven't had to add one back. But know closing admin console and re-opening it sometimes brings things back in sync with what PG3x might be feeding to it. Perhaps just need to force the restart of the node server to push the nodes back to IoX. Need to ask the developer on that. It might be better to work with them to figure out why they're blank in the first place. Most developers will watch their node server forum area, but you might need to mention them to get their attention. Sadly, for this node server looks like the developer isn't around to support this (looking at other posts here). Might be on your own for resolutions of any issues.

No clue. My PLM isn't in a location that I can see/notice the LED so it doesn't bother me. More than likely there could be a program condition that is firing something back to the eisy, but that's just speculation. You can look at the summary tab in the programs tab to see if a program ran recently. If you're really bored (and apparently you are because you're watching a LED on the side of a device just plugged into the wall) you could open Admin Console then Event Viewer and set it to level 3 and watch for Insteon traffic. Otherwise...stop staring at the PLM! You'll break it! So you got the query program cleaned up? Glad that was simple!

@wacvmd personally wouldn't ever press such a button unless UDI/UDI Support said to. I think somewhere in the early days of the eisy there was some troubleshooting functions that allowed UDI to get more information from users and that button just hasn't been removed. For the most part the only button needed for updating the Polisy or eisy is "Upgrade Packages" then "Reboot". I think even Enable TPM and Upgrade Bios were for Polisy and not sure they even apply to eisy. But not 100% certain. I just don't make a habit of randomly pushing buttons unless specifically told to for a good reason.

@RRoyceus, you keep using the words "write the changes". Are you hitting the button on the device that says "write changes"? As @Techman and @MrBill said in the replies above to set the "On Level" you have to hit the "On Level" button to the left of the dropdown. This is what sets the ON LEVEL for that device. I wouldn't look for raw text of on level, but rather the devices you indicate it happening two "before and the one today". This would find any program that references those DEVICES. Perhaps there's a random program that you don't recall making that's somehow been corrupted or changing the "ON LEVEL" and you didn't realize it was happening. Otherwise, you can ineed look for "On Level" in your programs. Just change the Find to "Raw Text" then type in On Level in the next line: That will take you to any program that references an "On Level" setting. Make sure that's set to 100 (or whatever you want it set to). Then SAVE the programs. Then find it again...going through that process until you get back to the first program you fixed. Note that setting an "On Level" in the program does not turn the device on. It simply sets the "On Level". So if you have to use the "ON" function. Should look like this: Then Set 'Master Bath' On This is the CORRECT display for programming to turn a device ON. There should not be an "On Level" used. It should just be "ON". At least for MOST simple programs of "If x, then turn on". While this is one way to "fix" this, it's not the most ideal way (IMO). This will ALWAYS trigger this light to 100% when this program runs. While this might work for this situation sometimes you might want the light to not be at 100% when motion is triggered. Since you're using a motion sensor to trigger a light I'm wondering if the motion sensor isn't triggering correctly and not even running the program. Have you looked at your "Summary" tab on the programs to see what's run recently when you have this issue? Please help us understand, you said the devices are being set to an "on level" of 0 (zero). Where do you see this? Are you look at the admin console and the device itself? If it looks like this when you're viewing it what do you see is "0"? While the screenshot clearly has an "on level" of 100% the "ON" percent is currently 0% for this device because it is "OFF". When I use the "On" button in Admin Console the on line changes to "100%" because the "On Level" is set to be 100%. Are you expecting that the "ON" % should be 100% if the "On Level" is 100%, but the light is off so you're reading that as "0% On Level"? Finally, no, this appears to be isolated issue that you're having (at least here on the forums). I run nearly all Insteon devices and have a couple of programs that adjust the "On Level" given the time of day as well as using Alexa to turn other lights on/off during the day and do not have the experience you are having. Earlier you said this problem started when on the Polisy. Since you're just now bringing it up there's little chance that anything that changed in your system recently triggered this. My random thought is that if might even pre-date the Polisy if you used the ISY994 and went from 4.x to 5.x firmware on the ISY994 there was an event in the update process that enabled all programs. You might have made a program ages ago that you thought was disabled, but silently became enabled in an old ISY994 update that you only noticed/experienced recently. Just a theory, but could certainly explain why it was happening during the Polisy time and moved to the eisy. Either way..."just living with it" isn't a solution for most. Glad it might work for you. You've been given a lot of tools to try to hunt down the culprit and fix it. Please post back with any additional findings you might make that somebody can truly get this issue resolved for you. Good luck!

@PapaBear nope you used "export to clipboard". The very last item is "COPY to clipboard". It will provide a very nice and clean version of the program. Like this: 00-Query All - KEEP If Time is 3:10:10AM Then Set 'eisy' Query Else - No Actions - (To add one, press 'Action')

select the program right click choose "copy to clipboard" paste in a reply That's the BEST way to share programs on the forums. It allows them to be searchable for others that might have issues, and helps anybody trying to help adjust/alter your programs by not having to type out changes.

@PapaBear did you migrate from the ISY994 to the eisy? It's possible that the program used the old name for the ISY994 and there might be a new device name in the eisy. Just select the program, adjust the device to the name of the eisy and save the programs. It should clear up. If not, you can delete the program and re-create it manually. Note that the Polisy and eisy do not come with the (old) default "query" program.

Updated and installed almost okay. Had to perform a full power cycle to get the Z-wave portion to become responsive again. There was not an alert to reboot, but eisy did seem to reboot in the process based on notifications to UD Mobile. However, z-wave was "unresponsive". Used the "reboot" button to try again, and same alerts came through UD Mobile. But not until a full 6 button press and power cycle did the z-wave work.

@ScottAvery what is the reason is to go to the 500 series in the 994? You might also want to check out the Coffee Shop area of the forums as there were some 994 available there a while back. Not sure if they had 500 series z-wave cards or not. Even a couple Polisy seemed to be available. UDI sent several messages about this in the last year. It's possible you have change emails since your purchase. I would suggest you log in to your account at https://www.universal-devices.com/my-account/ and sign up for the newsletters seen on the right side of the page to get future updates.

Great! That's one step in the right direction. Okay, it appears you haven't launched admin console yet. At least because there's no entry for it the process didn't actually start. You have to click on the line in the IoX Finder window. It should pop up the Admin Console (Lan) or Admin Console (Cloud) lines. Try using the "Cloud" option (even though you're local). What happens then? (as seen here - https://wiki.universal-devices.com/index.php?title=Main_Page#Quick_Start_Guides) Just rebooting doesn't format the SD card in the device. I've never attempted a reset of the ISY994, but don't think that formats the microSD either, but could be mistaken (again, I've never tried it so don't know the full extent of the reset). My expectation is that your SD card is still using the firmware that you've always had. If you want to start clean then use an unformatted card. And follow the instructions I posted above and @Michel Kohanim shared again. As you said you had issue with Telnet to the device. I don't run Win11 so not sure if either Win11 or your network might be blocking your Telnet connection somehow. That's beyond my experience and can't give any steps to troubleshoot Telnet errors. That's a search engine question waiting to happen. This belongs right here...this is fine to ask as part of your current situation. Yes, eisy works pretty much just as the ISY994 does from most users standpoint. It adds a lot of extra functionality if you have a more complex automation system you are trying to control. In my case, it works just as well as my ISY994. However, there are a few posts here of people having issues, but they're usually dealing with a lot more complex systems than it sounds like you (or I) have. The down side is since your ISY994 is reporting that you're on 5.3.0 you would not currently have a good migration path to the eisy and would need to set everything up new. I think your best bet is to fix your current issue and get the ISY994 up and running again. Then, because you're on 5.3.0, you need to update to 5.3.4 THEN you could consider if you wanted to migrate to the eisy.