Why Is Inovelli LED Bar Effect Not Showing Notifications?
- Notification command malformed/wrong format
- Hub not sending the effect correctly
- Firmware not supporting the effect
Problem Description
You sent a notification command to the Inovelli LED bar but nothing appears — the bar stays at its default color or goes dark. LED notifications require a correctly formatted service call with specific color, brightness, effect, and duration values. A miscalculated parameter value, an overriding automation clearing the effect, or a too-low brightness setting can all prevent the notification from appearing.
Why This Happens in Real Homes
Inovelli LED bar notifications use a special command that encodes the color, effect (pulse, blink, chase), brightness level, and duration into a single value — so an effect not showing usually means that command is malformed, sent incorrectly by the hub, or immediately overridden. It's a formatting/delivery issue more than a hardware one.
Confirm your hub is sending the notification command in the correct format for the VZM31-SN (in Zigbee2MQTT there are specific parameters or a helper for the LED effect), with a valid color, effect, level, and duration. Make sure the LED brightness isn't set to zero and that a state change or another command isn't immediately clearing the effect. Update firmware for full effect support. A correctly-formatted notification command displays the effect as configured.
Symptoms
- Notification effect not showing
- LED notification doesn't display
- Sent a notification, LED unchanged
- Effect command ignored
- No pulse/blink/chase
- Notification not appearing
- LED bar not reacting to the command
- Effect fails to show
Recognize these? Here's what usually causes it.
Common Causes
- Notification command malformed/wrong format
- Hub not sending the effect correctly
- Firmware not supporting the effect
- Parameters for the notification wrong
- Command sent to the wrong cluster/endpoint
- LED bar brightness at zero
- Effect overridden immediately
- Config/integration issue
Most fixes happen in the first 3 steps.
Do not stack multiple long-duration effects without reset handling.
Tools & Requirements
Step-by-Step Solution
Send the notification using the correct service call
LED bar notifications on the VZM31-SN require a specific service call in Home Assistant. The inovelli_blueprints community integration provides a 'Set LED Effect' script/service. Without this integration, you send the notification via Z-Wave JS or Zigbee2MQTT parameter commands. For Z-Wave Red Series: set Parameter 16 with a calculated value encoding color (0-255), brightness (0-10), effect (0=off, 1=solid, 2=fast blink, 3=slow blink, 4=pulse), and duration. For Zigbee Blue Series in Z2M: use the 'led_effect' or 'individual_led_effect' exposed features on the device page.
Calculate the notification parameter value correctly
The Red Series LED notification parameter (Parameter 16) combines color, level, effect, and duration into a single 4-byte value. The formula: (color × 1) + (level × 256) + (effect × 65536) + (duration × 16777216). Example: red (0) at brightness 5 with slow blink (3) for 20 seconds = 0 + 1280 + 196608 + 335544320. Getting one number wrong produces no visible effect or the wrong effect. Use the Inovelli LED calculator on their website to generate the correct value. For the Blue Series in Z2M: the interface lets you set each component separately — no calculation needed.
Check that no other notification is overriding yours
Only one LED notification effect can be active at a time. If you send a new notification while an old one is still running: the new one replaces the old. If an automation sends a 'clear' notification immediately after your notification: the bar goes dark instantly. Check all automations that interact with the LED bar — search for 'inovelli' or 'led_effect' in your automations. A common mistake: an automation triggers on state change, sends a notification, but then the state change triggers a second automation that clears the notification.
Verify the effect is visible at the configured brightness
LED bar notification brightness ranges from 0 (off) to 10 (max). If the brightness is set to 1 or 2: the effect may be too dim to see in a bright room. Set the notification brightness to 8-10 for testing. Also check: the LED bar's base brightness parameters (97/98) do not affect notification brightness — notifications use their own brightness value from the notification command. But if the LED bar hardware is defective (some segments always dark): the notification will also show the defect.
Clear stuck notifications
If a notification was sent with an infinite duration and you cannot clear it: send a clear command. For Z-Wave Red Series: set Parameter 16 to 0. For Zigbee Blue Series in Z2M: set the 'led_effect' to 'off' or 'clear.' In Home Assistant with the Inovelli blueprint: call the 'Clear LED Effect' script. If the notification persists after a clear command: air-gap the switch (pull paddle out for 10 seconds, push back in). The power cycle clears all active LED effects.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Notification delays almost always return after a major iOS or Android update — background app refresh gets reset to restricted on every major OS version.
Notification logic should define explicit priority and clear behavior.
Notification delays over 2 minutes are almost never the device's fault — background app restrictions quietly re-enable themselves after every OS update.
- Notification command malformed/wrong format
- Hub not sending the effect correctly
- Firmware not supporting the effect
- Parameters for the notification wrong
- Command sent to the wrong cluster/endpoint
Before you go — try one of these (they fix most cases).
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 LED Notification Effects.
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.