DennisC

If I understand what you want to do, all you need to do is start the IoX finder two times. The first time you start it, select your ISY994 unit and open the admin console. Start another instance of IoX finder and this time select eisy and login to the admin console. I do this all the time and everything works fine. As for migrating your programs, they should have come over during the migration process if the procedure was followed correctly. One thing of note, the migration backup is different than a normal ISY backup, so be sure to follow the migration instructions for making a migration backup.

I'm really confused, your saying you don't have zones but they are showing in your screen shot of the admin console. There are two areas showing, Basement & First Floor and both have zones showing. For example, Basement Area indicates no active alarm, Basement Mtn Ex Rm indicates Normal, Basement Mtn to Strs indicates violated, ect. If you click on one of the zones in the left hand tree, you will see more details about each zone. What is the issue? Your log now shows an active user code so you must have corrected something. Not sure what the screenshot of the Network Resource is about, why would you have a Network Resource to what appears to be Elk M1XEP?

Before downloading the debug log, make sure to go to log page, change to debug, and restart plugin. Wait several minutes before downloading log.

You can not have 2 connections open at the same time and have eisy update or issue commands. Only 1 connection can be used at a time with eisy. There is nothing difficult about it. Your previous post said the user code was incorrect. Now you are saying it was correct? Until you get the configuration correct, you will continue to have difficulty. Your previous Elk plugin log showed there was no working user code set. To move forward, post an updated Elk plugin debug log, screenshot of your plugin configuration, screenshot of Elk plugin Nodes page, and a screenshot of your eisy admin console Main tab, Network tree.

I apologize but I am still not clear on what you can not access. Are you having difficulty with IoX Launcher or opening admin console? Sounds like you first need to factory reset your dad's ISY, then restore your back up.

I PG3x, Dashboard, Elk, Configuration tab. All those settings need to be correct for your installation. This includes an active working user code. After updating be sure to hit save. That should be all you need to do now to get connected. Regardless to what Elk has indicated, currently the plugin to Elk can only be 1 connection. Although, that might change with the new interface UD is working on. Remember, for the changes to take affect, the admin console must be closed and opened after PG3x is updated.

Could you provide some additional information and clarity? What equipment do you have and what is it you are trying to do?

Correct My comment was intended to make sure you didn't have another connection open while troubleshooting this one. With the plugin, only one connection can be established at a time. As for your log, previous attempts up to around 17:00's were not connecting. Whatever change you made after that, as of 23:02, the plugin made a connection with Elk M1XEP - that's good. While the nodes appear to be in the log, the values are empty. From the Elk Dashboard within pg3x, to the left of the Configuration tab, there is a "Nodes" tab. Is there a number next to "Nodes"? Click on the Nodes tab and you should be seeing some node names. Are there any there? Within the admin console Main tab, under Network, do you see "Area 1" and "Elk Controller"? I see this in the log: 2025-07-13 23:09:50.865 ELK-82381 udi_interface INFO Controller:callback: ELK Controller: element=0 'ElkM1' real_time_clock:None elkm1_version:5.3.18 xep_version:2.0.48 remote_programming_status:0 system_trouble_status: temperature_units:None user_code_length:None type=<class 'elkm1_lib.panel.Panel'> cs={'elkm1_version': '5.3.18', 'xep_version': '2.0.48'} Back on the Configuration tab for the Elk plugin, are you still showing a value for user_code? If so, is the user code you entered here programmed in the Elk and can you use it to arm/disarm at the keypad?

You can only be in one of these at a time. Elk doesn't support more than 1 connection. Elk has nothing to do with UD or their plugins. That's because you are in the wrong location. You need to be on the Elk Plugin page - Log - Debug - Restart. Take a look at the attached mark up. Elk.pdf We will not be able to move forward without the Elk Plugin Debug log. If there is not an obvious error, you will need to tag the Elk plugin developer for his input. But first, we need to see what is in the log. Did you confirm the IP address of Elk M1XEP is correct? Also, go in to the M1XEP and on the TCP/IP tab, make sure there is a check mark next to "Enable Non-Secure Port" and the port is set to 2101.

Just a thought, since there can only be 1 connection to the Elk, is your ISY994 powered down?

While you are making changes to the Plugin, the admin console needs to be closed. If it is opened while you make changes, you need to close it and reopen it to see the changes. Under host, is that the IP address of your Elk M1XEP? The port is correctly added with :2101. just like you have. If you have more then 1 area, try separating them with a comma, instead of a dash to see if it makes a difference. Like this: 1,2 Are you using 100 outputs? Typically, you only want to display what you are using. As a test, try adding just a few with comma's. Like this: 1,2,3 Afterward, hit Save Changes. Next, go to Log tab and change the drop down to debug instead of what it is on now (possible Info?). Then while staying on the page, hit restart from the top menu. Log should start populating and you can check for errors. Also, very important, you can only make 1 connection to Elk M1EXP at a time. Therefore, you can not have anything else (like ElkRP2) connected at same time.

Post a screenshot of your configuration settings from pg3x.

Did you read my reply in your other post? All configuration is done in Polyglot, PH3x, not admin console. After changes in PH3x you need to close and then reopen admin console.

You don't install any plugin from the admin console. Plugins are installed and managed from PG3x. Is that what you did? The Elk plugin has extensive documentation and examples. If you installed the plugin correctly, go to PG3x, click on Dashboard from the top menu, followed by Configuration. Instructions for setting the plugin up are there on the Configuration tab. You can also go to Plugins Store from the main menu, select Elk Plugin, followed by "More Info". Here you will find details and examples. If you haven't installed the plugin in this manner, or can't access PG3x, go to UD's wiki eisy manual and there are instructions there.

Hold on a minute. Your using http, with port 8443, it should be https. Try: https://192.168.0.151:8443

Use the multi- function button the front of the unit. Check the user guide for # of presses.

You would be surprised, stranger things have happened. I would suggest rebooting your router and after it starts up, reboot eisy. If you still have trouble after that, go to Universal Devices wiki page and look at their troubleshooting page. There is a section there about troubleshooting when IoX can't find eisy/Polisy/ISY.

If adding the IP address manually in IoX finder doesn't work, you can also try adding: https://eisy.local:8443/desc

Go to my first response to you, I attached a link with the migration instructions. Static IP addresses are no longer supported because of heavy support load when problems appear. However, you can still fix the IP address by using DHCP reservation in your router, which is a better way of fixing the IP address over static IP's. When you say website, are you referring to PG3 (Polyglot)? Have you registered with the portal and approved it in eisy? Instructions are in the document I linked in my first post. All programs may need to be opened and saved after migrating, along with any network resources. Follow instructions in migration document above. I would suggest getting these issues cleared up before worrying about scenes. Also, changing from Elk module to Elk plugging, all Elk addresses will need to be updated.

Hundreds of us have managed to migrate without issues. Maybe it is you who are misunderstanding the instructions? As I said in my post above, if you don't provide details no one here can begin to assist you. You didn't answer my questions from above, are you following the migration instructions? What firmware on the 994 are you migrating from? What specific issues are you having?

Hard to help without you providing details about what difficulties you are having. For starters are you following the instructions here: https://wiki.universal-devices.com/Eisy:User_Guide#Migration Be aware, to migrate from ISY994 to eisy, there are some minimum firmware requirements for the 994 that you must meet. Also, Elk module has been depreciated, you will need to move to the Elk plugin.

Verify the easy IP address with your router. Then click on the add button in the Launcher and add the IP address manually.

I would still suggest trying another power supply, and not POE.

In the meantime, you might want to try a new power supply.

As far as we know, eisy is it for the time being. It's a matter of what you are comfortable with. But I would suggest that you obtain a new USB PLM, to have as a spare just in case. Download a copy of the migration procedure from the wiki and read through it several times. Be sure to ask questions about anything that is not clear before hand. You didn't mention what firmware you are currently running. There are minimum requirements for migrating to eisy, so you might need to do some firmware upgrades first.