Why Is Inovelli Switch Sending Duplicate Scene Events?
- Firmware bug causing duplicate reporting
- Device reporting the event twice
- Hub/integration re-processing
Problem Description
Your Inovelli switch fires the same Home Assistant automation twice with a single paddle press. The switch sends both a KeyPressed and KeyReleased event per tap, and if your automation does not filter by event type, it triggers on both. Z-Wave ghost nodes, Supervision retransmissions, and duplicate device entries can also cause duplicate events.
Why This Happens in Real Homes
An Inovelli switch sending duplicate scene events — the same tap firing an automation twice — is often a firmware issue where the device reports the event more than once, or the hub/automation processing the same event multiple times. Zigbee/Z-Wave retransmissions on a marginal mesh can also duplicate messages.
Start by updating the switch firmware, since duplicate scene reporting has been addressed in updates. Check your hub's logs to see whether the switch actually sends two events or the automation is triggering twice on one, and if it's the automation, add a de-duplication guard (single-run mode or a condition/delay). Heal the mesh to reduce retransmissions, and remove any duplicate bindings or event listeners. Current firmware plus a clean automation trigger stops the doubles.
Symptoms
- Duplicate scene events
- Same event fires twice
- Double scene triggers
- Automation runs twice
- Event sent multiple times
- Duplicate multi-tap
- Repeated scene events
- Scene fires more than once
Recognize these? Here's what usually causes it.
Common Causes
- Firmware bug causing duplicate reporting
- Device reporting the event twice
- Hub/integration re-processing
- Automation triggering on multiple events
- Zigbee/Z-Wave retransmission
- Config/binding duplication
- Multiple listeners on the event
- Mesh causing message duplication
Most fixes happen in the first 3 steps.
Do not stack raw and translated scene triggers for same action.
Tools & Requirements
Step-by-Step Solution
Filter by press vs. release events
Inovelli switches send two events per tap: one on press (KeyPressed) and one on release (KeyReleased). If your automation triggers on the generic 'zwave_js_value_notification' (Z-Wave) or 'zha_event' (Zigbee) without filtering the value/command field: it fires twice — once for press, once for release. Fix: in your automation trigger, add a condition to only fire on 'KeyPressed' (Z-Wave) or the specific 'button_X_single' command (ZHA). This filters out the release event.
Check for Supervision-related retransmissions
Z-Wave Supervision is a command class that requires the receiving device to acknowledge receipt. If the acknowledgment is lost (weak signal, interference): the controller retransmits the command, and the switch sends the scene event again because it processed the command twice. In Z-Wave JS: check if Supervision is enabled for the switch (device > configuration). Disabling Supervision for scene events may reduce duplicates, but also means commands are not confirmed. Test with Supervision off to see if duplicates stop.
Remove ghost Z-Wave nodes
Ghost nodes cause the Z-Wave controller to send explorer frames and retries when trying to route through the non-existent device. These retries can cause the controller to receive the same scene event multiple times through different routes. In Z-Wave JS: go to Settings > Devices and look for nodes with 'Dead' or 'Unknown' status. Click the node > 'Remove Failed Node.' After removing ghosts, heal the switch's route to establish a clean path to the controller.
Check for duplicate device entries in Home Assistant
If you migrated between hubs or integration versions: the same physical switch may have two device entries in Home Assistant. Both entries receive and fire events for the same physical button press. Go to Settings > Devices > search for the Inovelli switch. If two entries exist: one is likely old/stale. Delete the stale entry and update any automations referencing it. Only one device entry per physical switch should exist.
Add deduplication logic if nothing else works
If the root cause cannot be eliminated: add a deduplication condition to your automation. Use a template condition that checks the time since the automation last triggered: '{{ (now() - state_attr('automation.your_name', 'last_triggered')).total_seconds() > 2 }}'. This blocks the duplicate event that arrives within 2 seconds of the first. Alternatively, use an 'input_boolean' as a lock: the automation sets it to ON when triggered and an 'automation.turn_off' timer resets it after 3 seconds. Any trigger while the boolean is ON is ignored.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Scene reliability improves when one event source is canonical.
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.
- Firmware bug causing duplicate reporting
- Device reporting the event twice
- Hub/integration re-processing
- Automation triggering on multiple events
- Zigbee/Z-Wave retransmission
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 Scene Events.
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.