How to Program the ZEN35 Scene Dimmer on HomeSeer

So your ZEN35 Scene Dimmer is properly included and you're ready to program it? Read on!

Zooz products are officially integrated with the Z-Wave Plus and the Z-Wave JS Front-End of HomeSeer. If you're experiencing issues with accessing the advanced settings of your device or the unit not properly displaying, we would recommend first updating to the Z-Wave Plus or the Z-Wave JS Front-End, then excluding and re-including your device to your network in order for it to be recognized correctly.

The Zooz ZEN35 is a powerful Z-Wave dimming scene controller featuring five customizable physical buttons. Each button can be individually programmed to trigger automations through Central Scene commands or to directly control other Z-Wave devices using Direct Association. This dual-mode capability allows users to choose between flexible, hub-based automation logic or simple device-to-device control. Whether you're aiming to activate complex Home Assistant scenes or simply control a nearby light switch, programming the ZEN35 offers a smart and adaptable solution for seamless home automation.

Below, we'll cover what Central Scene and Direct Association are and how you can program either option on Home Assistant. Scroll to the bottom of the article for instructions on programming the LED indicators to reflect the status of the controlled device.

Central Scene / Scene Control

Each button on the ZEN32 sends a unique Scene Number, allowing Home Assistant to recognize which of the five buttons was pressed. What makes this controller especially versatile is its use of Key Attributes, which identify the type of interaction—such as a single tap, double tap, hold, or release. These combinations of Scene Numbers and Key Attributes give users granular control over automations, enabling one button to perform multiple functions based on how it's pressed. For example, a single tap might turn on a light, while a hold could dim it, and a double tap could activate an entire scene.

Scene Numbers and Button Mapping

Here's how the ZEN35 buttons are mapped to Central Scene scene numbers:

Button	Scene Number	Description
Dimmer Button	`5`	The large center button
Button 1	`1`	Small button, top left
Button 2	`2`	Small button, top right
Button 3	`3`	Small button, bottom left
Button 4	`4`	Small button, bottom right
ZAC99 (if used in 3-way)	`6`	Reports separately when used

Each button supports 7 key attributes (aka action types):

Key Attribute	Action Type
0	Key Pressed Once
1	Key Released
2	Key Held Down
3	Key Pressed 2x
4	Key Pressed 3x
5	Key Pressed 4x
6	Key Pressed 5x

So for example:

Pressing Button 1 once = Scene 1, Key Attribute 0
Holding Switch Button = Scene 5, Key Attribute 2
Double tapping Button 3 = Scene 3, Key Attribute 3

ZEN35 + ZAC99 Momentary in 3-Way Setup

Are you looking to have scene control options or dimming from the other locations when installing the ZEN35 in a multi-way location? You can use the ZAC99 Momentary switch in the other location(s) in your multi-way installation and use the reported events to trigger scenes.

This option is not available from a standard, dumb on/off switch because the ZEN35 is designed to trigger scenes based on momentary inputs—quick presses that send a signal to activate a programmed scene. A standard "dumb" on/off switch physically changes the electrical state (open or closed circuit) instead of providing the momentary signal input. With a momentary switch like the ZAC99, the ZEN35 consistently receives clean, simple press events it can interpret correctly to trigger scenes, ensuring smooth and reliable scene control.

The ZAC99 is SPST and only the top portion of the switch is pressed. If you click the switch once, it will turn on. If you press and hold it while it's on, it will decrease brightness. If you click it again, it'll turn off. Once off, when you press and hold it will increase brightness.

If you're wiring a ZAC99 momentary switch to the ZEN35 to control it from another location (e.g. a 3-way circuit), the ZAC99 will trigger Scene 6 with the same key attributes:

Device	Scene Number
ZAC99	`6`

This allows the hub to recognize the input from the remote switch and automate accordingly.

For example:

Tapping ZAC99 once = Scene 6, Key Attribute 0
Holding ZAC99 = Scene 6, Key Attribute 2

This gives you full automation capability from both the ZEN35 and the auxiliary switch location.

Summary

The ZEN35 uses scene numbers 1–5 for its built-in buttons.
Each button supports 7 types of press actions via key attributes.
If a ZAC99 momentary switch is wired for remote control, it reports as Scene 6.
Your hub can create distinct automations for each combo of button and press type.

Multi-tap triggers can be assigned to all buttons on the ZEN35, including the main switch button, whether you have a load connected to it or not.

Programming Central Scene

1. Select Events:

2. Click on the + symbol to add new event and name it:

3. Select Newly Made Event and go through drop down menus. We recommend selecting the device first, "Central Scene" variant

4. Make sure to select the trigger type as listed for scene control. The trigger VALUE is for specific function requested that triggers the scene:

5. Go through "THEN" drop down menus, selecting the type of action to be done, i.e. "control a device":

6. Select the device/s to be controlled or affected:

7. Select the specific action to be taken (on, off, dimmer % etc.):

Direct Association

Direct association is a direct link established between two Z-Wave devices where one of them acts as the trigger and the other acts as the receiver of that trigger. For example, if you associate a Z-Wave light switch to a motion sensor, the light switch will turn on anytime motion is triggered, without the hub getting involved or without the need to set up an automation for it. In other words, one Z-Wave device sends a direct message to another Z-Wave device, bypassing the hub. These are usually very simple unconditional commands like "on/off" or "dim/increase brightness". The communication works one way without any feedback to the other device. The controlling device simply sends the command to the controlled device or devices associated in what we call "association group". The controlling device is not affected by the controlled device at all, even though there is a link established between the two, it only ever works in one direction. You can read more about the requirements, limitations, and recommendations for programming using Direct Association here.

Associations Groups

The association groups supported by the ZEN35 can be found in the device manual, in the Advanced Settings document, and we've included them below as well:

Group 1: Lifeline to hub

Group 2: Main button basic set (pressed only, doesn't send anything when switch turned on via hub)

Group 3: Main button multilevel set (held)

Group 4: Main button multilevel start / stop

Group 5: Small button #1 basic set

Group 6: Small button #1 Multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level

Group 7: Small button #2 basic set (pressed)

Group 8: Small button #2 Multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level

Group 9: Small button #3 basic set (pressed)

Group 10: Small button #3 Multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level

Group 11: Small button #4 basic set (pressed)

Group 12: Small button #4 Multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level

Programming Direct Association

We've included a programming example below using the ZEN77 triggering the ZEN04, but associations will be programmed the same for the ZEN35.

Important Considerations

Before attempting association, double check that both devices are added with the exact same level of security; if one device is included with S2A and one is included with S0, the association will not be available.
Please also note that Direct Association is not an option if the device is included via Z-Wave Long Range. ZWLR is device-to-hub direct communication; there are no repeaters and no mesh and the ZWLR devices do not communicate with each other, so direct association programming is not an option for devices included via ZWLR.

1. Select Plugins:

2. Select Z-Wave Plus and click "Manage Associations":

3. Go through drop down menus, selecting the Z-Wave network, devices to be associated, and the association group:

4. A message will appear below saying if the association was successful or if an error was encountered:

Please let us know if you have any questions!