Leviton VRCS4

One possibility, which is the most likely issue, is that your VRCS4 is not associated to the ST hub on all four buttons.

How would I go about doing the association? I “joined” it to the z-wave network (hold button 1 + 3) and the device came up as z-wave controller. Is there another procedure to associate the other buttons?
Then I assigned the device handler to the device and installed the smart app for the button control.
Button 1 works as expected, the others aren’t even seen at the hardware level.
Thanks.

Can you post the code to the driver you are using?

Joining the z-wave network is different from associating the device to the hub. Some of the drivers will do the setup for the associations and some will not ( or… some will do the setup but will never confirm the setup actually worked ).

The SmartThings will often set itself up for the first association, but only in few cases, I believe, does ever attempt anything beyond that. There are devices with nine or more associations, and depending on what the version of z-wave is, they may or may not be critical for making the devices work.

Hello… I tried a couple of them actually. The most recent one I believe is yours:

  • Leviton VRCS4-M0Z Vizia RF + 4-Button Remote Scene Controller

But I’ve tried this one:

  • ZWave Scene Control
  • Copyright 2014 Brian Dahlem

and

  • Leviton VRCS2 Button
  • Copyright 2014 Brian Dahlem

Do you need the full code? I can paste that if that’s helpful.

All of them only see button 1.

Chris

If its the driver I published then on the devices page found via graph(*) then there will be a listing for what is in each group for the device. Just search the devices page for “Group #1” and so on.
You should find your SmartThings up in all four groups ( your hub will probably be device 1 ).

*) https://graph.api.smartthings.com/

That link will only work for some people, as different accounts are on different shards.

Instead, there is a universal sign on link at

https://account.smartthings.com/

This will automatically direct each person to their correct shard.

Please use that link in any forum posts and that way it will work for everyone. :sunglasses:

Brian:
Thanks for your reply, but I must admit, I’m totally not understanding what you are saying.
There’s a device handler and the device itself - are you talking about looking into the code in the device handler? Sorry if I’m ignorant to this.
Chris

Thanks! I always thought that the graph link was the universal link :slight_smile:

I believe that when I started using ST there was a different link, and somehow… I’ve just been using that one.

1 Like

HI Guys

Thanks by the DHT and SMART APP, I have used it in my vrcs4 for long time.

But now I am having a problem. My old smartthing hub(model STH-ETH250) died and I had to buy a new one(model GP-U999SJVLGDA) . But now the DTH and SMARTAPP from @bdahlem neither @ygelfand has worked in the new hub. In my old hub they worked fine.

Somebody has had this problem, could any of you guys help me pls?

HI Chris

Have you solved your problem with your vrcs4?

Hi @Malekfahl,

Just seeing your posts now (since you hadn’t flagged me with a leading “@”, so I wasn’t notified when I was mentioned).

@BrianAker is right – what you’re after is exactly what the VRCZ4 is designed for (and what my DTH and SmartApp support). I’ve never owned or tested a VRCS4, but it all comes down to what that unit does when you press the same button a second time (without pressing any other buttons in-between): Can you see the second press come through in the logs?

If you can, then there’s no reason you can’t add state-tracking for each button within the SmartApp, and use that to “toggle” the corresponding load on/off on alternate presses. If not (perhaps because the VRCS4 is only notifying on a change of “current button” selection, rather than every single press), then you’re going to need to replace your VRCS4s with VRCZ4s.

Let us know (either way?)

Ok thanks for the reply. I guess I’ll replace the device with a zone version. Thanks for the info.

Chris

OK – but I’d still be curious to know if the scene-controller version will signal repeated pushes of the same button. (Maybe you can check in your IDE?) If it does, I can help you adjust the code accordingly.

I will check - it toggles the device assigned to the first button - on/off properly but I cannot get it to do anything with the rest of the buttons - so I think it is seeing the repeated button press (just for button 1). I think this might answer this question but I’ll dig into the IDE again and take a closer look.
Thanks.

Wow those are expensive - $150-$175 per device. Is there a better option for an “in-wall” zone controller that anyone knows of?

Are you seeing that first button toggle the state values in the IDE/logger, or just seeing that it properly controls a device connected to that first button?

Depending on which version you have, the first button includes a physical switch that operates directly on the connected load. IIRC, people have sometimes seen this first-button-only behavior when in fact the DTH/SmartApp aren’t really working properly at all.

Let me know about the IDE and the other buttons, and we can go from there.

I’ve had good luck setting filters for these on eBay, FWIW – they’ll occasionally show up much cheaper.

Thank you. This device is: VRCS4-M0Z
It doesn’t have the relay switch built-in, it is only a scene controller and only wired to power (not to the load itself).
I bought the “S” version because I saw a thread somewhere on here and thought the scene version was the correct one to get - but I’ll still confirm in IDE. Thanks a bunch for your help. I really appreciate it.

1 Like

If there are some thing that I can do for help please let me know.

Here is a quick copy/paste from the IDE when pushing buttons on the VRCS4-M0Z

3f13739c-8768-455a-a863-a387d091a20b 5:31:26 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:31:26 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:31:26 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:31:26 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:31:03 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:31:03 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:39 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:36 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:27 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:27 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:25 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:23 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:22 PM: debug Parsing 'zw device: 33, command: 2605, payload: ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:21 PM: debug Parsing 'zw device: 33, command: 2604, payload: 00 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:18 PM: debug Parsing 'zw device: 33, command: 2605, payload: ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:18 PM: debug Parsing 'zw device: 33, command: 2604, payload: 40 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:12 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:12 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:06 PM: debug Button 1 repeat 0x 1571178606395

3f13739c-8768-455a-a863-a387d091a20b 5:30:06 PM: debug Parsing 'zw device: 33, command: 2B01, payload: 01 FF ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:04 PM: debug Parsing 'zw device: 33, command: 2B01, payload: 01 FF ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:04 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:04 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:00 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:00 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:00 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:30:00 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:58 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:58 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:58 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:56 PM: debug Parsing 'zw device: 33, command: 7205, payload: 00 1D 08 02 02 61 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:56 PM: debug Parsing 'zw device: 33, command: 7205, payload: 00 1D 08 02 02 61 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:55 PM: debug Sending configuration: [7204, delay 100, 8505, delay 100, delay 100, 2C0300FFFF]

3f13739c-8768-455a-a863-a387d091a20b 5:29:51 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:51 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:38 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:38 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:38 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:38 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:32 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:29:32 PM: debug Parsing 'zw device: 33, command: 2001, payload: 00 ’

3f13739c-8768-455a-a863-a387d091a20b 5:27:56 PM: debug Parsing 'zw device: 33, command: 7205, payload: 00 1D 08 02 02 61 ’

3f13739c-8768-455a-a863-a387d091a20b 5:27:56 PM: debug Parsing 'zw device: 33, command: 7205, payload: 00 1D 08 02 02 61 ’

3f13739c-8768-455a-a863-a387d091a20b 5:27:54 PM: debug Sending configuration: [7204, delay 100, 8505, delay 100, delay 100, 2C0300FFFF]