It would be awesome to one day see an “installation angle” parameter.
The idea is that it allows the rotation of the zones relative to the sensor according to that angle.
I have a bathroom where the light switch is on a short wall that’s at a 45° angle to the room. This kind of configuration is available in another brand of presence sensor I use and it’s very useful.
Thank you! This is VERY helpful. I did not even think about the fact that this thing has 360 degree sensing… So for a switch that is at the base of a stair - ie about 40" above the first step, on the wall parallel with the stair run, if I set the width min at 1’ (to the right facing out from the switch), and the width max at -12’ (to the left facing out from the switch) does it mean it would limit the detection area to the right to 1’ and to the left to 12’, or do the min and max mean something else?
I only want it to sense (from the position of standing at the all facing out from the switch) about 1’ to the right of the switch as any further right is in the hall where people pass all the time but don’t necessarily go up and down the stair.
Also, since there are three switches in my setup that control the stair lights, and the base of the stair is not the master switch powered from the panel, will I be able to use it, or will I need two. Alternatively does the motion sensing work separate from the switch, where I could just use the Inovelli as any switch in the 4 way setup and have the senor control a different z wave light?
Well it doesn’t have 360 degree sensing as far as I know. It can’t see behind itself for one thing and there is a limited range on the x/y axes as well. I don’t have the exact numbers off hand, but I think it was posted somewhere in this very long thread 
!
Let me give a more generic example. All of the measurements are from the position of the switch itself. So if you were the switch facing away from the wall and you wanted it to cover an area 1’ to the right and 12’ to the left, you would set the width min to -12’ and width max to 1’. Of course, convert all numbers to centimeters because that’s how the switch expects them.
You should be able to use Z-Wave associations or Zigbee binding to have the switch with the sensor control the master switch. Alternatively an automation on your hub could do it as well.
Yes. By default, the switch is controlled by it’s own presence sensor but that can also be turned off. There’s a bunch of different modes it can be in (screenshot again from Zigbee2MQTT because that’s the switch I have:
Looks like the switch received zwave certification in the last few days. There is also an instruction manual!
https://products.z-wavealliance.org/products/5218?selectedFrequencyId=-1
Yes! I was saving the announcement haha. We’ve finished Z-Wave and are awaiting on FCC/IC (should be wrapping up next week) and ETL (late July). But one step closer!
Very exciting!
Can’t wait! Contributed Apr 2023 and have been checking in regularly. I’m amazed there hasn’t been a Z-Wave mmWave switch or even a stand alone sensor in this time! Probably a testament to how difficult this was to produce. Wish you the best of luck with the release. Have a feeling this will be extremely popular!
Thank you @EricM_Inovelli for the explanation of mmWave sensor configuration! Also helpful is the user manual attached to the Z-wave certification. However, I find the configuration parameters a little confusing: why are the parameters specified as distances (in cm?) in the X, Y, and Z axes instead of angles in the XZ and YZ planes and a radial detection range? As an RF device, I would expect the field-of-view to be expressed as a cone defined by the -3dB angles in the XZ and YZ planes, and previous posts about this switch follow this convention. This is confusing because the configuration parameters define a cubic volume, while the field-of-view is (ideally) a conic volume. In fact, the manufacturer datasheet does specify horizontal and vertical beam angles of -60 to 60 degrees (section 4.3). So in the context of a 120-degree conic field-of-view, what do the rectilinear configuration parameters mean?
After reviewing the sensor datasheet, it appears that the configuration parameters (X_min, X_max, Y_min, Y_max, Z_min, Z_max) are exposed directly from the sensor API. From the datasheet, it seems that while “side-mounting” is described (with a 6m range), the intended use of the sensor is top-mounted (ceiling) looking down, and the detection parameters are defined “with the point at which the module is vertically projected to the floor as the origin.” In this context, I think the X and Y distances are to be interpreted as dimensions on the floor. So what does that mean in the context of a side-mounted sensor? Dimensions within a circle in the XY plane defined at the limit of detection sensitivity? Closer to the switch (as Z approaches zero), the sensitivity would not equal the configured X and Y limits; I guess that is what is meant in the manual by “as you can see in the graph, the range decreases closer to the switch.”
What is the purpose of Z_min?
After reviewing the user manual, I think it would be helpful to include a graphic depicting the XYZ axes in relation to the switch. Something like this:
Thanks, I’m really excited to install these!
Administrator edit: Edited the drawing to properly reflect the axis labels.
Z-wave finished? Latest release dates? ETA to get the 5 I ordered in my hot little hands? Thanks.
P.S. Switch now added to Home Assistant, (" * Add Inovelli VZW32-SN mmWave Switch")
Hi there,
Our current ETA for the Red Series mmWave switch to be delivered to users is late August to early September.
Thank you!
Looks like the Z-Wave Alliance has the Certificate Posted with Manual…
https://products.z-wavealliance.org/products/5218?selectedFrequencyId=-1
None of the short links in the manual work for me… Guess we’ll just have to wait until release to get all the details.
Is there a technical reason why you wouldn’t want to install 3 of presence switches together in the same gang box (say for can lights, under cabinet and exhaust fan)? Would the radars interfere with each other? In this scenario would it be best to use only one Presence switch dimmer and two smart dimmers?
I can’t speak to the technical aspects of signal interference, but this dimmer isn’t rated for a fan load. So for an exhaust fan, I’d go with the on/off and then trigger it with automation.
Two motion sensors side by side, if they’re compatible, seems like overkill to me.
The website still says delivery in late August (though they don’t specify a year, maybe 2027?).
So the question raises a different question. I already know
What I mean is, what if I want one light to go on when there is motion only to the left of the sensor, and a different light to go on only when there is motion to the right of the sensor? Could I install one Project Linus Motion Switch and just set up the two lights to trigger on different parameters of the mm wave sensor?
Hey everyone!
Just wanted to provide a quick update on this project. This is from the most recent Project Status Email for August:
All certifications are completed and we are now scheduled for production.
There was a small modification that needed to be made for the FCC/IC certification where we needed to add a small plate on the back of the mmWave PCB and the mmWave manufacturer had to run some internal quality control tests with the new plate, but those have passed, so we are set for production.
Right now, production is scheduled for the first week in September.
Traditionally, we sea-freight these which takes about a month, but since everyone has been waiting forever for this, we will air-freight them.
Once production officially starts, I will send an email out to confirm shipping addresses and to those who emailed in wanting to switch their order from Zigbee to Z-Wave or vice versa.
Thank you all for sticking with us on this – we’re excited to wrap it up and get it to you!
Thanks Kaleb! I am so excite 
It’s the end of September and I haven’t seen any emails or activity around this. Can you please give an update @Kaleb_Inovelli ?
In the other motion switch thread, they mentioned production being delayed until at least the end of Sept. They did say that on Sept 28th, we would get an update one way or another (but I still wouldn’t hold my breath… 
)
