This past weekend, I installed an ISY994i/Insteon 2413s kit to integrate my Insteon network with my ELK to allow me to control my Insteon network using my ELK. I had previously used HouseLinc to control my Insteon network but I wanted to consolidate my Insteon with my ELK and to control both my security and Insteon Network from the ELK so sensors could be shared to achieve addition automation cababilities without having to double up sensors on some doors, etc.
The first surprise was that the 2413s PLM and the Houselinc PLM refused to recognize each other which made for link issues. I findly had to take the HouseLinc PLM off line to get anywhere.
The installation involved a huge learning curve to learn how the ISY operates and how it interfaces with Insteon and ELK. I felt the ISY could use updating of its user interface compared to HouseLinc or the ELK. It felt like it is a generation behind on ease of use, and user interface presentation. The interface should be more intuitive, and less cryptic, in its status and diagnostic reporting. After a nearly 2 day effort, I was able to prevail and get the ELK to control my Insteon network and duplicate the program actions that I had been using in HouseLinc.
My biggest current issue/concern is that the ELK network module(M1EXP) seems to only support one IP session at at time so if I open the RP program which I often do to check status of the ELK, the control of the insteon network stops. This is a particular issue for rules that use Sunset or Sunrise because if those triggers are missed, it fails to execute those Insteon commands so things like the evening scene fail to execute.
I am using the encrypted port in the M1EXP for my RP program, and have enabled and forwarded the unincrypted port and have the ISY coming in on that port. I set up a separate user and access code for the ISY to avoid any possible conflict there, but the RP logon stops the ISY session. Communication with the ISY and the Insteon network resumes once I log off of the RP application.
Any one have any ideas? Is there something I'm missing or is this the way it is with the M1EXP?
The first surprise was that the 2413s PLM and the Houselinc PLM refused to recognize each other which made for link issues. I findly had to take the HouseLinc PLM off line to get anywhere.
The installation involved a huge learning curve to learn how the ISY operates and how it interfaces with Insteon and ELK. I felt the ISY could use updating of its user interface compared to HouseLinc or the ELK. It felt like it is a generation behind on ease of use, and user interface presentation. The interface should be more intuitive, and less cryptic, in its status and diagnostic reporting. After a nearly 2 day effort, I was able to prevail and get the ELK to control my Insteon network and duplicate the program actions that I had been using in HouseLinc.
My biggest current issue/concern is that the ELK network module(M1EXP) seems to only support one IP session at at time so if I open the RP program which I often do to check status of the ELK, the control of the insteon network stops. This is a particular issue for rules that use Sunset or Sunrise because if those triggers are missed, it fails to execute those Insteon commands so things like the evening scene fail to execute.
I am using the encrypted port in the M1EXP for my RP program, and have enabled and forwarded the unincrypted port and have the ISY coming in on that port. I set up a separate user and access code for the ISY to avoid any possible conflict there, but the RP logon stops the ISY session. Communication with the ISY and the Insteon network resumes once I log off of the RP application.
Any one have any ideas? Is there something I'm missing or is this the way it is with the M1EXP?