M1XSLZW - Setting Associations

[drvnbysound]

Alright fellas... so I got my Elk M1G powered on a couple of days ago. I got the XEP installed (static IP), and configured most of the Elk setup via ELK-RP. I moved on to trying to setup the XSLZW with the VRCOP (I do have the +3 version). I have had my Zwave network setup for some time and it works fine with the GE/Jasco handheld controller that I've got. Note, I've also had the VRUSB-1US for some time, and the network was/is setup via the VRUSB as the primary. I added the VRCOP to the network as a secondary controller without any issue. However, I am getting error messages (for each device) when I attempt to set the Associations for the VRCOP. The instructions included with the XSLZW specifically state that doing so is a very important step. Any ideas?

Also, I've attempted to enroll the XSLZW (connected to a DBH) and the M1 is not finding it either... I assume that I should complete the Zwave setup first, but I figured this might also be worth mentioning. Curious about connections here... as stated, I am using a DBH. Am I correct to assume that the wiring should be identical to the keypad wiring? Specifically, (when using Cat5) should I combine A and A1 (Orange and Green), and B and B1 (White/Orange and White/Green) at the XSLZW? I assumed so... but this is the only thing that I can think of that could be wrong in terms of wiring (and the XSLZW not enrolling properly).

After stalling here, I was successfully able to get the email setup and working properly within about 5 minutes or so. It was much easier than I thought it was going to be, especially after reading the many issues that people have getting that setup. I now also in the process of getting DDNS setup, which I don't expect to be a major issue either, but I can't seem to figure out the XSLZW...

 

[thill]

Only Leviton branded device can be associated to the VRCOP. Leviton branded devices get associated with the VRCOP so that two-way status is always current. Unfortunately your GE/Jasco devices cannot be associated with the VRCOP which is why they are failing. There is no point in even putting a checkmark next to the non-leviton devices because they will always fail.

 

[jpmargis]

Am I correct to assume that the wiring should be identical to the keypad wiring? Specifically, (when using Cat5) should I combine A and A1 (Orange and Green), and B and B1 (White/Orange and White/Green) at the XSLZW? I assumed so... but this is the only thing that I can think of that could be wrong in terms of wiring (and the XSLZW not enrolling properly).

Correct. Terminator removed from the M1XSLZW and installed on the M1DBH?

 

[drvnbysound]

Correct. Terminator removed from the M1XSLZW and installed on the M1DBH?

Right. The jumper is only on one of the pins... not on to make the actual connection, and the terminator is on the first unused port of the DBH. My keypads are enrolled and working fine.

 

[drvnbysound]

Only Leviton branded device can be associated to the VRCOP. Leviton branded devices get associated with the VRCOP so that two-way status is always current. Unfortunately your GE/Jasco devices cannot be associated with the VRCOP which is why they are failing. There is no point in even putting a checkmark next to the non-leviton devices because they will always fail.

I'm not sure I completely follow what this means or the implications. It's been confirmed that this setup does work with the Kwikset locks which are obviously not Leviton devices. Also, the GE/Jasco devices are able to get status when using the Installer Tool Software... so I don't follow why the VRCOP couldn't also get this.

I don't have any Leviton devices other than the VRUSB-1US and the VRCOP... and the XSLZW installation manual says, "Click Diagnostics > RS232 Setup on the software title bar. Select the VRCOP-1LW Node as the RS232 Module and put a check in the box next to each device, then click Set Association. This IS A VERY IMPORTANT STEP!" Based on what you are saying, am I to assume that I cannot integrate my Zwave lighting with the VRCOP... and thus with the XSLZW?

... Or can I just skip the associations step, since they aren't Leviton devices and the two-way status wont work?

 

[jpmargis]

Get out your ohmmeter check the data bus connections between the M1DBH and the M1XSLZW.

 

[drvnbysound]

Get out your ohmmeter check the data bus connections between the M1DBH and the M1XSLZW.

Are you referring to just checking for continuity? If so, I assume that's just between the RJ-45 connector and the terminals on the M1XSLZW, since I don't know where I would test connections while the RJ-45 is plugged into the M1DBH...

 

[thill]

I'm not sure I completely follow what this means or the implications. It's been confirmed that this setup does work with the Kwikset locks which are obviously not Leviton devices. Also, the GE/Jasco devices are able to get status when using the Installer Tool Software... so I don't follow why the VRCOP couldn't also get this.

I don't have any Leviton devices other than the VRUSB-1US and the VRCOP... and the XSLZW installation manual says, "Click Diagnostics > RS232 Setup on the software title bar. Select the VRCOP-1LW Node as the RS232 Module and put a check in the box next to each device, then click Set Association. This IS A VERY IMPORTANT STEP!" Based on what you are saying, am I to assume that I cannot integrate my Zwave lighting with the VRCOP... and thus with the XSLZW?

... Or can I just skip the associations step, since they aren't Leviton devices and the two-way status wont work?

The Leviton Installer Tool software presumes that you are using only Leviton devices. So when you try to use it to do associations with non-leviton devices, those association will always fail. That doesn't mean you can't use the devices, it just means there is no direct association between the VRCOP and those non-leviton devices, so status will not be updated between them. Regarding Locks - There association of Locks to the VRCOP and is done in the background by the ELK interface as it auto discovers the setup. Also, the later versions of VRCOP also do Lock association in the background.

If you look closely at the instructions with the M1XSLZW you'll note it pushes Leviton devices and that's because all their devices support status update. That's also the reason it pushes the "Set Association - Very Important" step. Certainly you can use non-Leviton devices, but don't expect their status to be current (except for Locks). Status is a unique aspect of Leviton devices.

Yes you can probably just skip the associations step if you aren't using any Leviton devices. But you still need to perform the Update Controller step.

 

[drvnbysound]

The Leviton Installer Tool software presumes that you are using only Leviton devices. So when you try to use it to do associations with non-leviton devices, those association will always fail. That doesn't mean you can't use the devices, it just means there is no direct association between the VRCOP and those non-leviton devices, so status will not be updated between them. Regarding Locks - There association of Locks to the VRCOP and is done in the background by the ELK interface as it auto discovers the setup. Also, the later versions of VRCOP also do Lock association in the background.

If you look closely at the instructions with the M1XSLZW you'll note it pushes Leviton devices and that's because all their devices support status update. That's also the reason it pushes the "Set Association - Very Important" step. Certainly you can use non-Leviton devices, but don't expect their status to be current (except for Locks). Status is a unique aspect of Leviton devices.

Yes you can probably just skip the associations step if you aren't using any Leviton devices. But you still need to perform the Update Controller step.

Understood. Thanks for the information.

I suppose this is where all the questions regarding polling come in... I will likely give this another shot soon and post any further issues.

 

[drvnbysound]

Zwave lighting working I will certainly have to play with this for a while to get it setup how I want, but glad that I was able to get all the hardware communicating as expected.

 

[drvnbysound]

Lock working too.. However, I am now getting more interested in getting the Vizia RF dimmers and switches, based on the automatic reporting status mentioned above. Unfortunately, from what I've found so far, none of them support 'beaming' which means no support for the locks... My next best option is to install more of the receptacles that I have now, which do support beaming... simply for support of the locks, and just switch out my existing dimmers (at least I got them CHEAP!). Are there any known issues with routing of the security class messages for the locks in a configuration like this?

 

[potts.mike]

I think the 4 button scene/zone controllers support beaming.

 

[ddennerline]

That’s good news you were able to get everything working.
Which "receptacles" are being used?

Just to be 100% clear, your mileage will vary with non-Leviton switches/receptacles because the Leviton RF Toolkit is geared to only understand manufacturer’s device, plus a select number of third party devices.

For Leviton, the only additional device that supports Beaming/Encryption is the VRP03+3 plugin dimmer (they may have recently added a new device). The Kwikset (and Yale) locks do support association class (two-way updates), so they can be associated with VRC0P+3.

The Technical Support at AutomatedOutlet recommended to use Evolve devices, but I am very hesitant to introduce any non-Leviton devices into my network. Using single manufacturer helps avoid major support headaches and fingerpointing troubleshooting [Yes, I know that Z-Wave is supposed to be multi-vendor] :mellow: .

 

[drvnbysound]

That’s good news you were able to get everything working.
Which "receptacles" are being used?

Just to be 100% clear, your mileage will vary with non-Leviton switches/receptacles because the Leviton RF Toolkit is geared to only understand manufacturer’s device, plus a select number of third party devices.

For Leviton, the only additional device that supports Beaming/Encryption is the VRP03+3 plugin dimmer (they may have recently added a new device). The Kwikset (and Yale) locks do support association class (two-way updates), so they can be associated with VRC0P+3.

The Technical Support at AutomatedOutlet recommended to use Evolve devices, but I am very hesitant to introduce any non-Leviton devices into my network. Using single manufacturer helps avoid major support headaches and fingerpointing troubleshooting [Yes, I know that Z-Wave is supposed to be multi-vendor] :mellow: .

Thanks for the response. I currently have all GE/Jasco devices. About a year ago Radio Shack was selling off ALL of their Zwave gear and I got them for about $20 ea... I couldn't pass it up compared the pricing of other dimmers. The VRUSB has added and controlled them without any issues. Overall, everything is actually working fine, I would just really like the status of the lights updated when controlled locally or via remote.

That said, thanks for also adding the bolded part above. Since the previous information posted stated that no non-Leviton devices supported Associations, I didn't even attempt it with the locks... and am currently not getting the lock status updates when I lock/unlock locally. I will attempt to add the association for the locks and assume that this will keep me from having to poll the lock for status... we'll see.

 

[drvnbysound]

Once again... easy enough. Used the Leviton Installer Tool software, added the lock association to the VRCOP, updated the VRCOP... and lock status reporting is working as expected!