You can check this post : 23 years in the making. Finally--reliable room level presence thanks to mmWave
The OP is running 15 of the "spammy" WZ-M100 mmWave sensors without noticeable issues.
Just to be on the safe side, I would recommend running so many radars on a second hub.
In terms of having the lights go out while I'm sitting still I'm not see any improvement over my Aqara FP1. Retriggering the lights back on after the lights go out is better with this device. The field of view seems wider, the lights come on sooner when I enter the room.
I'm going to play around with the settings to see if I can get the small movement detection better. So far I haven't been able to make any improvements.
I've been very pleased with the so called "spammy" 24GHz wall sensor in our tenant space. Working exactly as needed. Running it on HA with no noticeable disruption, so I've decided to buy two more from the same seller. They say they've got both 24 and 5 GHz versions, so I specifically ordered the 24GHz versions and hopefully they deliver that.
I've really changed my mindset about mmW, and it's place in my home. These are going to save me a ton by lowering the heat setting in unoccupied spaces. For this minor investment of $24 US a piece, I'll save hunderds of dollars this Winter.
Going down the track of mounting a ceiling mmWave sensor above the bed to detect if someone is there (but otherwise too still for normal motion sensors to pick up).
Looking at the list at the top of the thread I found this (https://www.aliexpress.com/item/1005004147995775.html). Thinking of going with the Moes version as it has a cleaner look with a blank face.
Has anyone got this sensor and found any issues with it (e.g. too chatty etc.).
Thanks in advance.
Another option is below the bed pointed up or at the foot corner angled toward the head to cover as much top of bed as possible with the cone.
As long as it will transmit through a cat's body, remembering my cat's behavior. Place anything on the ground and he would assume I had put it there for him to lie down on. 
Have we identified a 24GHz ceiling mount that combines the key attributes below?
Has a favorite emerged?
Put it in a box.
Clearly you've never owned a cat...a box is just a puzzle waiting to be solved.
I'm actually going to try mounting one to the bottom of our bed, that way I can run the cord along the bedframe so it won't be run over by the primary bedroom robovac. Biggest issue will be reaching the spot where I want it w/out taking the mattress and box spring off the bed. If I can't reach then I'm try at the foot of the bed pointed towards the headboard.
Great idea, thanks.
Didn’t even think of that possibility. Might try that with a spare Aqara FP1 I have lying around.
Keen to see what favourite emerges for a ceiling mount in due course.
Ironically, his name is Schrodinger.
LOLs... I guess that means whenever he climbs into a box you just step away. 
Does this model support MMwave?
The device works fine when I use it just for motion under YXZBRB58_RADAR Profile.
The device becomes non responsive when I change the profile to Human Presence MMwave Radar profile.
Particulars below:
It looks like one of the 5.8GHz radars. Not technically millimeter wave, but much more sensitive than PIR. I would suggest using the profile that works. This driver covers quite a few different sensors. They are all radar, some 24GHz, but most are 5.8.
@jiggy_nubn Which may also mean that it will "see ghosts" through walls, e.g., sensor sees motion in another room through a wall (if I remember some posts here) so you may have play w/placement and any available sensitivity settings you have access to, to deal w/that.
The distance setting is off by default. Turn that on and walk around the room. If you are not being picked up, raise the sensitivity. Check your minimum and maximum distances.
Don't forget to turn off the distance reports when you are done.
One more tip: set the illumination setting to 20, 30 or even higher. No one needs that much differentiation. This was one of the things jamming up my hubitat.
It apparently sends the lux no matter what you set it to, unless you tape it over. That made a huge difference in the number of events mine was sending.
Yes, taping it over is the better approach. Most of the Tuya devices reporting periods and thresholds are not configurable, the driver just hides the reports.
Thanks for clarifying. I know that the number of events per hour for mine went from almost 800 to around 350 after taping over the lux sensor. Not a small difference!
Thanks for the tips. Trying them now.
I know that it hides it. I'm a die-hard webcore user and by setting threshold for change up higher, webcore doesn't trigger a piston each every time that the lumens go up or down 1.
Download the Hubitat app
