February 3, 2026 / v2.01
Beta Testing Available: https://files.inovelli.com/firmware/VZW32-SN/Beta/2.01/VZW32-SN_2.01.gbl
Changes:
Typo in version. Registers as 2.1.0, not 2.01
Will test if there is any stability improvements.
Previous issue: After some time my node gets delayed and any changes like led behavior can take a minute to apply. The other day it wouldn’t respond to physical or remote inputs at all. Pulling the tab and resetting resolves the issue. Hope this is resolved now.
Any indication when we can expect mmwave (multi) zone metrics? The z-wave model is pretty far behind the blue version.
Anyone else test this and experience any issues with this?
Can confirm the firmware shows as 2.1.0. I was not experiencing any issue with the switch prior only been installed one day and is not used often.
Yeah its working much better now as the room sizing is actually applied. It doesnt seem to detect me through my lcd screen 2 meters away, but thats probably the limitation of the mmWave itself
For me, all appearances are that this firmware update fixes P101 - P106. Changing those parameters is now resulting in expected behavior.
How can I upload this firmware via Hubitat? Not seeing the Firmware update button like other Inovelli devices.
You have to use the Hubitat firmware updated application. Red Series • Updating Your Firmware • Hubitat | Inovelli Help Center
Is there a way for SmartThings users to update our devices without needing to buy a separate ZWave dongle? I’m eager to try this firmware because right now the motion detection on my switch is really not useful since it sees way too far.
You’ll need another hub, but not necessarily a ZWave dongle. If you get a Hubitat, the Zwave support is built in.
@SReg I have been able to set the boundary parameters in the firmware version the switch shipped with. If you are struggling maybe try this help article:
Red Series mmWave Presence Dimmer Switch • Parameter Changes Not Saving | Inovelli Help Center
If it doesn’t work maybe there is something going on in your hub and we can troubleshoot it to see what is going on. The SmartThings CLI will let you view the driver logs while you change the settings.
Hi Eric,
Gave those steps a try. Still the same issue. I posted the CLI logs back here in this thread: Z-Wave Motion Switch • Project Linus • Bug & Enhancement Thread - #82 by SReg
Wanted to second that this firmware update fixed my issues with P101-106. Thanks!
I have two of these set up right now. Both updated with the 2.01 firmware one reports 1w of contentious consumption in off where the other does not. Happy to provide additional details if it helps narrow the issue down.
I have not tried a full reset yet, since the other switch immediately corrected the behaviour after the update.
Can confirm this corrected the issue for me. I have a few switches setup but haven’t tried changing the detection zone until now. The parameters were saving but didn’t seem to have any effect. I thought I was losing my mind until I saw this.
There may be a memory leak with this firmware. To test changing the led bar I set 114 to zero and forgot to change it back. Where the switch is it constantly turns on and off and after a few days it locked up not responding to paddle presses or anything. I had to air gap it to get it working again.
The switch is not currently controlling any loads so I’m not sure when it locked up. Could have taken a week and thousands of motion detection’s, so this may be hard to reproduce.
I have three installed currently to test and I had one lock up a while ago before the update. Last week I had another one lock up and needed to air gap as well to get it working again as it would not respond to anything.
After you pull the air gap and reboot the switch it returns to normal operation? There doesn’t seem to be anything that can trigger it it seems?
Installed this on both my units. It made the P101-106 paramaters work (yay).
However, I had one lock-up on me (no response to button pushes even) which required air-gapping to restore.
The other one the illuminance detector has been stuck at 301 lux for days now.
