SJacobson

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.