Elk RP2 Connect

[CapeCod]

We have an Elk M1G that was installed by a local alarm company. Now in the process of moving from our Vera 2 zwave to the Elk, I am having trouble connecting RP2 through our wireless LAN. I followed the webinar and web tutorial with no luck. Do I need to start with a direct serial connection?

We now have 12 switches and six outlets on zwave. Moving into the Elk, we will add some outdoor motion detectors, indoor temperature control, Elk serial expander and a Leviton LEV-VRC0P-1LW.

 

[drvnbysound]

During the setup of my M1, I never connected via Serial connection. So it's certainly possible to do it without using the serial port. That said, I have to ask some questions that may seem pretty silly...

I assume if you are trying to connect via wireless, that you also have a M1XEP installed (??). Do you know what the internal IP address of the XEP is? Can you ping that address successfully?

 

[CapeCod]

Yes, Should have mentioned that. First attempts using the setup ELK button on the accounts page found the M1 and gave an IP address 1.0.1.2. Now, I'm getting a message "Can not connect" and No M1EXPs found. I'm pretty much a dummy about networking.

 

[chrisexv6]

1.0.1.2 sounds like an odd IP for the Elk.

Can you log in to your wifi router? There should be a page on it that will list the connected devices and their IPs (and their MAC addresses as well). Thats what I usually use to determine the IP of a new device. The Elk should be listed somewhere, if you know what else is on the network you can use process of elimination to get the correct IP for the Elk (or just try each of them one at a time if necessary)

 

[Del91574]

The IP sounds oddly enough like an "apple" based IP, as they seem to favor using that range to start.

Is the XEP DHCP or fixed? Is the IP address reserved? Have you tried going direct into the XEP with a crossover cable?

 

[drvnbysound]

There are exceptions, but generally, you will want the XEP on the same IP scheme as the rest of your network devices (e.g. router and other computers).

That said, if your router uses a 192.168.1.x address (usually 192.168.1.1), the XEP will need to be addressed similarly (e.g. 192.168.1.100). Most all consumer grade routers allow you to select what address to start DHCP addresses (those addresses which the router will give out on its own) and have an option as to how many DHCP addresses to give out. For example, it could be set to start handing out addresses starting at 192.168.1.100, and set to hand out up to 50 addresses. In that case, 192.168.1.100 could be reserved or used by a phone or other device on your network, and you would want to set the XEP to an address outside of that range (e.g. use 192.168.1.200 instead).

Del asked above, regarding your XEP setting (DHCP vs. fixed)... personally I would highly suggest using a fixed (static) address so that you always know what address it is set to and you should be able to always access the web interface using that address if you are on your local network (LAN). If you use DHCP, the address should generally stay the same but there is no guarantee that it won't change (e.g. power failure).

 

[CapeCod]

It turned out to be a cat5 that came loose on the switch box. This is compounded by some compatibility problem with windows 8. Installing on the older desktop worked. I might wait for a version update that deals with 8.

The UPS guy will bring the serial expander,ELK-M1XSP, and the Leviton LEV-VRC0P-1LW tonight. Any advice welcomed. Looking at the M1XSP it looks like a straight 4 wire connection to the data bus with no EOL resistor. I think jumper JP3 gets pulled as well.

 

[chrisexv6]

You'll want to read, re-read, and then re-read again the part of the Elk manual that talks about connecting to the databus. And then for good measure read the exact same section in the XSP manual Its important not just for the XSP but to understand the Elk databus in general. Where you need to terminate it, how you can daisy chain things, home runs, etc.

if you are using the Leviton connected to the XSP you might need to update the firmware on the XSP itself. Take baby steps: concentrate on getting just the XSP connected to the databus first, then make sure you can see it in ElkRP so that you can update the firmware if necessary.

 

[CapeCod]

Good advice.

Having recently switched over to Mac, and a time capsule (still have 8 pc's in the house), I need to do some research on assigning addresses. There is a section called DHCP Reservations in the airport utility probably for this very purpose. I was checking out some of the places that offer DDNS as a workaround for a static IP. dyn.com/dns/ for example. Maybe this is a good way to go.