I had this tagged from forever ago, did you ever get this figured out?
I haven't looked at it since - the automation is running through an HE app instead.
@jtp10181 - playing with this again. Group 2 direct association works (the paddle). Group 3 does not (the button).
Has anyone made any progress with this?
I am using Home Assistant and getting the same issue. Direct associations with group 2 (dimmer switch) work, but associations set with group 3 (relay button) do not work.
I opened a ticket with Zooz a while back, and they are aware of the issue and said they plan on fixing it in the next firmware update.
2 Likes
@jtp10181 Two things: Zooz have fixed the firmware but it seems the relay is set for Group 4 now, not 3. I can send you the latest via pm, as it's still being uploaded to their repository.
Second thing: The child device doesn't work with your driver. It works ok with the built-in, so I used yours to set the association and have switched back for the time being.
You need the updated ZEN30 driver I posted recently, and probably need to run a configure so it can detect the endpoints correctly. They changed the endpoints and I tested it on the 800LR 4.10. They told me there was an update for the v3 in the works but never sent me the firmware.
You want this to show up in the states:
1 Like
Got it, thanks! Endpoints showing up now, and the child works as expected.
1 Like
Perfect, good to know. There are some new and changed settings as well, supposedly. Zooz told me the same settings they added in v4 would be in the 3.2 firmware. So hopefully that panned out, and I coded the driver to expose them when that firmware was released. If you were able to configure and not get stuck with pending changes afterwards the driver was able to set all the settings and get a response back from the device on each one, so must be working.
Well I've got 1 pending change with 3.2. I didn't want to use the 800 driver because... it's not the 800 model. But sounds like it doesn't matter.
Its not a special driver for the 800LR, it is universal. The updated driver in my HPM package is for all ZEN30 models from v1 to current.
If you want to enable debug logging and then press "Save Preferences" at the bottom it will show us what setting it is having problems updating (in the logs). Otherwise when I get a chance to update my device I will check it out as well. Looks like I might need another driver update to fix this.
1 Like
Oops, I meant to say 800 firmware, not 800 driver.
Looks like the pending change cleared up upon saving preferences. 
Now if you run configure once more it should clean up that mess of garbage in the States left from the system driver. I hate how they save all the parameters there, it bothers me especially since it is all obviously not sorted at all.
Yes you would not want to use the v4 firmware, it would probably brick the v3 device. Not sure how you would have gotten an 800LR (v4) firmware though, only the launch version 4.10 is out, unless that also has the same bug and they fixed it there and sent you both, not knowing which model you had.
Ah, I only noticed the v4 firmware listed on their changelog page, but looks like they aren't offering it separately as a file, which makes sense.
All cleared up.
I am trying to do something similar with the Zen52 and having issues since the Zen52 has two child relay switches and they get DNI's with a xxx-1 / xxx-2. When adding these composite DNIs to the group associations in Zen30, I get a warning in the logs that DNIs must be 2 digits.
SETUP:
Zen30 in smartbulb mode with line/load pigtailed in the box.
Zen52 installed in ceiling fan casing receiving constant power from Zen30 Circuit.
Goal: Have the 2 buttons on the Zen30 control the two relays on the zen52 in a reasonable amount of time.
Problem: Can't use device associations due to the composite DNI. Button Controllers are very slow or completely unresponsive to the physical button pushes on the zen30.
You would need a separate tool to set a multichannel association.
That being said, the button events should work fine. Do you have the scene events settings enabled and Are you seeing the button presses on the hub? Should show in logs and also events.
I assume you are using my community driver?
What kind of tool could I use? The button events are crazy slow.... Sometimes they work quickly, other times 20-30+ seconds. The device association is near instant, but the only thing I could get working was the DNI for the whole double relay, which turns on and off both relays.
I am using your driver with scene events enabled - thank you!!
I bought 8 of these switches unfortunately...so hoping to get them working rather than eating the cost
The button events should not be that slow, seems like some sort of z-wave mesh issue honestly.
For the associations, this tool will let you do multi channel:
[BETA] ZWave Tweaker port from ST
The second post has a brief guide on how to do it. Its a very rough port of a tool from Smart Things but it gets the job done.
I think someone else has a tool out there with a more polished interface, I forgot if it does multichannel though. Going to see if I can find it. FOUND IT but I don't think this one can do multi-channel so you are stuck with my Tweaker tool:
Need direct ASSOCIATIONS - #3 by MrFarmer
Thank you -- I will try it out!
How do you identify and fix a mesh issue? Originally I had 3 ghost devices that I was able to exclude. Are there other potential issues? This project has about 60 zwave devices, so coverage is fantastic. This particular device is probably the farthest from the hub, but has lots of neighbors who have no issues.
What hardware version (or firmware) is the ZEN30? The v1 had a horrible antenna and gets very bad range.
If you want feedback on the mesh, make a new post with screenshots of the full z-wave details page and the red/blue topology. Also include the hub uptime (since last reboot). Uptime should be at least 12 hours for stats to accumulate. (Current 2.3.9.196 platform also has a bug where stats are not fully populating so...)
