How to Fix Zooz Double-Tap Not Triggering Automations
- Scene config disabled
- Automation listening to wrong event
- Driver changed
Problem Description
Double-tapping your Zooz switch paddle does not trigger the expected Home Assistant or Hubitat automation. Scene control (Central Scene CC) must be enabled via Parameter 12, the automation trigger must listen for scene events rather than state changes, and firmware bugs in older versions may cause unreliable scene reporting.
Why This Happens in Real Homes
Double-tap automations rely on Central Scene control, which on Zooz switches stays off until you enable it in Parameter 12, and the automation has to listen for the exact scene event. In real Hubitat and Home Assistant setups people forget Parameter 12 or subscribe to the wrong button event. Enable scene control on the device, then point the automation at the right key attribute.
Symptoms
- Single tap works
- Double tap ignored
- Logs show no scene events
Recognize these? Here's what usually causes it.
Common Causes
- Scene config disabled
- Automation listening to wrong event
- Driver changed
Most fixes happen in the first 3 steps.
Do not assume old event names remain unchanged after integrations update.
Tools & Requirements
Step-by-Step Solution
Enable scene control on the Zooz switch
Double-tap, triple-tap, and held paddle events are Z-Wave Central Scene commands. On most Zooz switches, scene control must be explicitly enabled via a configuration parameter. For ZEN7x series: Parameter 12 = 1 enables scene control. For older ZEN2x series: check your model's manual. In Home Assistant Z-Wave JS: go to the device > Configuration > Parameter 12, set to 1. In Hubitat: device Preferences > Enable Scene Control. Without this parameter enabled: the switch only sends basic on/off reports and does not generate scene events for multi-tap actions.
Set up the correct automation trigger
In Home Assistant: use an Event trigger with event_type: zwave_js_value_notification. Filter by: node_id (your switch), property: scene, property_key: '001' (up paddle) or '002' (down paddle), and value: 'KeyPressed2x' (double-tap). In Hubitat: use a 'Button' trigger — double-tap up = button 1 pushed twice, double-tap down = button 2 pushed twice. The exact button mapping varies by hub platform. Do not use a state change trigger (on/off) — state changes only fire on single tap, not multi-tap scene events.
Test scene events in the hub's event log
Before building an automation: verify that the switch actually sends scene events. In Home Assistant: go to Developer Tools > Events, subscribe to zwave_js_value_notification, then double-tap the paddle. You should see an event with the scene and key count values. In Hubitat: go to the device page > Events tab, double-tap, and check for button events. If no scene event appears: Parameter 12 is not enabled, or the firmware does not support scene control (update firmware from getzooz.com).
Check for paddle timing issues
Double-tap requires two quick presses within about 500ms. If you press too slowly: the switch registers two single taps instead of one double-tap. Practice a quick rhythmic double-tap — think of it like a computer mouse double-click speed. Some Zooz models let you adjust the multi-tap timing window via a configuration parameter (check your model's advanced parameters). If double-tap works inconsistently: you may also be accidentally triggering a triple-tap. Check the event log for the actual key count value received.
Update firmware for reliable scene reporting
Early firmware versions on ZEN71, ZEN72, ZEN76, and ZEN77 had bugs where multi-tap scene events were not sent reliably — especially after power outages or parameter reconfigurations. Download the latest firmware from getzooz.com/firmware for your model. The ZEN77 v10.20+ and ZEN76 v10.20+ firmwares include improvements to scene reporting timing and reliability. After updating: re-enable Parameter 12 (firmware updates sometimes reset parameters to defaults) and re-test double-tap events.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Keep one test automation dedicated to double-tap validation.
Home Assistant issues that only appear after restart are a well-known quirk — triggers that require prior state history simply can't fire until that history rebuilds.
- Scene config disabled
- Automation listening to wrong event
- Driver changed
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Zooz provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Zooz Multi-Tap Actions.
Source: help.zwaveproducts.com
Need More Help? Zooz Support
Note: The contact information below connects you directly to Zooz's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.
Accessories owners commonly pair with Zooz Multi-Tap Actions.
Zooz 800 Series Z-Wave Long Range S2 Motion Sensor ZSE18 ...
Zooz 800 Series Z-Wave Long Range Open|Close XS Sensor ZS...
Zooz 800 Series Z-Wave Long Range Temperature | Humidity ...
As an Amazon Associate we earn from qualifying purchases.
