I have tested this with a bound group and the load (just a quick test) and initial results are that it is working for me. I set “binding off to on sync level” to enable and then set “local default level” to 50. When I am detected by presence or if I turn the switch off and back on physically (as a test) it turns to that level. If you are still having problems I can run through and try all of your steps to see if that triggers an issue for me.
Although I wasn’t using it for my tests I posted about earlier, my goal is to let Adaptive Lighting determine the brightness level and not have it hard-coded into the switch via the default level settings. Changing the default brightness parameters to something like 50 does work as expected, but I thought setting them to 255 would return the the lights to their previous level when turned back on.
The only way that seems to work is if I turn the switch on from within HA. Hitting the paddle to turn the lights on doesn’t seem to respect the 255 value in parameter 13 like I was expecting.
I imagine this won’t be relevant in even just a few days, since it seems like the zigpy PR is moving along, but might I recommend a slight modification to the instructions.
As it stands right now, the instructions involve downloading an Inovelli-specific __init__.pyfile into the root of a user’s custom ZHA quirk directory, potentially interfering with and/or overriding an existing __init__.py or imports used by other non-Inovelli-related quirks.
Personally, I created an inovelli subdirectory in my custom quirks directory and moved the __init__.py file there (/config/custom_zha_quirks/inovelli/__init__.py). The VZM file I still placed at the root of the quirks directory (/config/custom_zha_quirks/VZM32SN.py). The import inside the VZM file was then edited as such:
from custom_zha_quirks.inovelli import (
INOVELLI_AUTOMATION_TRIGGERS,
InovelliVZM32SNCluster,
InovelliVZM32SNMMWaveCluster,
)
This will allow for future base classes and Inovelli-related imports to be appended to the Inovelli module via theinovelli/__init__.py file, without interfering with other modules.
Thanks for pointing that manual page out.. I never bothered to open my manual when installing this thing.. LOL
I did pop it open and looked on page 32 and saw a QR code and URL to go over the 15 different mmWave related parameters. I ran over to my laptop and manually typed in the URL from the manual which was https://inov.li/vzw32snMC
To my surprise, it just showed an error: Short code does not appear to exist.
So, I scanned the QR code on my phone instead and saw that the REAL URL is https://inov.li/vzm32snMC
So, slight printed manual error, there.. Now to go try to make sense of the parameters!
Hi, I have an idea for an enhancement that I hope folks will like. for parameters 13, 14, 15, the default dim level for local, remote, and when power is restored, value 255 is associated with the previous dimmed value.
Right now, I’d like to set automation so that at night based on some trigger it sets all the lights to minimum brightness on the next time a light is turned on. Then, in the morning, I’d like to set it back to reasonable values. The problem is, right now, if I set the value to 255, the first turn on of every switch in my house will be at 1% until the brightness is turned back up. I’d like there to be a parameter I could set that actually controls the “previous” or “next" dim level so that I can have automation preemptively set the value based on automation. I think this is likely to be useful for other automations as well.
Hello, recently installed the blue series mmWave. Was disappointed to find it operates differently from the 2 in 1 platform in multi-way configurations. A) Will toggle support in non-dimming mode and neutral wire present be a future capability or B) will aux switches be required?
If B is answer, when will aux switches (4 way configuration are a pain) potentially be in stock again or do other third party aux switches an option.
This is my first innovelli purchase and otherwise very impressed with performance and customization options of switch!!
I received my switches and the first one installed just fine. The second one will join zigbee2mqtt just fine as well, but then it immediately leaves the network. It continues to work locally, but it briefly appears then disappears a few times from the z2m dashboard. It has a neutral and replaced an inovelli red dimmer that didn’t have any problems. I tried factory resetting (holding config and up for 20 seconds), but it goes through the same sequence of connecting then disconnecting. I also tried forcing it to pair directly to the coordinator (a home assistant zbt-2). What can I try next? I have three more to install but want to get this sorted out first. After pairing the z2m log just says: [1/8/2026, 7:24:30 PM] z2m: Device ‘0x0c2a6ffffef19ff4’ left the network
Completely understand but wanted to confirm. Thank you for the tip on compatibility with aux switches. A pox on the contractor for putting 4 ways switches throughout my home!
Are you using it in a three-way / four way circuit. If so, the design was changed from the original plan to work with dumb switches. It now requires AUX switches if used in a multiway configuration. I received AUX switches fairly quickly when I ordered them from Inovelli.
to follow up on this, even in on/off mode it still shows the level for about 1 second (with Parameter 17 set to “Do not display load level”) when turned on, not sure if this is a bug or not.
I’m trying to understand what this “stay life” does. The default is 300. Is that seconds?
Just playing with it since yesterday - works great out of the box except for when i’m watching TV under a blanket. So, sounds like this is the param to tweak but i’m confused by the recommendations.
Thank you and appreciate the support from the community. They are those pesky 4 way switches and have ordered some 3rd party AUX switches as when I checked the innovelli type were currently on back order!
I shared a bit about this above, but essentially stay life determines how long to wait before setting occupancy to empty if the sensor loses you but you didn’t walk out of the room. So it should help address your issue when you’re watching TV under a blanket.
The units are in “50ms increments.” Admittedly this is a bit confusing, but what it essentially means is that 1=50ms, 2=100ms, 10=500ms, etc. So the default of 300 = 15,000ms or 15 seconds. I have it set to a really high value in bedrooms (7200000 aka two hours) or rooms where I might be sitting very still for extended periods.
Yes, hold time only impacts how long it takes to clear when it detects you moving out of the room. I never want it to lose me when I’m remaining in the room, so I have stay life set to a much higher value than hold time.
