'bout to give up - can't find a resolution to direct association for the Zen34s... now just throwing in the towel and looking for simple rule or app. Shame, liked the fact that I could use them for certain plugs on generator if the power was out and hub was off line
Did you ask @jtp10181 yet? King of Zooz around here... 
1 Like
I never made a driver for that once since @bertabcd1234 has one and no one was complaining. It looks like it has support for setting associations.
1 Like
I must have accidentally left that command in there when I was playing around with the idea but never actually implemented it. 
2 Likes
Oh... well maybe it doesn't work then.
I have it implemented on my ZEN37 driver. That driver could be adapted to the ZEN34 with some adjustments.
Thanks all! I thought about Jeff’s and I did try Bert’s driver too 
I guess I should add I was using the advanced driver from zooz prior. And the direct associations were still intact before I excluded and readded. I have other wired switches (which are using Jeff’s other drivers) that are also intact - but I don’t want to sacrifice excluding one and not getting it back.
I’ll have to find a stand alone I don’t care about to experiment with and report back
This tool should work for battery devices according to the person who forked my ported code. [BETA] ZWave Tweaker port from ST - #3 by scrool
I know there is a cleaner tool as well that someone made, I am trying to find it.
Found the other one: Need direct ASSOCIATIONS - #3 by MrFarmer
1 Like
I've done it.
Just remember, reaction time will be very slow if there is no power to the hub.
Something about it waits to check for hub connection....something like that.
If hub has power, even no net, works normal.
tried the second version - no go, direct associations just wont take - thanks for the research though
I'm having trouble making the association set commands work in my ZEN34 driver on Z-Wave JS. No errors, they just aren't taking. It's quite likely me, but it's possible something isn't right on the new stack. I'll try on legacy (probably on another hub) to make sure, unless someone else can confirm with some driver that this works with Z-Wave JS as the engine, in which case I'll go back to my assumption that it's me.
1 Like
same result here with any driver i've tried- it just doesnt take. The logs give the impression it should but something won't stick
I just tried a 700 series Zen77 using Jeff's advanced dimmer driver and direct assoc wont take on it so I guess it safe to say the Z-wave JS is common element
If you are on JS and anything is not working right, first test is switch back to legacy ZIP and try again. We had tons of issues like this in beta but obviously did not catch everything.
The only thing hat wasn’t showing a good connection after switching was the zen34 and door sensor so I just excluded and readded - now everything good but the direct association- not sure if switching back to legacy and back to Js again wouldn’t just repeat the same process again?
No, once the ZwaveJS database is populated and everything is working it would come right back to how it was if you switch. Both gateways have a separate database and they are retained when you switch.
Same code on legacy (Z/IP Gateway) works for me, so something was probably missed with Z-Wave JS here. Good to know I could have saved a ton of time testing last night thinking it was me... 
Working with Bryan on this.
That being said, association is pretty rarely used on Hubitat, if this isn't any indication. I wasn't really inclined to add it to the driver for this reason, plus the fact that it's not supported on LR (which I suspect people will start to use more and more as more devices support it, including this one) and it requires some care (e.g., removing associated node IDs yourself if they are removed from the hub to avoid possible problems). But...it's there now!
3 Likes
Yes rarely used but it does have some good use cases. In some cases you can get much better dimming with associations. Also possibly having all your leak sensors associated to a water valve to turn it off even if hub is down. I feel like almost everything else can just be done with rules.
Interesting.
Again, though, with the old z-wave, I think it would take, like, twenty seconds for a command to go from device to device if the hub was unplugged.
not quite following?
ok was away most of the weekend and didn't have a chance to play w/ this - but if I'm reading this right - i think you're saying I could switch back to Zip, add the direct assoc, then switch back to JS... which I assume is why my other direct associations continue to work since they remained in the devices internal db but these remotes were cleared when i excluded.
A working command (well, working on legacy Z-Wave, at least...) to add/remove associations was added to the driver update that I released on the day I wrote that post.
ah ok - I didn't read the comment in the drivers code until now! I see where you noted " 2025-04-05: Implement association support" but thanks for clarifying that is for legacy, I thought I was missing something still trying to get it to apply to JS
