Back to Inovelli Guides
Inovelli

How to Fix Inovelli Multi-Tap Events Not Triggering in Home Assistant

Inovelli GuideSmart Switches
medium difficulty 15-20 minutes 84 views 0 found helpful Where this fix applies: North America, Selected international markets Updated
This guide applies to: Inovelli Inovelli Multi-Tap Events (Blue/Red series with HA (ZHA/Zigbee2MQTT/Z-Wave))
At a glance — most common causes
  • Scene control not enabled on the switch
  • HA/hub not decoding the action events
  • Automation listening to the wrong action
15-20 minutes13 solutions coveredmedium level

Expert Review & Technical Scope

DeviceInovelli Inovelli Multi-Tap Events
Model CoverageBlue/Red series with HA (ZHA/Zigbee2MQTT/Z-Wave)
Fix Time15-20 minutes
DifficultyMedium
Required Toolshome assistant logs, automation editor
Network / ProtocolZ-Wave

Problem Description

You double-tap or triple-tap the Inovelli switch paddle but nothing happens in Home Assistant — your automation does not fire. Multi-tap scene events require explicit enabling on the switch (disabled by default on some firmware), correct event trigger configuration in ZHA or Z-Wave JS, and current firmware. The switch also adds a 700ms delay to all taps when multi-tap is enabled.

Why This Happens in Real Homes

Inovelli multi-tap events not reaching Home Assistant is almost always a decoding or automation-mapping issue. The switch fires distinct events for double-tap, triple-tap, and so on (up and down), but they only work if scene control is enabled, the hub exposes those action events (in Zigbee2MQTT they appear as action strings), and your automation listens for the exact one.

Enable scene control on the switch, then watch the events in Home Assistant's developer tools (or the Zigbee2MQTT log) as you multi-tap to see the exact action payload the switch sends — then point your automation at that precise action (like "up_double"). Update the switch firmware and re-interview the device if the actions aren't exposed. Tapping with consistent timing helps the switch register the multi-tap cleanly.

Symptoms

  • Multi-tap not triggering in HA
  • Double/triple-tap does nothing
  • No multi-tap events
  • Taps not seen by Home Assistant
  • Multi-tap automations don't fire
  • Events missing in HA
  • Only single tap works
  • Multi-tap ignored

Recognize these? Here's what usually causes it.

Common Causes

  • Scene control not enabled on the switch
  • HA/hub not decoding the action events
  • Automation listening to the wrong action
  • Firmware outdated
  • Zigbee2MQTT action not exposed
  • Device needs re-interview
  • Debounce/timing on taps
  • Event payload mismatch

Most fixes happen in the first 3 steps.

Warning

Do not rely on outdated forum snippets without verifying current payload format.

Tools & Requirements

home assistant logsautomation editor

Step-by-Step Solution

1

Enable multi-tap detection on the switch

Multi-tap (double-tap, triple-tap, etc.) is disabled by default on some Inovelli firmware versions to reduce the single-tap delay. On the Blue Series (VZM31-SN): check Parameter 258 bit 0 — if set to disable multi-tap, the switch sends single-tap events immediately without waiting for additional taps. Enable multi-tap by setting the parameter to allow scene control. On the Red Series (LZW31-SN): Parameter 51 controls button delay — set to 1 to enable multi-tap. When enabled, the switch waits ~700ms after each tap to see if more taps follow.

2

Set up the correct event trigger in Home Assistant

For Z-Wave Red Series: use the 'zwave_js_value_notification' event trigger in your automation. Filter by node_id, property: 'scene', property_key: '001' (up paddle) or '002' (down paddle), and value: 'KeyPressed2x' for double-tap, 'KeyPressed3x' for triple-tap. For Zigbee Blue Series in ZHA: use the 'zha_event' trigger, filter by device_ieee, and command: 'button_1_double' for double-tap up, 'button_2_double' for double-tap down. The exact event names depend on your ZHA/Z-Wave JS version.

3

Test events in the Home Assistant event listener

Go to Developer Tools > Events > Listen to Events. Type 'zwave_js_value_notification' (Red Series) or 'zha_event' (Blue Series) and click Start Listening. Double-tap the switch paddle. The raw event data appears in the listener — copy the exact field names and values into your automation trigger. This eliminates guesswork about event names. If no event appears when you double-tap: multi-tap is not enabled on the switch (go back to the parameter configuration).

4

Check for the button delay tradeoff

Enabling multi-tap adds a ~700ms delay to all single-tap actions because the switch waits to see if a second tap is coming. If you find the single-tap delay unacceptable for daily light switching: consider using multi-tap only on the down paddle (configure the up paddle for instant on/off, reserve multi-tap for the down paddle or config button). On the Blue Series, you can also assign multi-tap to the config button (small side button) and keep the main paddle instant.

5

Update firmware for expanded multi-tap support

Early Blue Series firmware only supported single and double-tap. Firmware 2.15+ added triple-tap, quadruple-tap, and quintuple-tap scene events, plus held and released events on both paddles and the config button. Update firmware via OTA in Zigbee2MQTT (device > OTA tab > check for updates) or ZHA. After the update, re-interview the device (Z-Wave JS) or reconfigure it (ZHA) so Home Assistant discovers the new scene capabilities. Without the re-interview, the new multi-tap events may not register.

Quick Solutions

Enable scene control on the switch
Ensure the hub exposes the multi-tap action events
Match the automation to the exact action (e.g., 2x up)
Update the switch firmware
Check Zigbee2MQTT exposes the action
Re-interview/re-pair the device
Tap with correct timing/cadence
Verify the event payload in HA developer tools

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.

Pro Tip

Keep a reusable blueprint for known-good multi-tap mappings.

Real-World Insight

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.

What Usually Goes Wrong
  • Scene control not enabled on the switch
  • HA/hub not decoding the action events
  • Automation listening to the wrong action
  • Firmware outdated
  • Zigbee2MQTT action not exposed

Official Manufacturer Manual

Inovelli provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Inovelli Multi-Tap Events.

View Inovelli Multi-Tap Events Online Manual

Source: help.inovelli.com

Need More Help? Inovelli Support

Note: The contact information below connects you directly to Inovelli's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.