Hi everyone; just started populating my Zooz devices onto HASS and am running into a weird conundrum with virtual 3 ways. I’ve been able to do it with “simple” devices (like a Zen72 and Zen 77) but cannot get a Zen77 and Zen35 to work together. I have a Zen77 connected to the load and works great, and then a Zen35 Scene Controller that I want to use as a remote. Unfortunately I can’t seem to find the right combination of Group, Target Node, etc to make it work.
(FYI - I don’t work for Zooz, and don’t have this exact setup in front of me, but…)
I’d try building two associations:
Root / Main Button - Pressed (Basic Set)
and
Root / Main Button - Held (Multilevel)
and assign both to the ZEN77, target endpoint set to ‘no endpoint’ and see how that works.
My thought is the basic will give you off/on, and the held will give you the multilevel.
I do recall there being something about virtual multi-ways preferring (but maybe not requiring?) a ZEN72. This may be a limitation in using the 77 for this purpose…
Read this:
Reading between the lines in that document, I would try enabling smart bulb mode on the ZEN35 as well. (Set Parameter 19 to 0 )
Parameter 19: Enable or disable physical and Z-Wave on/off and dimming control. Disable both physical button and Z-Wave control for smart bulbs (use central scene triggers). Scene control and other functionality will still be available from the button.
Values: 0 – Disable button; 1 – Enable button and Z-Wave; 2 – Disable button and Z-Wave. Default: 1.
I have several ZEN77s working as virtual dimmers in pairs and triplets. It works great, better than using a rule on a hub to trigger then send action to other dimmer. In my solution is all the devices are the same model number.
I believe for virtual dimming to work all the associated devices must be multi level devices. In otherwords they all have to have group 3 functionality. You can’t have a group 2 device (on/off switch) control a dimmer as a remote dimming location. Someone from Zooz can probably clarify it a little better than I have but I believe this is why your setup isn’t working.
I think you can set up the zen35 to turn on/off the dimmer but not control dimming level…
A Group 2 device cannot send a dimming command to a Group 3 device
because devices do not communicate between association groups. [1]
Association groups are lists of target devices stored inside a single source device. The source device sends specific commands to the targets inside those groups based on what physical action you take. [1, 2]
How Association Groups Communicate
Group 2 sends Basic Commands: When you tap a button on the source switch, it sends basic On/Off commands to any target device listed inside its Group 2. It cannot send dimming commands. [1]
Group 3 sends Multilevel Commands: When you press and hold a button on the source switch, it sends Dim Up/Down commands to any target device listed inside its Group 3.
Devices do not talk group-to-group: A device placed inside Group 2 only listens to the source switch. It cannot see or talk to a device placed inside Group 3.
How to Achieve Dimming Between Devices
To make a target device dim along with your main switch, you must add that target device directly into the source device’s Group 3 (or the group designated for “Multilevel Switch” commands in your device’s manual). [1]
If you want to see if your specific hardware supports this, tell me the brand and model number of both your main switch and your target light. I can look up their exact manuals and group definitions for you.
ahhh my bad thought ZEN35 was the high power on/off switch… Should work then , maybe some trick to setting up the ZEN35 association group due to mix of scene control buttons and a dimmer button. idk
I just mocked this up in my lab with the ZEN77 controlling a light, and the ZEN35 setup for remote control and it worked out of the box with no special parameters. Both on/off and dimming. (Using HA JS UI)
However the two would get out of sync, so to clean that up, I added associations backwards as well, and set one parameter on the ZEN35 (P 19 to 0)
Below are my associations that worked for bi-directional control that stayed in sync. (note that these were out of the box and not upgraded to the latest firmware since this was just a quick test).
(You could argue that the multilevel should also be set from ZEN77 to ZEN35 but that may be overkill, depending)
[The Zooz team can let us know if there is a better way… this was just my quick functional mock-up…] (They did - screenshots above edited)
If this isn’t working for you, I’m wondering if there is something else going on… are both switches at the same security level (S2, ideally)? And of course they both need to be in mesh (non-LR) mode, but I think JS UI would prevent you from building the groups in that case. If that all checks out, maybe try re-interviewing both devices as well. Good Luck!
Have you tried the Zooz Support Portal? You can enter a ticket (it’s the ‘Contact Us’ selection at the top of page) and I’ve found they usually respond within the same day. Also, @Sara from Zooz is often here on the Zooz Community and perhaps she’ll see this post…
Hm this is very strange, I still cannot get them to work. I’ve even tried re-adding the ZEN35 from scratch just in case there was some lingering information.
Can you post screenshots of both devices (like the example below) so we can see versions, etc?
Also a small bug in your setup but not critical, The association from the 77 to the 35 needs to be using the ‘root’ endpoint, rather than “none”. But this would only effect on/off syncing not general functionality.
I should also add, I’m a professional lighting designer for very large events and concerts. I can remotely control hundreds of robotic lighting fixtures while it’s raining in a field…this is very frustrating lol
So the other thing I can say is even with Relay Control disabled, if I press and hold the ZEN35’s main button I can hear the relay activate, which seems…wrong? Configuration screenshots attached.
ok…I’m now on the same versions as you. Immediately after the upgrade the associations were not working. I deleted them and re-added and they started working again.
My only other thoughts:
On the ZEN35, ensure that P 35 is set to 1 (enable). If disabled, this will stop it from working.
Well that seems to work better! Still having some weird delays and issues responding but at least there’s now some control…
Are there any other configuration settings I should look into to make it respond better? I still hear the relay clicking on and off even though I have Relay Control set to disabled.
Occam’s razor and all…
