How to Fix Inovelli Scene Button Hold Actions Not Triggering
- Scene control not enabled
- Hold action not exposed/decoded by the hub
- Automation listening to the wrong action
Problem Description
You press and hold the Inovelli switch paddle expecting a Home Assistant automation to fire, but nothing happens. Hold events require firmware 2.15+ on the Blue Series, proper event trigger configuration in ZHA or Z-Wave JS, and sufficient hold duration (500ms+). Smart Bulb Mode can also change how hold events are processed.
Why This Happens in Real Homes
Inovelli press-and-hold scene actions work like the multi-tap ones — the switch fires a distinct "held" event (up or down) that your hub turns into an automation trigger — so a hold that doesn't trigger usually means scene control isn't enabled, the hub isn't decoding the hold action, or the automation isn't listening for it. On a dimmer, holding also ramps brightness, which can mask the scene event.
Enable scene control, then watch the events as you hold the paddle to capture the exact hold action payload, and point your automation at it. Update the firmware and re-interview the device if the action isn't exposed. Remember that on a dimmer, a hold both dims the load (unless in Smart Bulb Mode) and sends the hold scene event, so both behaviors coexist. Holding long enough for the switch to register the action matters too.
Symptoms
- Hold action doesn't trigger
- Press-and-hold does nothing
- No hold events
- Hold not registering as a scene
- Hold automations don't fire
- Only tap works, not hold
- Hold ignored
- Held paddle no event
Recognize these? Here's what usually causes it.
Common Causes
- Scene control not enabled
- Hold action not exposed/decoded by the hub
- Automation listening to the wrong action
- Firmware outdated
- Hold conflicting with dimming (dimmer)
- Device needs re-interview
- Hold duration/timing
- Event payload mismatch
Most fixes happen in the first 3 steps.
Do not assume old automation blueprints include current hold-event schema.
Tools & Requirements
Step-by-Step Solution
Verify hold events are supported on your firmware
Hold (press and hold) and release events require specific firmware. On the Blue Series (VZM31-SN): firmware 2.15+ supports held and released events on up paddle, down paddle, and config button. Earlier firmware only fires held events on the config button. Check your firmware version in Zigbee2MQTT (device About tab) or ZHA (device info page). Update firmware if an older version is installed. On the Red Series (LZW31-SN): hold events are supported from factory firmware, but Parameter 51 (button delay) must be set to 1 (enabled).
Configure the correct hold event trigger
In Home Assistant for Z-Wave Red Series: create an automation with trigger type 'zwave_js_value_notification'. Filter by node_id, property 'scene', property_key '001' (up) or '002' (down), and value 'KeyHeldDown' for hold start and 'KeyReleased' for hold end. For Zigbee Blue Series in ZHA: use 'zha_event' trigger with command 'button_1_hold' (up hold) or 'button_2_hold' (down hold). Use the Developer Tools event listener to capture the exact event payload from your switch.
Distinguish between tap and hold events
The switch determines whether a press is a tap or a hold based on how long you keep the paddle pressed. A quick press and release (under 500ms) is a tap. Pressing and holding for 500ms+ triggers a hold event. If you release too quickly, the switch registers a tap instead of a hold. Practice holding the paddle firmly for at least 1 second to reliably trigger hold events. The LED bar on the Blue Series shows a visual indicator (the bar fills up) when a hold is detected.
Check for Smart Bulb Mode conflicts
When Smart Bulb Mode is active (Parameter 258 on Blue Series): the paddle behavior changes. Taps send scene events instead of toggling the relay. Holds typically still work for dimming in Smart Bulb Mode, but the hold event type may differ. If Smart Bulb Mode is off: holding the up paddle physically ramps the dimmer up (the light gets brighter), and the scene hold event may fire simultaneously or not at all depending on firmware. Test with Smart Bulb Mode both on and off to see which configuration reliably fires your hold automation.
Use config button holds as an alternative
The config button (small button on the side of the Inovelli paddle) supports hold events on all firmware versions. Pressing and holding the config button for 2+ seconds fires a config button held event. This is useful for triggering automations that you do not want to accidentally fire from the main paddle (like activating a scene or toggling a different room). In Z-Wave JS: the config button is property_key '003'. In ZHA: it is 'button_3_hold'. The config button does not control the relay or dimmer — it only sends scene 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.
Hold actions often use different payload keys than tap actions.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Scene control not enabled
- Hold action not exposed/decoded by the hub
- Automation listening to the wrong action
- Firmware outdated
- Hold conflicting with dimming (dimmer)
Before you go — try one of these (they fix most cases).
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 Hold Actions.
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.