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

The ISY994i isn't a unix computer like the eisy. You can't telnet or ssh into it. Yes, the "software id" of the UDI controllers is their MAC address. You won't be able to change that. For a ISy994i to ISY994i migration, have you tried doing a backup and restore from the Admin Console? That's the usual way to move things (programs) over to a spare unit. But you cannot move optional modules and the unit ID that way.

19 minutes ago, Guy Lavoie said:

The ISY994i isn't a unix computer like the eisy. You can't telnet or ssh into it. Yes, the "software id" of the UDI controllers is their MAC address. You won't be able to change that. For a ISy994i to ISY994i migration, have you tried doing a backup and restore from the Admin Console? That's the usual way to move things (programs) over to a spare unit. But you cannot move optional modules and the unit ID that way.

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.

Edited Friday at 03:17 PM4 days by SJacobson
Adding text.

Added plugins that you purchased for an ISY994i. Are connected ISY994i's UUID number. So getting it moved maybe very hard or not possible at all.

Or are you just using the basic Elk support in the firmware and not the purchased ELK Security plug in module?

From the manual:

ELK Security Module

While the ISY does include some ELK integration built-in, it is fairly limited in that most of

the integration must come from the ELK side. For example, you can write a program on the

ELK to turn a light on through the ISY, but you cannot write an ISY program that turns a

light on based on the state of an ELK resource.

The ELK Security Module changes that, fully integrating the ELK with the ISY allowing you

to use the ELK’s available resources in your ISY programs.

The list and state of available ELK resources can be found in the main ELK tab in the Admin

Console.

Edited Friday at 11:27 PM4 days by Brian H

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.

I have a suggested approach based on me having copied web pages onto my ISY994i when I used Benoit's HAD (Home Automation Dashboard). Had some notes I kept, but it was a lot of hair ago. Also I had to move a corrupted file back on my ISY at some point in time

This caveat is to say I haven't had a 994 in a long time and haven't used PUTTY or a telnet client in years.

So some info and things to try but I'm not sure this will work exactly:

• On the SD card, navigate to the /CONF directory.

• Look for files named programs.* Ideally:

  • programs.xml

  • programs.ndx

  • programs.bak (if present)

These contain your ISY program definitions.

• Install Putty Telnet on your PC

• Connect via putty to your ISY ip address via port 23

  Look and see if program files are there by entering:

• ls /CONF

• Confirm if this is there: programs.xml

• Use a file transfer tool that supports Telnet file copy (e.g., pscp if using PuTTY or scp if SSH is enabled).

• Copy the programs.xml and programs.ndx from your PC’s SD card to the ISY’s /CONF directory:

• Fuzzy on this part, maybe someone else can fill in. The DOS file reference SDCARD will be your name for the SD Card

• pscp C:\SDCARD\CONF\programs.xml admin@[ISY_IP_ADDRESS]:/CONF/programs.xml pscp C:\SDCARD\CONF\programs.ndx admin@[ISY_IP_ADDRESS]:/CONF/programs.ndx

A few last caveats

• If I have the above putty/scp syntax wrong, there will be documentation on the web about putty or scp and moving files

• I'm not sure how the UUID plays with these files, but let's see if you can get any where with the above.

• If the files on the card are corrupted, the ISY probably is not restoring them for that reason and 'force copying' them using the above steps will likely give unpredictable results.

Again this is not step by step but gets you something to look at and try

Edited Saturday at 07:54 PM3 days by paulbates

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?