DennisC

Yes, you can follow the topic here: https://forum.universal-devices.com/forum/339-current-release-announcements/ Best practices says yes, however, if I am in a hurry, I will try opening the admin console. It will let you know if there is a mis match between firmware and UI.

No, the first choice for updating should be the button in the admin console.

Then we need to get you updated to v5.5.9. Let's try to use the multi function button for the upgrade process. But first, can you ssh into eisy? If so, ssh in (login is admin/admin) and at the prompt type: sudo tail -f /var/udx/logs/log This will open a log in the window so that upgrade progress can be monitored. Next go to eisy and press the multi function button one time. This should start the upgrade process, which you should be able to monitor by watching the log. If all goes well, once the upgrade is finished, you will need to reboot, either from the admin console or from five presses of the multi function button. You will need to allow sometime for the upgrade, but when the log stops you should be ready for the reboot. Likewise, you will need to wait for eisy to completely load (up to 15 - 20 minutes), then you should clear your Java cache (check all 3 boxes to delete files & applets) and download a new start.jnlp from this link: https://isy.universal-devices.com/start.jnlp When you run start.jnlp, it should load a new Launcher on your desktop.

What device are you using: Polisy or eisy? What is your firmware and UI version from Help - About? The latest firmware is version 5.5.9. You will not see something changing if that is the version you are on. There is a current bug that falsely displays "upgrade available" message when no new upgrade is available. It is not effecting everyone, only some. UD has identified the root cause and has fixed the bug. The fix will be in the next firmware release. Typically, when new firmware is release, UD makes a post on the board in way of announcing the upgrade.

No it is not. The process is the same for Polisy/eisy. Upgrading firmware is covered at the bottom of the wiki user guide page for eisy here: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide Upgrade Process - As of July 2022 Please see this important update (July 2022) Unless explicitly requested by Universal Devices, the SSH method of updating the eisy should be avoided. Due to recent updates to the underlying operating system, unexpected consequences are being experienced when users force a full package upgrade and update using SSH. You can simply click on the power button once and eisy will automatically try to upgrade itself. You don't have to reboot. Or, if you wish to use the Admin Console: e IoX Launcher to open the ISY Finder window. Once logged in navigate to: Configuration tab System Then click: “Upgrade Packages” This updating/upgrading process through Admin Console has been developed to handle downloading the proper packages from Universal Devices servers to update UD specific libraries and dependencies needed to keep the eisy operating efficiently and as designed. And it's covered in this post: Once logged in navigate to: Configuration System Then click: "Upgrade Packages"

Maybe I am forgetting something. When I first set up my ISY994, my lighting was imported in to my ELK M1. I don't remember if this was a manual operation, (some toggle button?) or done automatically. When I started using the Elk Node Server, all that lighting was imported back to the Node Server without user action. I don't see a way to delete these nodes, either in the Elk Node Server, or M1. In the M1, there is a column for "Show" and the description for this says " An X under "Show" means that device will be visible on the keypad and other user interfaces." I might be able to remove them from the Node Server by unchecking "Show", but never tried that, as I didn't want to break something.

Are you on Polisy/eisy? On PG3, if you go in to the node server, where the command buttons for the node server are. There should be a button to Stop the node server and then there should be a button to Delete the node server. Just make sure you select the node server in the slot that is not working. If Delete button doesn't work, I think you will need to reach out to Bob.

Make sure the battery devices are awake when you do the exclude/include procedure. Check the manual for the device, sometimes there are specific procedure for keeping the battery device awake for exclude/include.

Are you on eisy? Which version of PG3 are you running? Some versions had trouble updating/update available message. The latest version 3.1.23 for eisy was suppose to correct the issue. I haven't seen this issue on Polisy's PG3 and I am on v 3.1.18, which I think is the latest. In some instances, to get the update, reinstalling in the same slot worked. In other instances, you had to remove the node server and then reinstall. Be carful, if you do this, you will need to setup the configuration page again.

Are you able to just reinstall the node server in to the same slot? When you click on install there should be an option located about mid page to reinstall in same slot.

At the least, may be you could add a toggle to the configuration page of the node server to disable adding the Elk lighting nodes? Programing in the admin console is so much easier.

Jim, I for one would welcome the change. Have those extra lighting nodes listed under the alarm zones can be confusing, especially for my wife.

I don't use a Mac & you may be required to update Java before the Launcher will work, depending on how old your version is. You can try opening Java Control Panel and going to the security tab. There should be a section called "Exception Site List". Add the IP address of your ISY to this list and click OK. This should skip the security block for this address. If this doesn't work, your Java might be outdated.

Download and run this file and it will add the Launcher to your desktop. https://isy.universal-devices.com/start.jnlp

I believe those are two separate errors. Resetting PLM should not trigger the message you received. I would suggest checking the error log. As an aside, sign in to portal and see if ISY is on line.

I have experienced the same thing on v3.1.22, several times, that's why I repeated my comment. Yes, however, after running update packages from the admin console on eisy, you need to log in to PG3 and look for a message indicating PG3 needs to be restarted. Then you restart PG3 from the menu, upper left side. The current version of PG3 for eisy is v3.1.23, therefore, you should update. I have not experienced the login issue on the latest version of PG3.

Thanks! I sent you an email with the links. You had most of what that site had available for weather, but I found a few more scattered around that might substitute for weather conditions.

Did you try removing power from eisy, waiting a beat, and starting eisy back up?

@Javi, When time permits, would you think about adding some additional weather related icons (wind, thunderstorm, various degrees of rain [light, heavy], ect)?

If you really want to know which version you have: Identifying 300 Series Z-Wave™ By The Protruding LED The 300 series will have an LED protruding out of the rear of ISY and may have an antenna mount as well. Identifying 300 Series Z-Wave™ By Version From the Admin Console select the Z-Wave™ menu at the top of the screen. Select Z-Wave™ Version. If the version is 4.55.00 the ISY has a 300 Series Z-Wave™ dongle. If the version is 6.81.00 the ISY has a 500 Series Z-Wave™ dongle.

It's not doing any harm in staying there. Providing you migrated your portal license, or if you find a new home for your ISY, you can delete it by clicking the red X in the first column on that line. Since it is at end of life and support is due to end soon, there is no real value to it, but it's possible someone here might be interested in it.

What you are seeing is correct. The password to login after the portal login is your eisy login. If that doesn't work, make sure its not a browser cache issue by clearing your browser cache. If that doesn't work, I have found removing power from eisy, after a proper shutdown, helps.

The only other suggest I can offer is have you looked in the node server log and PG3 log for errors? IF that doesn't help, I would suggest tagging the node server developer for help.

After installing a node server, it needs to be configured in PG3. It is possible your previous configuration settings were lost in the upgrade. Check under the Configuration tab for the node server in question and compare what is required in the help text to what you have configured to insure all is correct. Did you have the admin console open during the upgrade, if so, you must close the admin console and restart it for the changes to be shown. While I don't use this node server, I found the following instructions in the readme file: Installation IMPORTANT: The latest harmony hub firmware broke access, you must manually enable xmpp for each hub in the Harmony App: https://community.logitech.com/s/question/0D55A00008D4bZ4SAJ/harmony-hub-firmware-update-fixes-vulnerabilities Connect to one of your Hubs in the Harmony App Select Menu -> Harmony Setup -> Add/Edit Devices & Activities Select Remote & Hub -> Enable XMPP Do this for every hub. Make sure your Harmony Hubs have a static IP assigned. The nodeserver can not re-find the hub if it changes IP addresses. This may be fixed in the future. Backup Your ISY in case of problems! Really, do the backup, please Go to the Polyglot Store in the UI and install. Add NodeServer in Polyglot Web Open the admin console (close and re-open if you had it open) and you should see a new node 'HarmonyController' The auto-discover should automatically run and find your hubs and add them. Verify by checking the nodeserver log. If it doesn't then Select the HarmonyController node and click the 'Discover'. While this is running you can view the nodeserver log in the Polyglot UI to see what it's doing This should find your Harmony Hubs and add them to the ISY with all devices and activities if your Harmony Hub and Polyglot are on the same subnet. If they are not, then you can manually add the hub address as described in the next section, Once all nodes are added you will need to close and re-open the admin console the new custom profile is loaded.

Did you confirm the configuration for the node server is correct in PG3. Did you try selecting the Discover button on the page in your screenshot and then close and restart admin console?