Hi Lance
I’m not trying to use the motion sensor to trigger the load. On this switch, I need to be able to disable local control, as I plan to tie that switch paddle to a different switch with Z wave association.
Motion sensor is not being used to trigger the load.
Does not work there, tried many times with multiple switches.
We just updated the driver try doing an import of the VZW32-SN driver from the Gihub
Thanks Lance - the Local Control setting now shows on the preference page in Hubitat, and shows that Local Control is disabled - but has no effect, the switch still has local control.
Looking on Z Wave JS, there is no setting for local control at all, so I assume this is a firmware issue?
Thanks for your help
After you updated did you hit configure and initialize? You may want to also reboot the switch. Once I updated the driver I was able to control local protection. Try the couple things and let me know how it goes.
I always forget to do the configure and initialize thing. I did that plus power off, and still does not work. I’m on firware 2.01, so I tried rolling back to 2.00 and still does not work.
A snippet of the log:
dev:1582026-05-03 09:09:42.867infoBottom Deck Light Protection Report: Local protection is off & Remote protection is off
dev:1582026-05-03 09:09:42.860debugParsed {"cc":117,"cmd":3,"ep":0,"values":[{"ccVersion":2,"newValue":0,"endpoint":0,"metadata":{"readable":true,"label":"Local protection state","secret":false,"writeable":true,"type":"number","stateful":true,"states":{"0":"Unprotected","1":"ProtectedBySequence","2":"NoOperationPossible"}},"propertyName":"local","commandClass":117,"property":"local","commandClassName":"Protection","value":0,"prevValue":0,"ts":1777820982840},{"ccVersion":2,"newValue":0,"endpoint":0,"metadata":{"readable":true,"label":"RF protection state","secret":false,"writeable":true,"type":"number","stateful":true,"states":{"0":"Unprotected","1":"NoControl","2":"NoResponse"}},"propertyName":"rf","commandClass":117,"property":"rf","commandClassName":"Protection","value":0,"prevValue":0,"ts":1777820982840}]} to ProtectionReport(localProtectionState:0, rfProtectionState:0)
dev:1582026-05-03 09:09:42.297debugBottom Deck Light setParameter [ProtectionSet(localProtectionState:1, rfProtectionState:0), ProtectionGet()]
Looks like the command is sending, but is not taking.
So I updated the firmware to 2.02, but the issue persists. I cannot disable local control.
I’ve been using the VZW32-SN and the VZW30-SN for a couple of weeks, in different configurations, from single pole to two VZW32-SNs in 3-way stair configs. Mostly I’ve been really happy. My VZW32-SN were shipped with firmware 2.0.0, which worked for some simple scenarios. I recently updated to v2.2.0 (also known as v2.0.2), and finally have accurate fine grained control of the radar. Very excited to see how it works. I’ve set P114 to 30s, to hopefully avoid any lockout issues, but will update here if they occur. I love these switches, and wanted to encourage the team to keep going. My gf was skeptical at first, but is in love with inovelli, and refuses to let me even try Lutron. You’re almost there in terms of rock solid performance, so, in case you needed some encouragement, here it is. I noticed there is no review option available on your main page (where I purchased from), so I’m assuming you received some negative reviews. We love what you are doing, so please, keep chipping away, and these switches will definitely become ridiculously rock solid some day soon, we LOVE the fine grained control of the mmWave sensor, it is GAME CHANGING!!! KEEP GOING!!!
Hey all,
I installed three VZW32-SNs about a week ago and flashed 2.02 at install. Yesterday all three had Z-Wave connectivity problems on the same day, while my VZW31 (no mmWave) and the other ~25 nodes on the network were totally fine. Setup is Home Assistant + Z-Wave JS UI with the Nabu Casa ZWA-2 (800 series) controller.
What I saw:
Things I ruled out:
One data point that stands out: commandsDroppedRX in Z-Wave JS is 247, 228, and 31 on the three VZW32s vs. 2-3 on my healthy nodes.
So the pattern is: only the mmWave switches, all on 2.02, all within a week of install, with what looks like the switch radio briefly dropping its connection to the controller and then getting stranded on a bad route.
I see the 2.03 beta’s changelog includes “Optimized the network re-connection logic” and “Further optimized the interaction logic between the mmWave module and the Z-Wave chip” — is what I’m describing the issue those fixes target?
Happy to beta test on one of my switches.
Thanks!
@smarthomer I just pushed 2.03 to our git you can find it here Firmware/Red-Series/Z-Wave/VZW32-SN-MMWave-Switch/Beta/2.03 at main · InovelliUSA/Firmware · GitHub
I would also try removing the switch from the mesh and doing a factory reset the re-include. Also Important Step After Flashing 2.03+ When you update the switches, physically pull the air-gap tab on the switch for at least 10 seconds after the flash completes
Just wondering if you guys plan on implementing anything that will check the lux threshold before turning on the light due to movement. It seems like you could use Config 118 and just add another Config to turn on/off the option to turn on/off the light when the threshold is met and movement is detected.
@EricM_Inovelli any progress with adding mmWave features to the z-wave motion switch? I have five of the RED motion switches, and I would very much like to use multiple detection zones for automations. Is there any near-term expectations that might be possible, or should i just buy a BLUE motion switch instead?
We do have a beta fw for the VZW32 coming up, but it will mostly be bug fixes. The main “feature” I would say is improvement of how Quick Start processes with various ramp rates. Multiple zones is still planned for the VZW32, but it is not currently being worked on.