How to Fix Inovelli Scene Button Hold Actions Not Triggering
- Hold action disabled
- Event mapping missing hold code
- Integration sends different hold payload
Problem Description
When your Inovelli Inovelli Hold Actions 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
- Hold not detected
- Tap works only
- Automation never fires on hold
Recognize these? Here's what usually causes it.
Common Causes
- Hold action disabled
- Event mapping missing hold code
- Integration sends different hold payload
Most fixes happen in the first 3 steps.
Do not assume old automation blueprints include current hold-event schema.
Tools & Requirements
Step-by-Step Solution
Verify hold event support
Confirm current integration exposes hold action events.
Capture raw hold payload
Use event monitor to identify exact hold event key/value.
Update automation trigger
Bind hold logic to observed payload and retest.
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.
Hold actions often use different payload keys than tap 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.
- Hold action disabled
- Event mapping missing hold code
- Integration sends different hold payload
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.