Back to Inovelli Guides
Inovelli

How to Fix Inovelli Scene Control Not Working

Inovelli GuideSmart Switches
medium difficulty 15-25 minutes 93 views 0 found helpful Where this fix applies: North America, Selected international markets Updated
This guide applies to: Inovelli Inovelli Scene Controls (Blue Series 2-1, Red Series 2-1, White Series Dimmer)
At a glance — most common causes
  • Scene control not enabled (parameter)
  • Hub not decoding scene events (Z2M/ZWave JS)
  • Firmware outdated
15-25 minutes13 solutions coveredmedium level

Expert Review & Technical Scope

DeviceInovelli Inovelli Scene Controls
Model CoverageBlue Series 2-1, Red Series 2-1, White Series Dimmer
Fix Time15-25 minutes
DifficultyMedium
Required Toolshub logs, inovelli switch, automation editor
Network / ProtocolWi-Fi / app-based troubleshooting context

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.

Why This Happens in Real Homes

Inovelli scene control lets the paddle do more than switch the load — multi-taps and holds fire scene events your hub turns into automations. So when the load works but scenes don't, the scene events either aren't being generated (scene control not enabled, or firmware) or aren't being decoded by the hub (Zigbee2MQTT/Z-Wave JS not surfacing the button events).

Confirm scene control is enabled in the switch's parameters, and that your hub is set up to decode the scene/button events — in Zigbee2MQTT that's the action events, on Z-Wave the Central Scene notifications. Update the switch firmware, re-interview or re-pair the device so the hub knows its capabilities, and make sure your automation is listening for the exact event payload the switch sends. With scene control on and the hub decoding events, taps and holds trigger automations.

Symptoms

  • Scene control not working
  • Multi-tap does nothing
  • Paddle load works, scenes don't
  • No scene events
  • Taps not registering as scenes
  • Scene commands not sent
  • Automations not triggered by taps
  • Scene control dead

Recognize these? Here's what usually causes it.

Common Causes

  • Scene control not enabled (parameter)
  • Hub not decoding scene events (Z2M/ZWave JS)
  • Firmware outdated
  • Device not reporting scenes
  • Binding/routing issue
  • Automation listening to the wrong event
  • Config not applied
  • Central Scene not configured (Z-Wave)

Most fixes happen in the first 3 steps.

Warning

Do not assume one working tap means all scene events are healthy. Validate every multi-tap action separately.

Tools & Requirements

hub logsinovelli switchautomation editor

Step-by-Step Solution

1

Confirm model and integration path

Identify exact Inovelli series and make sure 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.

2

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.

3

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.

4

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.

5

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

Enable scene control in the switch parameters
Ensure the hub decodes the scene/button events
Update the switch firmware
Confirm the device reports scene events
Re-interview/re-pair the device
Match the automation to the actual event payload
Apply the config parameter properly
Verify Central Scene support on Z-Wave

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.

Pro Tip

Create a small scene-test automation dashboard to validate every tap pattern after firmware or integration updates.

Real-World Insight

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.

What Usually Goes Wrong
  • Scene control not enabled (parameter)
  • Hub not decoding scene events (Z2M/ZWave JS)
  • Firmware outdated
  • Device not reporting scenes
  • Binding/routing issue

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 Scene Controls.

View Inovelli Scene Controls Online Manual

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.