srjacob

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

Done

I installed the plugin using PG3X and got the configuration screen. I configured it to my Elk, and clicked "save changes" . I still can't see anything about the elk plugin in the admin console (I had the Elk module working fine in my ISY994) and I am a newbe to eisy and polisy.

I have the M1G with the M1XEP interface. The Elk module worked perfectly on my ISY994. I did that, but the configuration in the admin console under plugins (plugin 1-the Elk) doesn't indicate these values, and doesn't seem to change the values once I come out and come back in to the plugin. Where, exactly, does the Elk plugin parameters show up in the admin console? How do I know the plugin was configured correctly.?

I successfully logged into the administrative console, and installed the Elk plugin, but I don't know how to configure it or use it in my programs. Also, my Insteon scenes are totally messed up. Steve

I just got an eisy and installed the Elk plugin. The documentation on using the Elk plugin isn't very good, and I can't figure out how to point the plugin to the Elk system. Also, there is no documentation on how to use the Elk zones and outputs in eisy programs. If someone can give me a clue on these things, I would appreciate it. Also, if someone could point me to the Elk plugin documentation, that would be great. Steve

That did it. I can now access the eisy. Now on to my other problems. My Insteon scenes are all messed up.

I rebooted the router and did that with the eisy. Nothing worked. I went to the router's DHCP table and found the IP address to be 192.168.0.151. I put the url (http://192.168.0.151:8443) into the IoX finder, and it could not find the eisy (I got an error message) like it told me to do in the wiki. How do I factory reboot and clear the eisy?

How can I reboot the eisy if I cannot get to the administrative console?