davefred99 Posted May 22, 2013 Posted May 22, 2013 I have an existing ELK/Insteon system that has about 30 devices already in my Elk Controller. I came across a deal on a used 99pro with the elk module already installed. I am just getting started with elk/issy integration and was wondering if it possible to export my My Insteon Lighting from the ELK and import it into the ISY. I know the common approach is to add them all to the Issy first and export to the Elk but I was hoping to save a little time and also be able to keep my existing rules set up in the ELK until I get more acquainted with how the Issy works. I am not looking forward to starting all over as my system has been up and running trouble free for more than 3 years now but always wanted to add the Issy for better lighting and integration.
LeeG Posted May 22, 2013 Posted May 22, 2013 I strongly suggest not buying the 99i. Do to code memory constraints 3.3.10 is the last ISY image that will install on a 99i. Start with a 994i. 4.0.4 RC1 may be the next official release. None of the 4.0.x images can be installed on the 99i nor anything that comes after 4.0.4.
davefred99 Posted May 22, 2013 Author Posted May 22, 2013 I strongly suggest not buying the 99i. Do to code memory constraints 3.3.10 is the last ISY image that will install on a 99i. Start with a 994i. 4.0.4 RC1 may be the next official release. None of the 4.0.x images can be installed on the 99i nor anything that comes after 4.0.4. To late I already purchased it but it was really cheap, it is a 99pro and came with all the modules and a PLM. I knew what I was getting and if it works out OK will upgrade later to a 994i. I have always been pretty happy with the Elk controller for my needs but the Issy seems to be a little better and more efficient . I really do not see any must have feature in the new models accept for possible Zwave integration in the future. My needs are fairly simple as I generally set and forget my system as it helps with the WAF. thanks for the warning anyways.
LeeG Posted May 22, 2013 Posted May 22, 2013 It is not the features you see that will bite you. So long as new Insteon devices (even of the existing type) are not added the 99i should be fine. I'm sorry I do not know the answer to the original question. I do not use ELK. Normally things go the other way. An existing ISY configuration is transferred to the ELK.
gatchel Posted May 22, 2013 Posted May 22, 2013 It is not the features you see that will bite you. So long as new Insteon devices (even of the existing type) are not added the 99i should be fine. I'm sorry I do not know the answer to the original question. I do not use ELK. Normally things go the other way. An existing ISY configuration is transferred to the ELK. Usually in this scenario you would need to start over in the ISY and export the mapped devices / scenes to the Elk. Putting the ISY in "command" with fresh programming is the better way to do it. Yes, it will take a bit longer but if you have any issues the troubleshooting will be easier with the ISY. The Elk has very limited if no ability to troubleshoot issues should you happen to run in to any. If you have 30 devices in the Elk being controlled you may end up with a cleaner interface between the two systems using the scenes from the ISY mapped to an Elk X-10 address slot which is what the export from the ISY does.
davefred99 Posted May 24, 2013 Author Posted May 24, 2013 It is not the features you see that will bite you. So long as new Insteon devices (even of the existing type) are not added the 99i should be fine. I'm sorry I do not know the answer to the original question. I do not use ELK. Normally things go the other way. An existing ISY configuration is transferred to the ELK. Usually in this scenario you would need to start over in the ISY and export the mapped devices / scenes to the Elk. Putting the ISY in "command" with fresh programming is the better way to do it. Yes, it will take a bit longer but if you have any issues the troubleshooting will be easier with the ISY. The Elk has very limited if no ability to troubleshoot issues should you happen to run in to any. If you have 30 devices in the Elk being controlled you may end up with a cleaner interface between the two systems using the scenes from the ISY mapped to an Elk X-10 address slot which is what the export from the ISY does. Well it seems that after digging a little deeper I am going to have to start from scratch. I wanted to keep my elk system running in parallel with the Isy while I got up to speed but from what I can tell it is not advisable to have two controllers running on the same system. The way Elk uses Insteon natively is not the same as how ISY does and linking multiple controllers can be a big problem. So now I am sort of stuck on how to best move forward. Starting from scratch what is the best way to begin my transition. I see three options for importing devices where as one is to just add the device and delete all other links and the other two are variations on importing existing links. Not sure which to use as I have lots of interlinked devices with 3 keypad links and a couple motion sensors and a control link. I cant do anything until my m1xep arrives next week so I am looking for any help or suggestions in preparation for the switch and pairing the ISY to the ELK.
Michel Kohanim Posted May 24, 2013 Posted May 24, 2013 Hi davefred99, The best way to go forward is to start from scratch, put all your devices/scenes in ISY, and then export the configuration to ELK Lighting (as long as you have M1XEP). With kind regards, Michel
apostolakisl Posted May 24, 2013 Posted May 24, 2013 I have Elk/ISY combo since way back. Before ISY had an Elk module. I will put another vote in for you to start from scratch. Frankly, there is really no need to use the Elk to control Insteon devices at all. I did the export/import and all of my devices are thus programmed into Elk, but I might as well have not bothered. When you have the Elk module, very nearly 100% of Elk stuff is visible to ISY. This means that you can use ISY to control your lighting, even if Elk events are the trigger. Like if a zone opens or an alarm goes off. And vice-versa, if you want to control Elk functions from an Insteon device, you can program that into ISY as well. Like you might want to arm the system from a KPL button or turn an Elk output on. Once I got the Elk module, I removed all of the Elk rules that had anything to do with Insteon and moved them all to the ISY.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.