HELP! Migrating from an ISY994 to an eisy.

[srjacob]

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.

[DennisC]

The 994 should have been powered down when you started to restore your backup on eisy.

You should be following these instructions:

https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

 

[srjacob]

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.

[apostolakisl]

I don't see where it would be a problem to have the 994 on and no plm attached in an insteon network that has an eisy running as well. I would shut down polyglot if you have that running on rpi and I would disable any programs using network resources and I would change the elk module credentials so it can't mess with your elk whilst you configure the eisy.   Or you could isolate the 994 by plugging it into another network. Easy way would be if you have a spare router. Plug a computer and isy into it and nothing else and then it can't mess with anything. 

[srjacob]

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.

 

[lilyoyo1]

14 hours ago, srjacob said:

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.

Are you sure? Part of the instructions says for you to plug your PLM into your eisy. With you leaving the plm on the isy, the EISY cannot read your insteon network. 

[Brian H]

It also has to be a USB 2413U or the 2413S from the ISY9941 and the USB to serial adapter cable. With the special wiring sold by UDI.

 

[apostolakisl]

9 hours ago, srjacob said:

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.

 

 

Eisy won't change anything on any devices unless you tell it to.  Scenes are all written on the plm and on the devices.  ISY keeps track of what is supposed to be written in those links so you can restore the devices.  But if you never tell it to restore a device/plm, it won't write anything and they will stay the same.  In short, if you don't tell it to restore the plm or restore devices, your insteon network won't be changed.

[srjacob]

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.

[apostolakisl]

15 minutes ago, srjacob said:

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.

You need to plug the plm into eisy or it will give you errors.  The whole point of what I just wrote is that eisy won't change anything in the network unless you tell it to.  Just plugging it in won't change your links.