Elk Firmware Version?

[automateme]

Is 5.1.x M1G firmware required for use with the ISY-99i? I am installing a Caddx NX Wireless Receiver, and Elk shows that version 4.5.4 is required. Version 5.1.x only works with the Elk Wireless.

[Morris Hansen]

I am using a Caddx NX-548E with firmware 4.5.4 along with the 99i.

 

I am not having any issues.

[automateme]

Thanks for the info!

 

I was able to import the ISY's XML file into the M1 after I updated to version 1.6.24 of ElkRP. I still cannot get communication to/from the M1 and the ISY though. I put the M1's IP and Port into the ISY. I could not see anywhere in the M1 to specify the IP of the ISY. Also, the field in my Automation/Lighting tree shows "Opt", and not "Future". I wonder if that has anything to do with my communication problem. Which does yours show (Opt or Future), and what version of ElkRP are you using?

[Morris Hansen]

Which port number did you put into the ISY. It should be whatever you have configured for non-secure port in Elk RP. Default is 2101.

 

The IP of the ISY is part of the XML file that is imported into the Elk. I assume the ISY and the Elk are on the same network. I don't know if it technically matters but would be easier to troubleshoot.

 

I am using Elk RP version 1.6.24. I show Opt in the lighting tree.

 

Main Program Version 1.6.24

M1G Control Version 4.5.28.0

M1 Control Version 4.5.28.0

EZ8 Control Version 4.5.28.0

ElkComm Version 1.2.10.10

ConvertDB Version 1.2.10.0

ElkSafe Version 1.0.2.0

ErrorDlg Version 1.0.10.0

 

How are you testing the functionality? using rules? web access?

[automateme]

Thanks for your help on this. I just had my Elk installed, so I am learning my way around it. We have exactly the same versions of software. The ISY and Elk are on the same network. I did not have the non-secure port enabled, so I turned it on and used the default 2101 port. I had put my secure port into the ISY. I changed the ISY setting to 2101, and re-exported the XML. I then went back to the Elk, cleared the Lighting, and imported the new XML. After fixing-up my Opt and Show settings, I sent it to the Elk. I don't know if it is necessary, but I did not restart the Elk. Unfortunately, still no joy. I am testing by going into the Lighting page on the Java applet console. It shows all of the lights that I enabled in the "Show" field. Clicking them on an off does nothing.

[Michel Kohanim]

Hello automateme,

 

Do you see the security panel at the top of ISY? If ISY can communicate with your ELK M1XEP, then a security panel will be visible at the top of ISY's Admin Console. If so, please see whether or not you can arm/disarm your ELK from within ISY. We'll isolate the problem one at a time.

 

With kind regards,

 

Thanks for your help on this. I just had my Elk installed, so I am learning my way around it. We have exactly the same versions of software. The ISY and Elk are on the same network. I did not have the non-secure port enabled, so I turned it on and used the default 2101 port. I had put my secure port into the ISY. I changed the ISY setting to 2101, and re-exported the XML. I then went back to the Elk, cleared the Lighting, and imported the new XML. After fixing-up my Opt and Show settings, I sent it to the Elk. I don't know if it is necessary, but I did not restart the Elk. Unfortunately, still no joy. I am testing by going into the Lighting page on the Java applet console. It shows all of the lights that I enabled in the "Show" field. Clicking them on an off does nothing.

[automateme]

Hi Michael,

 

No, I do not see the security panel at the top of my ISY in the Admin Console. All I see are the regular Tabs (Main, etc) and above that the Date/Time information, and above that the icons associated with the menu items.

[Michel Kohanim]

automateme,

 

This means that ISY cannot communicate with your M1XEP for one reason or another. Please do the following:

1. Go to ELK tab (in Configuration)

2. Remove ELK IP and ELK Port and then click Save

3. Enter the IP and Port again and then click Save. Wait for about 16 seconds ... if the security panel does not appear, then ISY is not communicating with your M1XEP and we would have to find the network issue.

 

With kind regards,

Michel

 

Hi Michael,

 

No, I do not see the security panel at the top of my ISY in the Admin Console. All I see are the regular Tabs (Main, etc) and above that the Date/Time information, and above that the icons associated with the menu items.

[automateme]

Michael,

 

I tried removing the IP/Port, saving, then putting back in the IP/Port and waiting ~16sec. No change at all in the Administrative Console.

 

I don't know if its related but, when I originally configured the 99i for the Elk, I incorrectly put in the secure port instead of the non-secure port. When I did a save, the top section of the Administrative Console started flashing what looked like a login box. It continuously flashed between a section with a login box, and the normal Administrative Console. I closed the Admin Console and logged back in, but it was still flashing. I finally pulled the serial connection to the PLM, to recycle power, and the flashing stopped when I logged back in.

[automateme]

OK, all is well. Lighting control works great.

 

I telneted into the ISY and did an RS after changing the port, and after the reboot completed, I could see the security panel at the top of the Administrative Console. So I guess that the lesson learned is, if you inadvertently put in the wrong information (secure port vs. the non-secure port) when configuring the IP/Port for Elk, you might need to reboot the ISY.

[Michel Kohanim]

Hello automateme,

 

Thanks so very much for the update. You should never have to reboot ISY but this situation was reported once (and only once) before so we'll surely try to figure out the root cause.

 

With kind regards,

Michel

 

OK, all is well. Lighting control works great.

 

I telneted into the ISY and did an RS after changing the port, and after the reboot completed, I could see the security panel at the top of the Administrative Console. So I guess that the lesson learned is, if you inadvertently put in the wrong information (secure port vs. the non-secure port) when configuring the IP/Port for Elk, you might need to reboot the ISY.