How to Fix Inovelli Automation Triggering Twice
- Switch sending duplicate scene events (firmware)
- Automation has multiple matching triggers
- Both a state and an event trigger firing
Problem Description
Your Inovelli switch (Blue Series VZM31-SN or Red Series LZW31-SN) triggers the same Home Assistant automation twice with a single paddle press. The switch sends scene events on both button press and release — if your automation listens for the generic scene event without filtering by action type, it fires twice. Duplicate Z-Wave integration instances or ghost nodes causing command retransmissions can also cause double triggers.
Why This Happens in Real Homes
An Inovelli automation triggering twice is usually caused either by the switch emitting a duplicate scene event (a firmware issue) or the automation itself having overlapping triggers — for example, both an event trigger and a state trigger firing on the same action, or two automations matching the same event.
First rule out duplicate events by updating the switch firmware and checking the hub log to see if one tap produces two events. Then audit the automation: make sure it has a single, tightly-scoped trigger (not both a state and an event trigger for the same thing), and that no duplicate automation exists. Setting the automation to single-run mode prevents a second concurrent execution. Current firmware plus one clean trigger gives one action per tap.
Symptoms
- Automation triggers twice
- Runs twice per tap
- Double execution
- Automation fires two times
- Duplicate automation runs
- Action happens twice
- Two triggers per event
- Repeated automation
Recognize these? Here's what usually causes it.
Common Causes
- Switch sending duplicate scene events (firmware)
- Automation has multiple matching triggers
- Both a state and an event trigger firing
- Event processed twice by the hub
- Duplicate automations
- Retransmission on the mesh
- Trigger not scoped tightly
- Config causing double-fire
Most fixes happen in the first 3 steps.
Do not stack state and event triggers for same user action unless required.
Tools & Requirements
Step-by-Step Solution
Check for duplicate scene event subscriptions
Inovelli switches (Blue Series VZM31-SN, Red Series LZW31-SN) send scene events on both press and release. If your automation triggers on the generic 'scene activation' event without filtering by action type, it fires twice — once on press, once on release. In Home Assistant: check your automation trigger. Change from 'event: zwave_js_value_notification' (which catches all events) to specifically filtering KeyHeldDown or KeyPressed. For Zigbee Blue Series: filter the ZHA event by command type — 'button_1_single' fires once, but a generic scene trigger fires for both press and release.
Check for multiple integration instances
If you migrated from one hub to another (SmartThings to Home Assistant, or Z-Wave JS to ZHA) and the old integration still has the device: both integrations may fire events for the same physical button press. In Home Assistant: go to Settings > Devices & Services. Check that the Inovelli switch only appears under one integration. If it appears under both Z-Wave JS and ZHA (for example, if you switched from Z-Wave Red to Zigbee Blue Series): remove the device from the old integration.
Disable the button delay if using instant scene events
By default, Inovelli switches have a 700ms delay after a single tap to wait and see if a double-tap follows (multi-tap detection). Some automations trigger on 'scene 1 pressed' at the 700ms mark when the switch determines it was a single tap. If you then also have a 'switch turned on' automation, both fire. Fix: decide whether you want to trigger on the scene event or the on/off state change — not both. If you only need single and double tap: use scene events. If you only need on/off: use state change events and ignore scene events.
Check for ghost Z-Wave nodes causing retransmissions
On the Red Series (Z-Wave): ghost nodes in the Z-Wave network cause command retransmissions. When the switch sends a scene event, the Z-Wave controller retries delivery if it does not get an ACK. The controller may process the same event twice — once from the original transmission and once from the retry. In Z-Wave JS: go to the network map and look for nodes showing 'Dead' or 'Unknown' status. Remove ghost nodes using the 'Remove Failed Node' function. This cleans up the mesh routing and eliminates duplicate message processing.
Add a deduplication guard in your automation
If you cannot eliminate the root cause: add a deduplication condition to your automation. In Home Assistant: use a 'condition' that checks if the automation last triggered more than 2 seconds ago, using 'last_triggered' in a template condition. This filters out the duplicate event that arrives within milliseconds of the first. Template: '{{ (now() - state_attr('automation.your_automation', 'last_triggered')).total_seconds() > 2 }}'. This is a workaround, not a fix — identify and address the root cause when possible.
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.
Use idempotent automation design for event-heavy switch 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.
- Switch sending duplicate scene events (firmware)
- Automation has multiple matching triggers
- Both a state and an event trigger firing
- Event processed twice by the hub
- Duplicate automations
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 Duplicate Triggers.
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.