- Binding not configured correctly in the hub
- Bulb doesn't support the binding cluster
- Devices not on the same Zigbee network
Problem Description
You set up a Zigbee direct binding between your Inovelli Blue Series switch (VZM31-SN) and a Zigbee bulb, but pressing the paddle does not control the bound bulb. Zigbee binding lets the switch control lights directly without the coordinator, but it requires matching clusters, correct bind configuration in ZHA or Zigbee2MQTT, Smart Bulb Mode enabled if the bulb is on the same circuit, and firmware v2.15+ for reliable binding persistence.
Why This Happens in Real Homes
Inovelli Blue Series Zigbee binding lets the switch control bulbs directly, device-to-device, without routing through the hub — so it's fast and works even if the hub is down. When it's not working, the binding is usually misconfigured, the target bulb doesn't support the required binding clusters, or the devices aren't communicating on the same Zigbee network.
In your hub (Zigbee2MQTT), configure the binding from the switch to the bulb or a group, binding the on/off and level control clusters, and confirm the bulb actually supports being bound (most Zigbee bulbs do). Ensure both devices are on the same Zigbee network with a solid mesh link, and re-create the binding if it was lost after a re-pair or firmware update. For several bulbs, bind to a Zigbee group. A correct binding to a compatible bulb gives direct, snappy control.
Symptoms
- Zigbee binding not working
- Binding doesn't control the bulb
- Bound bulb doesn't respond
- Binding setup failed
- Paddle binding no effect
- Direct control not working
- Binding unreliable
- Bulb not bound
Recognize these? Here's what usually causes it.
Common Causes
- Binding not configured correctly in the hub
- Bulb doesn't support the binding cluster
- Devices not on the same Zigbee network
- Binding target (group/device) wrong
- Binding lost after re-pair/update
- Weak Zigbee link between devices
- Firmware issue
- Group binding not set up
Most fixes happen in the first 3 steps.
Do not assume all devices expose compatible endpoints for direct binding.
Tools & Requirements
Step-by-Step Solution
Understand Zigbee binding on the Blue Series
The Inovelli Blue Series (VZM31-SN dimmer, VZM35-SN fan switch) supports Zigbee direct binding — the switch sends commands directly to a Zigbee bulb or group without routing through the coordinator. This makes the switch control the light even if Home Assistant is offline. Binding requires both devices to support the same Zigbee clusters (On/Off, Level Control). Not all Zigbee bulbs support binding — check the bulb's Zigbee cluster list in your coordinator (ZHA or Zigbee2MQTT).
Set up the bind in ZHA or Zigbee2MQTT
In ZHA: go to the Inovelli switch device page > Manage Zigbee Device > Bindings tab. Select the target device or group and bind the On/Off and Level Control clusters. In Zigbee2MQTT: go to the switch device page > Bind tab > select the target (device or group) > bind 'genOnOff' and 'genLevelCtrl' clusters. After binding, press the switch — the bound bulb should respond directly. If it does not respond within 1 second: the bind did not take (see next steps).
Use group binding instead of direct device binding
Direct binding (switch to single bulb) can be unreliable with some bulb firmware. Group binding is more reliable: create a Zigbee group containing the target bulb(s), then bind the switch to the group. In Zigbee2MQTT: create a group, add the bulb(s), then bind the switch's On/Off and Level Control clusters to the group. Group messages use Zigbee multicast, which most bulbs handle more reliably than direct unicast binds. The switch can be bound to multiple groups simultaneously.
Enable Smart Bulb Mode on the switch
If the Inovelli switch is physically wired to the same circuit as the Zigbee bulb: you must enable Smart Bulb Mode (Parameter 258 = 1) on the switch. This keeps the relay always on (so the bulb always has power) and converts the physical paddle into a scene/binding controller instead of a relay toggle. Without Smart Bulb Mode, pressing the paddle cuts power to the bulb and the binding command is meaningless because the bulb has no power to receive it.
Check firmware compatibility
Binding behavior improved significantly in Blue Series firmware 2.15+. Earlier firmware had bugs where binds would not survive a power cycle — the switch would forget the binding target after a power outage. Check your firmware version: in ZHA, it is on the device info page. In Zigbee2MQTT, it is on the About tab. Update firmware via OTA: in Zigbee2MQTT, go to the device OTA tab and check for updates. In ZHA, OTA updates appear automatically if available. After updating, re-create all bindings — firmware updates sometimes clear the binding table.
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.
Document working bind profiles for repeat deployments.
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.
- Binding not configured correctly in the hub
- Bulb doesn't support the binding cluster
- Devices not on the same Zigbee network
- Binding target (group/device) wrong
- Binding lost after re-pair/update
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 Zigbee Binding.
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.

