SJacobson

Any way to get the developer to respond to my issue?

Nice try, but I have come to a different conclusion. I just would like it validated. I have been a user since the ISY99, and have come to several conclusions. These are: 1) Whatever firmware UD is using is NOT OS dependent, but a stand-alone app. They MAY have converted it to run under LINUX for the ISY994, but it still is a stand-alone app.. 2) In the ISY994, UD didn't want to support both the Elk module and PGx, so they dropped support of the Elk module and left it up to some developer to develop an Elk plugin. 3) The firmware for the ISY99 through the eisy seems to be the same code base, with additions for the new functions (such as PGx, etc.). There seem to be only minor differences between the admin console for the ISY99, and the eisy. However, the firmware for the ISY994 contains code to prevent unauthorized execution of the Elk module. 4) PGx seems to be a small module within the eisy that provides OS and library functions for the plugins, and licensing for the plugins. When it is activated, it makes contact with the server at UD that is accessible at the UD portal. It is this server that stores the plugin licenses and gives the control panel for the PGx. The PGx module in the eisy then gets it's info from the portal server. LINUX may or may not be used for the UD devices. I don't believe Unix is used at all. The eisy (and the ISY994) boot too quickly to load an OS. Linux (or Unix) is NOTHING like Windows. 5) Somewhere in the eisy there is the portal credentials. 6) I don't know how much snooping UD does with PGx. I really want decent documentation from UD.

I have PM'ed the develop on this issue. So far, no answer. Sorry-the developer of this plugin.

This is exactly what I have suspected-There is NO documentation on how the entire framework ties together. For example PG3 runs partially on the eisy, but is also must have a central database somewhere in order to keep track of licenses and plugin info. Where is all of this because it it too big to reside totally on the eisy (there are other good reasons why PG3 can't totally run on the eisy)? What I am looking for is a layout of how the entire framework ties together. You can call it the system architecture, but that is exactly what I am looking for. I have asked Michel for this, and he has ignored me. I thought perhaps someone in the forum could enlighten me.

I have attached the PG3 ELK debug + Modules log. I still have the red exclamations and shown in this topic. I am going to PM the developer to look at this forum topic. ELK_2-2-2026_30923_PM.zip

Is there any way to use the old login for eisy admin console? I am getting tired of having to put in my portal email and (very long random) password. The eisy is behind a router firewall and is inaccessible from the Internet. I see that in order to use PG3 login, i use the old eisy (ISY) password and uid.

Is there any documentation regarding the relationship between eisy, IoX, and PG3?

I thought the backup file might give the developer some insight as to the problem. The Elk is connected to the eisy. All the Elk-driven programs in the eisy work. The only errors I see pretain to some wireless Elk devices where the batteries are dead. I know about these. It is a good way to know if the eisy plugin is connecting with the Elk. Those errors are showing up in the PG3 log. When I get the exclamation problem resolved, I will replace the batteries in those devices. ALL THE DEVICES are showing up with red exclamation marks I wish the developer of the Elk plugin would respond. Steve

I get red exclamation marks for the Elk nodes, even though the eisy-Elk connection is made, and the Elk triggered programs seem to work. What is going on? Elk log and eisy logs and eisy config are attached as zip files eisy Ver: 6.0.4 PG3 Ver: 3.10.5 Plugin ver: (updated) ELK_2-1-2026_90034_AM.zip IoX-Backup.v6.0.4__Sun 2026.02.01 09.08.35 AM.zip ISY Error Log.v6.0.4__Sun 2026.02.01 09.10.54 AM.txt ISY Log.v6.0.4__Sun 2026.02.01 09.10.44 AM.txt

Could you please answer my question. Lack of support for this plugin is troubling.

Could the developer of the plugin please answer me!

I could telnet into the ISY994, but they seem to have removed all of the Unix commands except LS. THis was a dead end. I tried to create a program to access the Elk, and when I tried to save it, I got the attached error message. Does anyone know what this means?

Please reread my last post. I backed up the SD card using Macrium Reflect (because I don't have a backup to this ISY994 and I don't know how long this SD card will last). I then wrote the backed up sd card to another sd card, and put it IN THE SAME ISY994. All my programs disappeared. I then restored the configuration of the SAME ISY. Anyway, I am just trying to find out why my programs disappeared on my working ISY. I suspect it is because of the write error (as shown in the attachment). If I could somehow telnet into the ISY, I could probably figure out the problem, but I can't seem too, unless some kind soul tells me how. UD simply won't help me.

Of course it is a Unix computer, just like the eisy. The eisy is just new hardware, same software. I did a file list of the ISY SD card on my Windows machine, and it's Unix. UD didn't rewrite their software just for the eisy (they may have recompiled it, though). I tried to telnet into the ISY using PuTTY, but the telnet must have been disabled. I know enough about UNIX to be dangerous, having worked with the Raspberry Pi. All I am really trying to do is get the Elk module over to my spare ISY. UD won't do anything with the ISY, so I need another way to do it Anyway, I am just trying to find out why my programs disappeared on my working ISY. I suspect it is because of the write error (as shown in the attachment). If I could somehow telnet into the ISY, I could probably figure out the problem, but I can't seem too, unless some kind soul tells me how. UD simply won't help me.

This is a long story. I have two ISY994s and and eisy. One ISY has the Elk module and controls (through the Elk) an electronic gate (via an M1KAM moduole). The ISY and the Elk module words great and very reliable. I decided I needed a backup to the ISY and Elk module, and purchased an eisy and got the Elk plugin. Since trying to migrate, I have encountered numerous problems, particularly with the Elk plugin. I am only keeping the ISY as a spare, since I am highly dependent on the gate and the Elk alarm (I have spare boards for these). Anyway, I took the SD card from the ISY and saved an image to the hard disk on my computer (using Macrium Reflect). I then wrote that image to a micro SD card (also using Macrium Reflect, and plugged it in to the ISY, and rebooted the ISY, and the control panel came up and it looks like all the Insteon devices are there, and the Elk module is there also, but my programs aren't there. I tried to restore the ISY from a recent backup (the same one that I loaded into the eisy), and the Insteon devices were there and the proper configuration was there, but the programs were not-the programs were missing. When the ISY restore tried to load the programs, I got the attached error (screenshot). How do I fix this error, and get my programs to come up? My entire purpose is to use the second ISY as a backup to the operational one, and not use it until the first operational one dies. However, it seems that UD has somehow configured their software to the MAC address of the ISY, and the cloned micro SD card will boot in the backup ISY, but the control panel won't come up (and the IoX finder won't find it, either). Is there a way to telnet into the ISY to change the UD software so it will run on the backup ISY? I am not very knowledgable in Unix, and don't really know my way around in it. I do know Windows really well, however. I have done some work with the Raspberry Pi. I am getting really tired of the problems with the eisy and the Elk plugin, and getting terrible support for the Elk plugin. I can use the eisy elsewhere, so it isn't a total loss. Steve

Please answer my question about the left-pointing arrows, and when do you think the PyISY error will be fixed?

If the plugin does not poll the Elk, how does it find the state changes in the inputs and output? Also, why are there polling parameters in the PG3X configuration page of the plugin? Also, why does rebooting the eisy solve the problem (for a few days, anyway)? I changed the log parameters as you suggested. Again, this worked flawlessly on the ISY994 with the Elk module, so something is amiss. Steve

OK. This is the third time this is happened. I have the Elk control an electronic gate via an M1Kam module. It normally works fine, except on several occasions. Today was one of them, and it was raining. The symptoms are: The gate doesn't open either through the Elk or the remote control, which directly toggles the gate controller. Rebooting the eisy always frees up the problem. What seems to be happening is that the Elk plugin is polling the Elk all the time, keeping the Elk from doing it's job and causing the M1KAM to prevent the gate from opening. I never had this happen with the ISY994 and the Elk module. I don't know where the problem is, so I have put this on the Elk forum and submitted a ticket. I have attached a zip file containing the error logs from both the eisy and the PG3. I hope someone can figure this out soon, or I will be putting back my old ISY994. I would PM the developer of the Elk plugin, but I don't know how to PM the developer. Steve eisy-Elk troubles.zip

You said it was a problem with the shared library PyISY, so when will it be fixed? Also, I would like to know why my relay inputs (from an M1XIN and the M1KAM) don't show up with an arrow pointing to the right. I am not shouting, just frustrated. I expect software to be well-documented, and this isn't. Eisy and this plugin are giving me more problems than the ISY994 and the Elk module. So far, I have had to reboot the eisy twice to get the Elk to control my electronic gate (which is controlled by the Elk and a remote M1KAM). I never had to do that with the ISY994 and Elk module. It just worked.

But I have input contact sensors with no arrow in front of them. Why are these different?

So now what do the arrows mean? Why do I even get the arrows? What is the permanent fix? I NEVER HAD THIS PROBLEM WITH THE ISY994 AND THE ELK MODULE.

The red arrows changed to left pointing arrows. See uploaded image.

More log files. There are NO error logs. ELK_10-24-2025_104842_PM.zip

When I restart the plugin, the errors (?) do NOT get cleared. I uploaded the config page error (the only one I know about), but the forum didn't accept it. Please tell me EXACTLY where I can find the PG3X page that gives the errors. I have no idea what you are referring too. I have been running the old ISY994 with the Elk module for years, without any problems.