Got myself an ES1. I plan on mounting it such that it activates an extended branch of overhead lights in an unfinished basement.
I did the initial device addition- Hubitat assigned the default driver. It did not have illuminance, which I planned to use to help prevent the lights going on if its already daytime/bright. If i dont mention it again, I pretty much spam some sequence like refresh/config/refresh/refresh/browser-reload/refresh after initializing a newly added device or after switching device driver.
Wanting a LUX Reading, I installed the community driver specific to the ES1. Also my first try at HPM. No offense to contributors, but Im not a fan as it didnt work and I gave up. Importing drivers from a git url is fine by me. The device shows LUX now, but motion active and motion inactive for X seconds didnt work as trigger in Basic Rule to turn a test device on and then off. Distance from hub is not a thing.
Then I tried the more general driver for Tuya mmWave presence sensors. Parameter, and even sub-parameter (design-wise I was impressed as Ive never seen this before; love the extended help toggling too) overload 
. Plus it sort of nagged at me that the option to specify a device proto didnt have the ES1. Still the "motion inactive for X seconds" didnt function as a trigger in a Basic Rule to turn off a test device.
Further, when looking up to select this driver I realized Hubitat has a terminology (ontological?) issue:
Only user devices appear as "presence device"- phone or tablet types. Motion sensors, and the whole notion of "motion" seems like a mis-match to what these devices are supposed to do. They sense physical motion, which is what PIRs do, but they are also intended to detect sustained human presence and then that presence becoming absent...
Which driver will allow:
- illuminance reading
- motion trigger
- motion/presence has stop for X amt of time
I was hoping I can avoid inferring non-presence by setting a rule-based trigger with a wait standoff from the last motion, like I'd put up with in use with PIRs.
My end goal is to use this sensor to trigger an outlet to turn on when someone passes into a portion of my basement (utilities + storage). Restricted by LUX, so my overhead lights dont turn on unnecessarily. Then, the sensor reporting no static presence and no active motion for some time will trigger the same outlet to turn off (the overhead lighting).
I read a lot of the three or so related threads about these 25ghz mmWave Tuya Devices, which is how I found out about the two community drivers. However, those threads are long and many other threads link-to them and it was not very clear what the current best practice is and state of whats-what with the development status of these drivers and devices.
I've high hopes for this kind of device, and their ability to accurately gauge how long it's been since a person was in-frame of the watched area. I've got another, an oval-shaped Haozee presence sensor, to support another segment of overhead basement lighting. So, Im hopeful to ace this first-go with the Linptech and then go forth. Id like to replace a PIR, looking at a stairwell to add lighting, with one of these mmWave Sensors. More epic meh than acing so far though- please help 
