srjacob

If it were that easy, I would have discovered it by now. I don't see keypads, but I see the keypad location, but I can't expand it. See attached image. And yes, I restarted the plugin and the eisy. In any event, I created and named two outputs in RP2 that were set on when the F4 and F5 buttons on the keypad were pressed. Unfortunately, these two outputs don't show up in the eisy. I set the two outputs (by the output numbers), but it doesn't seem to work. I use the outputs as flags (I am an old programmer) for programs within the Elk and the 994. Steve

I am really a newbe to the eisy, but not to the ISY994. I am trying to migrate programs that use the Elk Module to the Elk Plugin. I have successfully accessed my elk zones and outputs, but I have no idea how to access the function keys on the Elk Keypad. In fact, I can't even see the Elk Keypad in my Elk Controller list. I use the F4 and F5 on a particular keypad to permanently open and close an electronic gate that is controlled by the Elk. The documentation on the Elk Plugin offers no insight into this.

That is correct, I don't want the eisy to modify the network. That's why I haven't put the PLM on the eisy. I just want to find out if my migration is correct. I need to convert the programs that communicate with the Elk.

The PLM is still attached to the 994, and everything works fine, including the Elk interaction. I am concerned about several things: 1) the scenes in the admin console for the 994 seem to be using the new version of the admin console, not the version that I am used to for that device. The copyright date goes to 2025, and the scenes have an Action field in them, which they origionally didn't have. 2) The admin console scenes in the eisy (when migrated) have an action field of off, which the action field in the 994 was on. Almost every scene has this issue. 3) my concern is that if I put the PLM on the eisy, my scenes will be screwed up, and I don't want that. 4) I wonder if I did the migration correctly. If not, please tell me what I forgot.

I did follow the instructions I am NOT migrating Zwave, just Insteon. Therefore, the instructions don't indicate that I have to shut down the 994. Having both the eisy and the 994 up at the same time allows me to migrate the programs that use the Elk module to the Elk plugin. I have about 30 programs that use the Elk because the Elks controls an electronic gate.

I am trying to migrate from an ISY994 (Firmware Insteon V5.0.16C) to a eisy (firmware 5.9.1) and am running into a problem with Insteon scenes. What I did was do a file->Backup ISY from the admin console of the ISY994 and restored that file using file->restore IOX (the WIKI isn't really clear on this). What has happened is that even though the devices seems to come through, the scenes have an action filed (that the 994 never had), and the admin consoles for both the 994 and the eisy seem to be the same. I have to migrate the programs that use the Elk module to the eisy using the Elk plugin), and the scenes seem to be messed up. Did I do the migration properly, and somehow did UD slip a new admin console for my 994? I am running the 994 and the eisy on the same network (they have different IP addresses). The PLM is still on the 994, and the Insteon lighting network and the Elk communication with the 994 seems to work fine.. I am hesitent to move the PLM to the eisy because I don't want my Insteon scenes to be messed up and I still have to convert the programs that use the Elk plugin.

That worked fine. The programs did not come over properly because I used the Elk module on the 994 and the Elk plugin on the eisy. That difference means I have to convert the programs that use the Elk. The programs that only used Insteon came over fine. What didn't come over fine was the scenes. I have a separate post on that. The 994 works perfectly and I hated to upgrade to the eisy.

I recently migrated to eisyfrom ISY994. When I migrated my 994 to an eisy, I did a backup on the 994, and loaded that into the eisy (as per the instructions). Unfortunately, the scenes got messed up. I have attached a screenshot from the 994 and the migrated eisy scene. Same scene. What is going on with the migration? I should note that the PLM that is on the 994 has NOT moved. I don't want my Insteon scenes to be messed up and I still have to convert the programs that use the old Elk module to the new Elk plugin.

Is there any way to run multiple copies of IoX (one for an operational ISY994 and the other for an eisy)? I am trying to migrate programs from the Elk Module in the 994 to the Elk plugin on the eisy.

If somebody had told me the Elk stuff was intermixed with the network stuff, I would have looked therre. I think it is all here, and I can work with it. Now on to why the scenes are messed up. I have attached a screenshot. I don't know why there is Action, and what is the Default. When used the admin console for the 994, I get basically the same thing. The original admin console showed the scene correctly. I have not moved the eisy to the PLM yet. I wanted to make sure the scenes were correct and the programs that used the Elk module were modified. Does anyone know what is going on with the scenes, and why I am getting the same admin console for both the 994 and the eisy?

My configuration must be correct. I am getting the outputs, just not the zones. Yes, at one time my user code was not correct. I created a new one, and it works fine with M1ToGo. The debug log is attached, and the screenshot of the other things you asked for. ELK_7-14-2025_124815_PM.zip

I did all that with the configuration. It was already correct. I don't see anything relating to the Elk in the eisy Admin console. I think you misunderstand regarding simultaneous connections. What Elk is telling me is that I can have up to 30 simultaneous connections to the M1XEP (but they have only tested 4). That means I can 1 connection via the eisy, and 3 more with M1ToGo. If the M1 is in programming mode (via RP2), the other connections are blocked. I am still trying to figure out why my zones don't show up in the nodes list, and where in the eisy admin console the Elk stuff shows up. With the Elk module for the 994, it was easy. The eisy seems much more difficult.

OK. Yesterday I said I would email Elk and ask them "how many simultaneous connections can the XEP make"? Here is their reply from Brad Weeks: Now you know. My answers are in BOLD At Nodes from Elk plugin.txt

I have attached the Elk Plugin Debug Log. The restart you spoke of restarts the plugin, not the log. Anyway, I didn't see any errors. And yes, the IP address is correct and the non-secure port is enabled. And yes, I can run the 994 and M1ToGo simultaneously. I do it all the time. I didn't know you couldn't. My question to Elk had nothing to do with the plugin, but I asked them how many simultaneously connections can the XEP support. I'll probably get the answer tomorrow. ELK_7-13-2025_111019_PM.zip

I believe there can be only one programming connection to the XEP (thru RP2), but multiple non-programming connections. I often go into my M1 system through both the 994 and M1ToGo. I tried 1-2 and 1,2 for my areas. It didn't seem to make any difference. I have posed this question to Elk Technical Support. I have around 70 outputs. Some of these are real outputs (I control a gate using an M1KAM) and some are used as program flags. This is why I specified 100 outputs. If I make Elk programming changes later, I don't want to go back and reconfigure the plugin. In any case, I have disconnected the 994. Makes no difference. I configured the log for debug like you suggested. There was no RESTART on the top menu, you I am attaching the entire log. Steve Debug log file.txt