Check out the official list of supported button devices...
So it looks like that is a no go. The question then becomes if any of the devices on the list has functionality similar to the minimote to set association between two or more devices.
Someone must know,. There have to be other people with 3 way dimmers! When I was in Vera, you could directly associate the devices via an "advance settings" tab.
Update: I have achieved an incomplete level of dimmer functionality using the following information in rule machine:
From the User Guide:
Set these dimmers
This action sets the selected dimmers to the selected level with an optional fade time, or tracks another dimmer’s level.
Track event dimmer works along with a Condition or Trigger Event of “Dimmer level”. When this dimmer level event causes the rule to run this action, the selected dimmers are set to the same level as the dimmer that triggered the rule. This can be used in automations where a group of dimmers follow another dimmer as it changes level. The typical usage for a Trigger is to have a Trigger Event of “Dimmer level >= 0”, and then Track Dim as the action.
I defined a trigger
The Accessory dimmer is the trigger where the trigger event of dimmer level greater than or equal to 0.
The master dimmer then tracks dim as the action.
With this, the Accessory dimmer can dim up and down, but cannot turn on and off the lights. Further, the Accessory dimmer has its own on and off, which means it wont control the master unless it is turned on itself.
Because association changed with Z wave plus, I don't think we are going to see anymore secondary controllers like the minimote which can form associations between two other devices.
With SmartThings, the preferred method now is to use the Z wave tweaker DTH. You just assign the device temporarily to that DTH, create your associations, then shift back to your every day driver.
I don't know if it's possible to port that to hubitat, but it would be the easiest way to deal with associations.
Failing that, you need to look into adding some secondary Z wave controller to hubitat, and I don't know if that's supported either. But the tweaker would be a much better option because it doesn't require buying a second device and it's much easier to use.
1 Like
Some button controllers are secondary zwave controllers, but others just use scenes or central scenes. It's really a different device class than the Cooper that was mentioned.
I would think you'd be able to add any secondary zwave controller, that's part of the zwave standard. But I don't know for sure with Hubitat.
Can you add a zstick to a Hubitat network?
1 Like
Thank you for your time in replying. That ST tool would seem to solve the problem. Sadly, I have no idea how to attempt porting it to Hubitat.
With respect to the Cooper handheld controller, I agree with your rationale.
I have a house full of Cooper and evolve/linear 3 and 4 way dimmers, so I’m in a bit of pickle. I either solve the problem or.....buy a bunch of HS switches and accessory switches I guess? Or I stay with Vera and deal with their issues
1 Like
FYI..
I've added multiple ZSticks (secondary) to the Hubitat network, successfully.
1 Like
Cooper is now a division of Eaton. So as of 2016, Eaton is the company, Cooper is the division, and Aspire is the model line. You can find the devices listed under any of these three names, or under "Eaton Cooper" or "Eaton's Aspire," it just varies by retailer. The model number is always the same, fortunately. 
http://www.cooperindustries.com/content/dam/public/wiringdevices/literature/lit_pdf/AspireBroch.pdf
See my post above - I was able to add my minimote (still working) as a secondary controller and was able to muddle my way through direct associations (I hope).
They work, but, when I tried removing some 'DEAD' Z-wave devices in Hubitat, a couple of my associations stopped working... this can't be correct, right?
Doesn't the secondary controller add those associations directly between the Eaton Aspire switches? Thanks.
Yes, no other devices should be involved except the trigger device and the target device. The association information is stored in the firmware of the trigger device.
1 Like
Thanks @JDRoberts - so, one final question - if the secondary controller (Minimote) is later excluded, those associations should continue to work, correct?
Yes, in this situation the minimote just tells the trigger device to store the information, it has nothing to do with The association after the set up.
If you exclude either the trigger device or the target device and then re-add them, you would have to re-create the association. But the minimote won't matter.
1 Like
these switches are no longer working with the stock device type generic zwave dimmer.
they update level and dimming based on chagnes digitally from the apps or control panel but the buttons on the actual switch do nothing.. I got it working with a port of my device handler from smartthings here
I also have the 9540. That one works fine as a Generic Z Wave Smart Dimmer. I was able to connect the 9542(which operates the same lights as the 9540) to the hubitat but it doesn't work as a Generic Z Wave Smart Dimmer. The physical switch itself also no longer turns on the same light. I've only had the hubitat for a month or so, so I'm not the most advanced at this. Does anyone have a suggestion to get the 9542 functional again?
This sounds like the issue I was having with the newer z-wave plus version (9640) I am still looking for a proper driver for that device, I had to take it out of service for now.
Have you tried my driver it should work
1 Like
I just tried it out and it's working now, thanks!
Also looks like my post including the model 9640 is now showing up in searches so hopefully others can find this solution as well 
1 Like
Okay seems some interest here. I have 8 for sale, 4 brand new, 4 barely used. 100.00 for the lot of them
