Connecting VRCZ4-MRZ - not to be confused with VRCS (DTH in post 20)

SetLightstatus() comes from lots of tinkering and me reverse engineering the Vera implementation. I did see that if you send something it doesn’t like (e.g. command with bad checksum, etc) it used to lock out. It’s been a while so don’t remember all the details.

Interesting. Did you have a Vera system (and/or can you point me to any documentation for same)?

Yeah I did/still do, though it’s no longer plugged in. It was closed source though as it was some sort of partnership w/ leviton so I think they gave them docs on the 0x91 commands. At least at the time I looked at this there was none public. If you find any id love to see them in case there’s anything else cool.

Sure. (And it worries me that, without your Vera-based explorations, we’d never know how to control those status lights…)

Quick update: I’ve now installed two more VRCZ4-M0Zs (for a total of four), and they both worked perfectly with my DTH and smartApp right out of the box (after I first let them get discovered by the SmartThings hub and initialized as "Z-Wave Remote"s).

I might tweak the dimming function to make it a bit faster, but otherwise these seem good to go.

Curious to know if these updates resolve the issues reported by others (@barney.raymond, @BadPirate, @birnboim)?

1 Like

Cheers for keeping development alive for the VRCZ4. I have got two partially working–On and dim work, but I cannot get any lights to turn off. Nevertheless, very excited that these are functioning for first time in years! Thank you

1 Like

So glad to hear that!

I’m surprised (and somewhat confused) to hear that it’s turning on and dimming for you, but not turning off? Offhand, I don’t see how that would be happening.

Happy to look into it with you, though – are you up for some live-log analysis?

I can talk you through, but I’d be especially curious to de-comment the log.debug statements in the buttonEvent() handlers in both the smartApp (line 72) and the DTH (line 159), and also to add some new ones in the DTH’s supporting methods buttonToSwitch() and buttonToStatus() (lines 186 and 192, respectively).

The old control path (see handleManufacturerProprietary() at line 92 of the DTH) expects the on/off state to be encoded in the Manufacturer Proprietary messages that I’ve only ever seen coming out of my very first VRCZ4. (And they still do, FWIW.)

The new control path uses Z-Wave association to associate the “on” sides of the buttons with “button” numbers 1-4, and the “off” sides of the same physical rocker-buttons to “button” numbers 5-8. Everything else keys off of those button-number assignments, so I’d expect “on” and “off” to work (or not work) similarly to each other.

I can see two possibilities thus far: Perhaps you’re on the old control path and the Manufacturer Proprietary codes you’re getting are slightly different from mine (so that the "on"s match, but the "off"s don’t?); or it could be that you’re on the new control path, and you’re (somehow?) successfully associating the “on” button-numbers but not the “off” button-numbers?

In any case, the debug statements I’ve suggested above (along with, perhaps, the ones in handleManufacturerProprietary()) should shine some immediate light on the situation.

Let me know what you see?

1 Like

@mpk I’m ecstatic that you and others have been working hard on making these Leviton scene controller switches more reliable. I installed a couple for my parents and their HS-WS100 connected lights sometimes takes 10 seconds to respond to the commands, and usually no faster than 2 seconds.

Are there any other reliable z-wave scene controllers that work with ST? I tried the Cooper-Aspire 5-button but from what I remember it didn’t work as well. I also saw the Evolve Controller series but have no idea if they can be integrated.

Sorry – I don’t have experience with any other controllers besides the VRCZ4s. But I will add that I’ve never seen anything approaching a 10-second delay (or even 2 full seconds, for that matter) with my setup.

What I have noticed, however, is occasional/intermittent lags of 1-2 seconds, which I’ve attributed to Internet delays in communicating across the cloud.

Can I ask where your parents are located, and what sort of Internet connectivity they have? (I’m in NYC, with a 1GB Verizon FIOS connection…)

I ended up using the Cooper Aspire switches. I found a device handler which worked pretty well.

I have noticed a delay in my setup, as well, but it might be the relays that I have behind the lights.

I have Fios 50/50, you think that is an issue?

I have a couple VRCZ4 devices that I didn’t use (one opened, one still sealed) in case anyone is interested.

I’m using the same scene controllers- they live in NYC with a 100 up/down FIOS connection.

I might be interested in your VRCZ4s (as my DTH/smartApp seem to be working well now – I already have four of them running). Message me directly and we can discuss?

(And no…I don’t really think FIOS 50/50 should be an issue)

Yeah…I doubt 100/100 is a problem (for delay). Not sure what else it might be – maybe radio noise for the Z-Wave?

Hi

Following up on the discussion about the VRCZ4s.
I have two of them. One is brand new & still sealed in the original box.
The other has been opened. It is pretty much ‘like new’ (as far as I can tell) except that the GREEN (ground) screw ‘came out.’ I’m not sure how to get it to ‘re-catch’ to get it to stay back in.

Let me know your thoughts/interests.

Thanks

I tried updating – no joy. Lights seem to be registering correctly, but action button still doesn’t work. Turned back on the logging with your latest and here is an example of what I see when I hit the top button in the off position:

130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:42 PM: debug Parsed SceneActuatorConfGet(sceneId: 0) to [['name':'button', 'value':'default', 'descriptionText':Kitchen Controller button was released, 'isStateChange':true, 'displayed':true, 'linkText':'Kitchen Controller']] ([[name:button, value:default, descriptionText:Kitchen Controller button was released, isStateChange:true, displayed:true, linkText:Kitchen Controller]]) from description zw device: 19, command: 2C02, payload: 00
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:42 PM: debug Kitchen Controller button 0 was released
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:42 PM: debug Entering buttonEvent() for button 0...
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:42 PM: debug SceneActuatorConfGet: SceneActuatorConfGet(sceneId: 0)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:42 PM: debug Parsing 'zw device: 19, command: 2C02, payload: 00 '
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:39 PM: debug Parsed BasicSet(value: 0) to null (null) from description zw device: 19, command: 2001, payload: 00
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:39 PM: debug Kitchen Controller bzone button was pressed: BasicSet(value: 0)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:24:39 PM: debug Parsing 'zw device: 19, command: 2001, payload: 00 '

And when I hit the second button in the on position:

130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Parsed SceneActuatorConfGet(sceneId: 0) to [['name':'button', 'value':'default', 'descriptionText':Kitchen Controller button was released, 'isStateChange':true, 'displayed':true, 'linkText':'Kitchen Controller']] ([[name:button, value:default, descriptionText:Kitchen Controller button was released, isStateChange:true, displayed:true, linkText:Kitchen Controller]]) from description zw device: 19, command: 2C02, payload: 00
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Kitchen Controller button 0 was released
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Entering buttonEvent() for button 0...
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug SceneActuatorConfGet: SceneActuatorConfGet(sceneId: 0)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Parsing 'zw device: 19, command: 2C02, payload: 00 '
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Parsed SceneActuatorConfGet(sceneId: 0) to [['name':'button', 'value':'default', 'descriptionText':Kitchen Controller button was released, 'isStateChange':true, 'displayed':true, 'linkText':'Kitchen Controller']] ([[name:button, value:default, descriptionText:Kitchen Controller button was released, isStateChange:true, displayed:true, linkText:Kitchen Controller]]) from description zw device: 19, command: 2C02, payload: 00
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Kitchen Controller button 0 was released
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Entering buttonEvent() for button 0...
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug SceneActuatorConfGet: SceneActuatorConfGet(sceneId: 0)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:04 PM: debug Parsing 'zw device: 19, command: 2C02, payload: 00 '
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Parsed BasicSet(value: 255) to null (null) from description zw device: 19, command: 2001, payload: FF
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Kitchen Controller bzone button was pressed: BasicSet(value: 255)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Parsing 'zw device: 19, command: 2001, payload: FF '
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Parsed BasicSet(value: 255) to null (null) from description zw device: 19, command: 2001, payload: FF
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Kitchen Controller bzone button was pressed: BasicSet(value: 255)
130eec72-e7aa-4fd8-9cc7-a0fd7df94ed5 1:27:01 PM: debug Parsing 'zw device: 19, command: 2001, payload: FF '

Sadly, neither had any effect on the state of the linked devices. Any steps I should take besides re-installing the driver and app software (done) and re “saving” the configuration information?

Sorry, Kevin – didn’t see this before now.

Yeah, after making sure you have my latest versions, you should try reconfiguring. Your outputs (above) are showing “button 0” and “null” throughout…while the latest code should be assigning (and recognizing) a unique scene number for each button.

It looks like a very knowledgeable group on the Leviton Zone and Scene Controllers. Does anyone know if you can use either two VRCS4 for VRCZ4 controllers to connect to a single z-wave switch (Leviton switches in my case). I am building a house and planning on putting my load switches in a closet and using scene or zone controllers to control lights in the family room / kitchen / dining in an open floor plan. I would have two controllers connecting to a single switch. This post seems to indicate multiple scene controllers can be associated with a single switch but it doesn’t specifically call out either VRCS4 or VRCZ4. I would appreciate any help. Thanks!

http://communities.leviton.com/message/3755#3755

Kevin

Okay, pulled latest version, deleted app from device, checked controller settings and still no love :frowning: Here is what I see in the logs:

c5eaeea6-f521-44bb-a5f4-3da91a3a3b28 6:59:14 PM: debug Falling through to default case for buttonEvent() on event physicalgraph.app.EventWrapper@1dade7fe with evt.data {“microDeviceTile”:{“type”:“standard”,“icon”:“http://schemalive.com/vrcz4-m0z.png”,“backgroundColor”:"#ffffff"}} parsed to [microDeviceTile:[icon:http://schemalive.com/vrcz4-m0z.png, backgroundColor:#ffffff, type:standard]] with status null for button null

c5eaeea6-f521-44bb-a5f4-3da91a3a3b28 6:59:14 PM: debug buttonEvent data: [microDeviceTile:[icon:http://schemalive.com/vrcz4-m0z.png, backgroundColor:#ffffff, type:standard]]

c5eaeea6-f521-44bb-a5f4-3da91a3a3b28 6:59:14 PM: debug buttonEvent evt: physicalgraph.app.EventWrapper@1dade7fe

c5eaeea6-f521-44bb-a5f4-3da91a3a3b28 6:59:00 PM: debug 1B

c5eaeea6-f521-44bb-a5f4-3da91a3a3b28 6:59:00 PM: debug Devices for Button 1: Kitchen Fan

It’s worth noting that using the same configuration I’ve got 2 other leviton switches of the same make working in my house (WOW!) – It’s a real pain, but should pull the device and rejoin it? Is there any better reset button here?

Hm…first, just to clarify: You’re saying (at the end) that two other VRCZ4s are working properly with the same DH/smartApp, but a third VRCZ4 is not?

I’m not sure I have all the context I’ll need to fully make sense of those debug statements…but the first debug is certainly odd/curious. It’s happening when you turn one of the buttons on/off?

I wonder: Since deleting/restoring the smartApp, have you also updated/reassigned the Device Handler to the latest version? And after updating both, have you then gone into the DH screen on your phone and pressed both “Configure” and “Get My State”?