How to Fix Inovelli Dimmer Not Reaching Full Brightness
- Maximum level parameter reduced
- load calibration drift
- automation cap override
Problem Description
When your Inovelli Inovelli Max Brightness Limit 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.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. Dimmer tops out below expected maximum output. The pattern people actually report is Ceiling below 100%, brightness cap after firmware update, and different max local vs remote
The most common real-world triggers are Maximum level parameter reduced, load calibration drift, and automation cap override. The fix is most reliable when the sequence is followed exactly: Inspect max-level parameters, then Run calibration routine, then Validate with live tests. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Ceiling below 100%
- brightness cap after firmware update
- different max local vs remote
Recognize these? Here's what usually causes it.
Common Causes
- Maximum level parameter reduced
- load calibration drift
- automation cap override
Most fixes happen in the first 3 steps.
Do not assume app slider at 100% equals true output if caps are active.
Tools & Requirements
Step-by-Step Solution
Inspect max-level parameters
Confirm brightness ceiling values for local and remote contexts.
Run calibration routine
Recalibrate dimming curve where platform/device supports it.
Validate with live tests
Test manual and automation commands at full output.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If flickering only happens on dimming, the issue is almost always the dimmer's minimum-load setting, not the bulb — it's drawing less current than the dimmer expects.
Maximum-level settings should be validated after every firmware rollout.
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.
- Maximum level parameter reduced
- load calibration drift
- automation cap override
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.