DennisC

Try reading through the ISY Cookbook. While written for the ISY994, the programming concepts are the same. If using node servers, just look in your node server for the proper node address and use that. http://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf

Are you talking about Elk Module or Elk node server? The Elk Model is most likely not supported in v5.7.0.

While I don't use Mac, it appears like there is a file association issue? Try clearing your Java cache, checking all 3 boxes and download a new start.jnlp from here: https://isy.universal-devices.com/start.jnlp After the download, run start.jnlp and a new IoX Launcher should appear on your desktop. Depending on which version of Mac you are running, there are a few troubleshooting steps in the wiki.

You need to use port 2101. Since you appear to still be having trouble getting everything to work, can I suggest you disable importing lights for now and concentrate on getting your Elk system in to your system. Where are you seeing this? It is recommended to set up a new user code in Elk to use with the node server. This can be done from the Elk programming software, ElkRP2, or from some keypads. Have you done that and tested the user cade to be sure it works? Once you have a user code that works with your Elk, enter the user code in the node server configuration tab. Save the page, restart the node server while watching the log. You should see the node server start up, connect to Elk, and add the nodes. After the nodes have been added, then start the admin console. If the admin console was open when starting the node server, you must restart the admin console. If this doesn't work for you, please post some screenshots.

Try shutting down eisy, pulling the plug for a few minutes, then starting it up again. You don't mention what firmware you are on, but if you haven't run upgrade packages from the Configuration tab, go ahead and do that to ensure you are on the latest firmware. You may need to reboot several times to get everything running. After that, you should find PG3x at your eisy IP address, as follows: xxx.xxx.x.xxx:3000. By the way, since you mentioned Polyglot, you probably already know that you will need to purchase the Elk node server to use with eisy. The Elk module doesn't work with eisy.

You could create a variable for each device to record the state and then set the variable init vale to maintain it over a power outage. Then write a start up program to restore those states.

In my opinion, your best bet would be to copy your programs to the clipboard and paste them to a text document, then Factor reset your Zwave devices and add them to eisy. When you add the Zwave dongle to eisy, the Zwave naming convention changes, hence each Zwave address will change requiring manual intervention anyway. Having a text copy of each program should simplify creating the programs on eisy. I feel this process will be cleaner and less painful then troubleshooting something that may or may not work. Not even sure if transferring controller is an option in eisy?

You can use a keypad or ElkRp2 to add a new user. Check the Elk manual for exactly how to do it. The errors might be because you are lacking an authorized user, but I'm not sure. You can also try rebooting eisy. Suggest you get a proper user programmed before you start chasing something else.

Have you checked the node server log for errors? The user code is not reansom, you must program the Elk for a new user with the code you want to use. Did you do this?

Wording & layout could be better, but I'm satisfied as long as it all works. lol

Go to the Purchases tab, click on the node server you need to update. Under Purchases, there should e an update button.

These are the important fields to get basic data in the admin console: Set temperature_unit to F or C Set host to the host or ip address and port, e.g. 192.168.1.15:2101 Set user_code, suggested to create a unique usercode for this NodeServer Set areas to the range of areas you would like to include Set outputs to the range of outputs to include A range can be comma separated to include just those numbers, or separated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses. Have you entered the correct IP address and port? Note, you can not use the secure port. You can only have one device connected to Elk at a time. Are you in ElkRP2 or anything else? Have you entered a valid user code? Did you set the area to your existing Elk area? Did you restart the admin console? If the above doesn't help you, we will need to see your configuration details.

It is recommended that you create a new user code in Elk for use by the Elk node server & UD Mobile. Remember, you can only have one active connection to the Elk at a time. Therefore, you can not be connected with say Elk RP2 and have the node server via the admin console respond. You would need to exit ElkRP2 first. You can access more information and/or the instructions for any node server before purchasing/installing from the node server store. Click on the name of the node server, followed by More Info button.

For starters, here is a link to the Elk Node Server documentation: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md You can access the node server configuration page by going to the IP address of your eisy and adding :3000, which would be the port number. Sign in using your admin console credentials and click on the Elk node server from the dashboard, followed by Configuration tab. You should see the following instructions: To Configure the ELK Nodeserver Custom Configuration Parameters Set temperature_unit to F or C Set host to the host or ip address and port, e.g. 192.168.1.15:2101 Set user_code, suggested to create a unique usercode for this NodeServer Set areas to the range of areas you would like to include Set outputs to the range of outputs to include Set change_node_names to true makes ELK the source of node names so if they are changed then ISY names will be changed to match. Set light_method to ELKID to check for ELKID=n on ISY Nodes, or ELKNAME to check if the Elk Light Name matches and ISY Node name or address. ELKALL This creates an ISY Light node for every definded Light node on the ELk ELKID This works by right-clicking on a node in the ISY and adding a note with "ELKID=n" where n is a unique integer After changing to ELKID method, you must wait until you see "Export Completed" warning message in the Log. Then click on the "export" like provided below If you change an ELKID on a node then you must restart the nodeserver for it to be seen. ELKNAME This attempts to match the name of an ISY Node with the Name of an ELK Light node to control. The table on this page will show the matches. Note that if you remove an Area, it will not be removed from the ISY or Polyglot. This is intentional just in case it's an accident and your scenes or programs reference the nodes. If you change light_method from ELKALL to another method, the Light nodes will not be removed. You can go to the Nodes Page in the Polyglot UI and delete leftover nodes from changing ranges or light_method using the X to the right of the node. Ranges A range can be comma seperated to include just those numbers, or seperated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses. Once you get the configuration set up, you need to restart the admin console if it was open. Afterwards, your Elk should appear in the admin console. Next, go to programs and update them for the new node names. There are examples in the help document. If you have further questions, it is best to start a new topic.

I'm using Ryse, which as a node server for it. Ryse sells a motor that you can hook up to most shades.

Download and run a fresh copy of start.jnlp. Make sure you download a fresh copy.

Do you have a portal account to try?

Are you running on a Windows machine or a Mac machine? Do you have a UD portal account? If so, try selecting "cloud" and login with your portal credentials. Also, if you are running anti virus software, try disabling it.

Try rebooting your computer and then attempt to delete the state file without trying to open the admin console. Next try adding Java memory per my previous post. After deleting all of the state files, clear Java cache (all 3 boxes), download new start jnlp from UD sites and run it.

Try deleting state files: https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored Also, check Java memory: Admin Console is very slow or hangs If the admin console is slow to respond, it is likely you need to increase the amount of memory allocated to the Java runtime (JRE). Open the Java Control Panel, select Java tab, press View button, then add or modify the Runtime Parameter -Xmx to the following: -Xmx512m Press Ok to close the window, then Press Apply to save the changes

Make sure the PLM is not plugged in to a UPS or surge protector, as these can cause communication issues.

If you tap on the round circle in the upper left corner of the tile, it should activate. For example, tapping the circle for kitchen lights should turn them on. Tap the circle again should turn lights off. Is that what you are looking for?

Maybe try power cycling and if needed reinstall node server after the restart?

There is no easy way to partially upgrade, however, UD does have a migration path depending on your current system and firmware. When you do migrate, be sure to follow the directions exactly. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

@Excalibur78 FYI, you are running on an old platform that is no longer developed or supported. You should consider upgrading to the current device, eisy. https://www.universal-devices.com/eisy/