Low-latency presence sensor: mmWave + PIR using ESPHome

What? What way do PIR outperform mmWave? From what video? It makes zero sense.

Sorry to wake dormant thread. a POE dual presence sensor such as this is exactly what I need for my HA setup. I have POE boxes above every door way in my home (was originally for the defunct Hiome grid sensor). Can any lead a Noob to a schematic on how to build this? I have advanced soldering skills and a 3d printer.

Thanks!

@crlogic I am currently working on a similar project and am considering whether a PIR is needed in addition to an LD2410 mmWave sensor.

From your thread so far, I have gathered that solely relying on the mmWave sensor resulted in a small number of delayed actions.
Hence, the signal is combined by the PIR signaling “on” and the mmWave signaling “on”.

My use case also involves detecting still objects, such as people sitting on a sofa and not moving much while watching TV, meaning I’d need to rely on the mmWave sensor for still detection.

Now, I am less worried about a second or so delay in turning on the lights but more by false positives due to micro-vibrations happening in the proximity of the sensor, which is why I am considering some combination of a PIR and mmWave sensor. However, I haven’t figured out how to combine both in still-detection cases accurately.

Based on your experience, do you have some input?

For my use case, it was a half-bath and I found using only the mmWave resulted in wild misfires of the automation and the lights flapping on and off from cats to toilet paper waving from the heat vent to the blinds gently swaying lol. I combined a PIR into my sensor device and use only the PIR to trigger on, then only the combined on+on or off+off state to turn off the lights… with very little dwell time. I’ve found this eliminates virtually all cats/tp/blinds or other air convection issues that might trigger the lights. Oh, the main purpose/need for my test case which I consider a success, is that the light is also the vent, and I wish it to be on no matter what the… “user” of the half-bath might feel is needed :wink:

Thank you for your input! That makes a lot of sense and, actually, I haven‘t thought about implications of wind so far - especially in summer when the AC might create micro-movements. :slightly_smiling_face:

Looking at this aspect, it definitely makes sense to trigger when the PIR goes on - what I need to figure out though is how to do still detection and keep the lights on even after the PIR initially triggered presence in the area.

Sounds like you already have a sensor (MCU+PIR+mmWave) in mind or maybe working now. Using example code from many sources including here… you can easily use Automations or Node-RED flows to do this. I can show some examples but the trick is to ignore the combined presence status that you typically see in the YAML examples and instead be sure to use the two binary sensors separately, PIR to trigger on large movement and turn on the lights, then only turn off after some time of no PIR and also no mmWave and then back to waiting for that initial PIR trigger. This way when the mmWave “flaps” as it will on so subtle of a movement or even sometimes vibrations in the wall or something through a wall, window, door or ceiling… lol. Your solution won’t also flap the lights but instead wait for PIR to trigger which can’t “see” anything outside the room if angled correctly. Mine are built into wall plug nightlights and where my outlets happen to be, over the height of the bathroom vanity counter top, and angled into the room not toward the door, they work great and only catch large movement entering the room-turning on lights but then watching for real mmWave motionless presence so the lights stay on until all motion is done and no one is present.