Why Is Inovelli Switch Sending Duplicate Scene Events?
- Multiple event subscribers
- Driver emits translated + raw events
- Debounce settings too permissive
Problem Description
When your Inovelli Inovelli Duplicate Scene Events isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- Automation fires twice
- Two events per tap
- Intermittent duplication
Recognize these? Here's what usually causes it.
Common Causes
- Multiple event subscribers
- Driver emits translated + raw events
- Debounce settings too permissive
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
Inspect raw event stream
Identify whether duplicates are upstream or automation-layer.
Remove redundant listeners
Keep one authoritative event source for scenes.
Retest tap patterns
Verify single and multi-tap actions fire once.
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.
- Multiple event subscribers
- Driver emits translated + raw events
- Debounce settings too permissive
Before you go — try one of these (they fix most cases).
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.