DennisC

You can start here: https://wiki.universal-devices.com/INSTEON_Signal_/_Noise_Troubleshooting https://wiki.universal-devices.com/INSTEON:_Troubleshooting_Communications_Errors

You should open a support ticket with UD before doing anything else.

Sorta sounds like the old Insteon All on event. ISY shouldn't activate devices on it's own. Plenty of info in the forum and troubleshooting wiki to dig deeper. If you are looking to update, easy is the most current and only available option.

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.