Why Is Inovelli Fan-Light Combo Scene Not Syncing
- Endpoint mapping mismatch
- scene payload missing one channel
- integration driver endpoint bug
Problem Description
Your Inovelli fan/light combo switch (LZW36 or VZM35-SN) does not trigger scene events correctly — double-tapping the light paddle fires the wrong automation, or fan scene events are missing entirely. The fan and light endpoints send separate scene events, and automations must target the correct endpoint to respond to the right paddle.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. Fan and light scene actions execute inconsistently on combo setup. The pattern people actually report is Fan changes but light does not, scene partially applies, and state drift after repeated scenes
The most common real-world triggers are Endpoint mapping mismatch, scene payload missing one channel, and integration driver endpoint bug. The fix is most reliable when the sequence is followed exactly: Audit endpoint mappings, then Rebuild scene payload, then Retest repeatability. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Fan changes but light does not
- scene partially applies
- state drift after repeated scenes
Recognize these? Here's what usually causes it.
Common Causes
- Endpoint mapping mismatch
- scene payload missing one channel
- integration driver endpoint bug
Most fixes happen in the first 3 steps.
Do not rely on single generic command for multi-endpoint devices.
Tools & Requirements
Step-by-Step Solution
Understand the dual-endpoint design
The Inovelli fan/light combo switches (Red Series LZW36, Blue Series VZM35-SN) have two separate control endpoints — one for the fan motor and one for the light. Each endpoint sends its own scene events independently. In Home Assistant, these appear as two separate entities: a light entity and a fan entity. Scene events from the fan paddle and the light paddle are different events with different property keys. Make sure your automation is listening to the correct endpoint's scene events.
Map scene events to the correct paddle
On the LZW36 (Red Series fan/light): the top rocker controls the light, the bottom rocker controls the fan. Scene events from the light use property_key '001' (up) and '002' (down). Scene events from the fan use different property_key values. On the VZM35-SN (Blue Series fan switch): the paddle controls the fan only — light control is through bindings or automations. Check the exact event payloads using Developer Tools > Events > Listen to Events > 'zwave_js_value_notification' or 'zha_event.'
Create separate automations for fan and light scenes
If you want a double-tap on the light paddle to activate a specific scene (e.g., movie mode): create an automation that triggers on the light endpoint's double-tap event only. Similarly, if a double-tap on the fan paddle should change fan speed: use the fan endpoint's event. Do not combine both endpoints into one automation trigger — they fire independently and your automation needs to know which paddle was pressed.
Check for entity conflicts after re-pairing
If you removed and re-paired the fan/light switch: the old entities may conflict with the new ones. Home Assistant sometimes creates duplicate entities (e.g., light.inovelli_fan_light and light.inovelli_fan_light_2). Go to Settings > Devices > find the switch. Delete any old/duplicate entities. Check your automations — they may still reference the old entity IDs. Update automation triggers and actions to use the current entity IDs.
Adjust the fan canopy module if using the LZW36
The Red Series LZW36 has a canopy module that installs inside the fan canopy (at the ceiling). The canopy module communicates wirelessly with the wall switch. If the fan and light scene events are inconsistent or missing: the canopy module may have a weak wireless connection to the wall switch. Check the distance and any obstructions between the wall switch and the ceiling fan. The RF link between the two has limited range (about 6 meters). If the fan is far from the switch: consider the Blue Series VZM35-SN which uses Zigbee (better range through the hub mesh) instead of a proprietary RF link.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If pairing fails after multiple attempts, the device may still be registered to a previous account — factory-reset it before trying to add it to a new one.
Combo devices require endpoint-aware scene design.
Pairing failures almost always come down to distance during the initial handshake — manufacturers seriously understate how close you actually need to be.
- Endpoint mapping mismatch
- scene payload missing one channel
- integration driver endpoint bug
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 Fan-Light Scene Sync.
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.