Does anyone have or know how to integrate the Z-Wave Duwi Remote Control with Smarthings. I’ve added into my Smarthings Hub, it appears as a ‘Z-Wave Remote’ however there are no smartapps for this device.
<img src="/uploads/default/original/3X/c/9/c999b87729ac668eb2ab7b6f32d0c489b28a1f37.png" width=“121” height=“291” style="“float:righ!important;text-align:right;”>
Depends on how it binds. If it is joining as a secondary controller, you won’t be able to do much with it. If it is joining as a button controller, you can do more.
See the docs
3.5.3 Including devices on additional controllers
Here a device is registered in the network using the primary controller (or on the usage of a wireless switching centre/
server using any controller), without direct allocation to a group. The device can then also be allocated to the group/
scene on other controllers in the network, e.g. an additional wall transmitter or if the device is not to be switched via the
primary controller.
Thank you for taking time to respond, the only way to get it into Smartthings is to add it as a ‘Secondary Controller’ in terms of the Duwi remote. Oh well. I got tricked into buying it when buying another z-wave product! Never mind.
Not that these are completely useless. They can be setup to control lights and switches in tandem with ST. You just won’t be able to control any non z-wave devices with it.
I use z-wave remotes in my kids rooms. They seem to like it better than having tasker controls on their tablets. As long as you’re just looking to control Z-wave devices it’s a nice, easy to use “offline” secondary option.
Looked at this–it does use association. I think it may be able to used just like a minimote. (The minimote also joins as a controller; it’s not what it does when it joins that matters, it’s how it communicates when a button is pressed. If it uses Association, then we’re in. We put the hub in the Association group (not the end devices), then the hub gets the message when the button is pushed, and it can be a button controller.)
Same idea as The enerwave sc7.
The GE devices don’t work that way with smartthings because they don’t use Association. They don’t just join as a secondary controller, they act as a secondary controller, which means when you press a button on the remote itself sends a basic commands directly to the devices that it included (which have to be zwave devices within one hop).
But the Duwi remote uses Association, so I think it may work as a button controller where we get it to send its command to the hub rather than directly to the end device.
Of course if you do that then it just becomes a set of seven buttons. When you press the button it just sends a message to the hub. You would lose all of the fancy light information, with red lights meaning one thing and yellow lights meaning another thing and all of that. It will likely need custom code. and it will only work if the connection to the smartthing cloud account is available. But I think it may be doable. 
For clarity, “bind” is is a zigbee term, not zwave. In zwave, the device will always join the same way. The only thing that makes it a button controller is that it is able to do association and send its button presses to the hub that way and that the device type handler includes capability.button. (or for newer devices use the “central scene command set,” but not the older “scene” command set and again use A DTH with capability.button)
So if it uses Association, we should be able to get the button presses.
The official conformance statement for this device is missing some fields, but it looks like it should join as a handheld controller, just like the minimote, and that it supports Association, again just like the minimote. So I do think it should be able to be used like a minimote. You won’t get to use all the buttons the way the manufacture intended, and you probably won’t get the red/yellow/green lights, but you should be able to press a button on the device and have the hub know about it. At that point with the right automation, including the official smartlights feature, you should be able to get the hub to send instructions to other devices on the SmartThings account.
But there may be some manufacturer – specific issues, I don’t know. And it would need a custom DTH to get control of all the buttons. If someone who has one can let us know how they are using it, that would be helpful.
I have one, but I can only control my lights by directly associating my lights with it, not via the hub. That has advantages though, because it allows me to dim/bright my lights by continuous holding of the button, something that can’t be done via the hub, which is a shame.
Just to add. I did associate it with the hub too (I think by accident rather than intentionally) as a zwave controller, but that’s as far as I got.
So I’m assuming that those lights can also be controlled in other ways from SmartThings? Even if it’s just opening the mobile app and using the things screen?
If so, the sequence would go like this:
One) add all the lights to the SmartThings account
Two) add the remote to the SmartThings account. It should be found as a portable controller or maybe a secondary controller. Just adding it to the SmartThings account will automatically put the hub in Association group one. You don’t have to do anything special.
http://docs.smartthings.com/en/latest/device-type-developers-guide/z-wave-primer.html
The SmartThings hub automatically adds itself to association group 1 when a device that supports association joins the network.
One of the advantages of using a Z wave device as a button controller and sending the messages through the hub rather than sending the messages to the lights directly from the remote is that with the button controller you can control anything that smartthings controls, including mode changes or devices of other protocols. And you can also control devices that are more than one hop from the remote, like lights on the other side of the house. But there are still community members who are using direct association with nearby Z wave devices for various reasons.
Those three steps should do it. The lights can talk to either the hub or the remote. The remote is known to the hub but you’re not doing anything with that other than giving it permission to talk to the light.
To go further, you would need to be using a device type handler that had capability.button
Yes, that’s how I have it working - direct control of zwave devices from the remote. And yes, the hub can still control those same devices.
I’d love somebody to be able to create a DTH that allowed me to use the remote with the hub.
Quick (general) question. I have associated my floor/table lamps to the duwi remote easily because they operate via pocket sockets…and association just involves a triple click of the pocket socket’s button. But is there a way to put these devices into association mode remotely? The reason I ask is I want to associate my fibaro dimmers to the remote and they are not easily accessible.
Short answer is maybe. You can write code to attempt it, it’s just that not all devices will accept it without physical manipulation of the device, usually a button pattern as you mentioned.
See the following for the code you have to write:
@RobinWinbourne might have more to add, he is an expert on the Fibaros.
I do know Fibaros can be tricky in associations if you have paired them in secure mode.
First of all apologies because I am sure that somewhere there already exists the answer to this however I can’t find it after a lot of googling. I suspect the answer is I need the right DTH and I may have to write one but I havent written DTHs yet and I don’t really understand Zwave enough I now realise.
Background: I have a Duwi Zwave Remote [1], which is normally a standalone controller in a zwave network. I know this is not a great thing, and as it is a scene controller I know thats even worse, however bear with me as what I am looking to do is (as detailed in link [2] and see next post for link 3 and 4) use association to directly link the remote to the ST hub. I believe then it can be seen by the ST system as buttons when using association to ensure presses are passed to the hub not out to zwave devices. This would work perfectly as I see button press events (as I can then use pistons to do things with those events)
Now, I freely admit to being a little out of my depth here so if something doesn’t make sense I probably don’t understand it properly. In all the forum links @JDRoberts nearly answers this but not quite as I am missing something basic I think!
Fundamentally I am at a loss to how I actually go about linking the remote to ST not as a secondary controller - because if I do inclusion then the remote is seen as a secondary controller. This may not matter as it doesn’t actually affect how ST works with it. The remote has buttons for inclusion, exclusion and association (mainly for it to include/exclude as a controller I expect not as a zwave device would). So, should I just be able to change to a default DTH or is a new one needed, and if so do I need to write one handler for this. I see a button device is part of the ST list already but this thing has 10 buttons.
So, in short I feel like I am so close but so far away. I have missed something fundamental…or what I am doing isn’t actually possible (the remote was cheap from Vesternet so it was an experiment anyway)
Any suggestions welcome 
–Chris
[1] Z-Wave Duwi Remote Control Manual http://www.vesternet.com/downloads/dl/file/id/203/product/565/z_wave_duwi_remote_control_manual.pdf
[2] Thread on Duwi remote usage Z-Wave Duwi Remote Control (Reitz gmbH ZWRC10)
Other links:
[3] ST and Association Z-Wave association groups
[4] Another thread on Duwi remotes Z-Wave Duwi Remote Control (Reitz gmbH ZWRC10)
Ahhh ok thanks I understand. I started this separately as I thought it was going to go off on how to add devices differently and write custom handlers to support that process. But i see now what I was missing-that it’s all the same and it’s dependent on an inherent support of association not actually manually “performing an association”
I’ll have a play with the minimote handler and report back
Thanks!
Working with the minimote DTH (copy of which is here https://raw.githubusercontent.com/SmartThingsCommunity/SmartThingsPublic/master/devicetypes/smartthings/aeon-minimote.src/aeon-minimote.groovy) should I be seeing content around association classes being used in there (physicalgraph.zwave.commands.associationv2.*) as it doesn’t look like it does.
Initial testing of setting the remote to a type based on the minimote definition doesn’t seem to do anything - I can see events when i run the simulator on the IDE and press buttons but I see no button press events when i press real buttons on the remote?
I see that the other thread is now active again aftter you added a post and is indeed talking about a similar problem. I haven’t had a chance to catch up on it yet so that’s a job for tomorrow sometime
Back on this now…reading the thread you also were posting to and the gist in the crosslinked thread about switches I can see that the gist has calls to association classes but minimote doesn’t, so I’m not sure the minimote code (assuming I’m using the right one) will fulfil the association actions out of the box?
My problem is that when it gets to writing association related code from scratch I’m really in the dark, I can adapt and debug but at the moment I’m googling for DTHs that have association based approaches to button pushes.
Any suggestions
–Chris
(posting in here as the other thread seems to have diverged onto switches not duwi button presses)
I asked the same question about a device handler that would allow me to use the remote with the hub here
I’m not too fussed about this though, because I know I’d lose the ability to smoothly dim my lights if I use the remote via the hum. At present, the remote, by direct association with my lights, allows me to dim them as they should be dimmed - smoothly and via a continuous button hold.
I guess the only advantage I see of being able to use the remote with the hub is to allow me to control any (not just zwave) devices, routines, pistons, etc, but at the cost stated above.