How to Fix Inovelli Scene Control Not Working
- Scene feature disabled in device config
- Wrong integration/driver selected
- Automations mapped to wrong event fields
Problem Description
Inovelli switch controls load normally but scene actions like double tap or hold do not trigger automations. This typically results from scene mode configuration gaps, wrong hub integration mapping, or automations listening to incorrect event payloads.
Symptoms
- Switch controls light but scenes do nothing
- Double tap actions never trigger
- Only one scene action works
- Worked in old hub but not new one
- Event appears missing in logs
- Scene fails after driver migration
Recognize these? Here's what usually causes it.
Common Causes
- Scene feature disabled in device config
- Wrong integration/driver selected
- Automations mapped to wrong event fields
- Hub does not expose multi-tap payload correctly
- Stale entity after re-inclusion
- Firmware/event schema mismatch
Most fixes happen in the first 3 steps.
Do not assume one working tap means all scene events are healthy. Validate every multi-tap action separately.
Tools & Requirements
Step-by-Step Solution
Confirm model and integration path
Identify exact Inovelli series and ensure your hub uses the recommended driver/integration. Scene payload behavior differs by stack, and basic load control can work while scene events remain unavailable if integration mapping is wrong.
Enable scene-capable settings
Open device settings and verify scene/multi-tap options are enabled. Save and apply changes, then run any required configure/interview action. Without this, taps may never emit events even when the switch appears healthy.
Inspect event logs directly
Trigger tap patterns and watch raw logs to see which event names and fields are emitted. Use this live payload as automation source of truth. Many failed automations come from using outdated community examples tied to old event schemas.
Rebuild automation triggers
Update automations to current event payload keys, including button number and action type. If device was replaced or re-included, remove stale references and bind to current entity/device ID to avoid silent trigger misses.
Update firmware and final test
Apply stable firmware and re-test single, double, and hold actions for both paddles. Document working event map so future updates or migrations can be validated quickly with the same test matrix.
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.
Create a small scene-test automation dashboard to validate every tap pattern after firmware or integration updates.
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 feature disabled in device config
- Wrong integration/driver selected
- Automations mapped to wrong event fields
- Hub does not expose multi-tap payload correctly
- Stale entity after re-inclusion
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.