DennisC

I must be missing something, where are you getting the following from: _33_3 & _72_3 Start simple using a program and an email notification so you can right click on the program, select run then and have a notification sent. Y email. Once you get the right output, then transfer the correct node address to your cvs output. Does the following work: ${sys.node.ZY014_143.TPW},${sys.node.ZY014_143.CV}

If you type the following into a browser window, click through the warning and then enter user name & password, you get a page that gives you all of the property id's for that node (if the node address is written correctly (the example is based on using eisy via https, with a node address of n001_81668 (from node server, update it for other type of nodes): https://xxx.xxx.x.xxx:8443/rest/nodes/n001_81668

I think you will need to submit a help ticket with UD and get Chris involved in this. There is one more thing you can try: Go to the top menu and select ZWave - Synchronize - New & Deleted with Interview.

I apologize, I misunderstood the issue and deleted my previous post.

I misunderstood the issue and deleted my previous post.

Try right clicking on device and run ZWave - Synchronize with Interview. Restart admin console and recheck. If that doesn't work, then try ZWave - Synchronize without Interview. Restart admin console and recheck. Edit: Before restarting admin console, let the synchronization finish. You can monitor this in Event Viewer set at level 3.

Yes, you can have a folder inside or under another folder. Click on the parent folder and at the bottom of the left hand tree, select make folder. The new folder will be under the folder you selected. Is that what you were trying to do?

If you are accessing your ISY locally, you should be using the Launcher. You can get it by downloading start.jnlp from the link below. Click on start.jnlp and it will place the Launcher on your desktop. start.jnlp https://isy.universal-devices.com/start.jnlp Instructions: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop If you are still having a problem after that, try the troubleshooting steps below: Admin Console Closes Automatically This is usually related to firewall software on your computer and especially with AVAST or AVG (including MAC). Two solutions: Use https (instead of http) to connect to your ISY Configure Your Firewall Software Admin Console Minimized/Invisible and Cannot be Restored This is usually related Admin Console state files not being updated properly and especially in case of multi monitors. All you need to do is to find the following files in Java temp directory (on Windows: c:\Users\[Username]\AppData\Local\Temp) and delete them. Or, you can simply search the computer for udi_*.state or ud_*.state file patterns: ud_finder.state udi_finder.state udi_frame.state udi_launcher.state udi_pgm.state udi_tree.state Be aware that the ISY is at end of life and will have no new development. Shortly, free support for it will end. The latest device is eisy and you may want to read up about it from UD's store page. You might want to consider an upgrade. When you get in to your ISY, I would suggest you take a fresh backup. So, not sure what firmware version you are on, but there has been a lot of development going on. You might want to read up.

The admin console was not meant to be left open for monitoring. It was designed to do a task and then be closed. Having said that, what UD hardware are you using and what is the firmware and UI versions? If you are running on either Polisy or eisy, the latest version is 5.5.9. Some versions before that had a bug that would give error messages about open sockets not being closed. If you are not on latest firmware, you should update.

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.