I don't know if this belongs in devices or integrations, so I apologize.
I have a Tuya TS0225_LINPTECH 24Ghz Human Presence Detector that works very well in the bathroom at detecting presence. However, when the window is open and the blinds move just a tad bit, it has trouble clearing motion. I had an idea that would involve me adding a window sensor and using it, along with the existing door sensor, to basically turn off the lights after the door has been open for a period of time. This would work, but the trouble is that the motion sensor doesn't pick up anyone coming in because it's still set to "active".
In Home Assistant, there is an action called "Hubitat: send_command" with the description, "Send a command to a Hubitat device" and but I have no idea what a Hubitat command for this device would look like, or even if it's possible in Hubitat itself to tell that presence sensor to clear.
Is this possible? If so, how would I do it for this device?
What driver is that device using in Hubitat? Built-in or community? As far as I know, there are no built-in drivers for "real" devices (as opposed to virtual devices) that support such a command.
If it is a community driver, you can request the developer of that driver to consider adding such an option.
Yes, it's at least possible with @kkossev's commuity driver -- I have a rule that leverages that capability via a momentary virtual switch (screenshot below).
I don't know if it's possible with the native driver or the other available Linptech-specifc community driver -- I've just never tried with either.
These newer mmWave sensors open up some great possibilities for sensing room occupancy even when someone’s staying pretty still, an obvious problem for PIR “motion” sensors.
But tuning and tweaking them to avoid false positives can be pretty challenging (or maybe even impossible in practice).
As @hydro311 described, you could use @kkossev’s driver and rule machine to send “inactive” commands to your Linptech sensor. The existence of the command is really more for sensor testing purposes, and it’s probably why it’s not an option for built-in device drivers.
But it can presumably be used for that work around if needed.
@kkossev’s driver also allows for a fair amount of tweaking the device sensitivity, which can help a lot.
Right on... I have not had to leverage my kill switch in a while now (which is great) -- it's just a button I keep on one of my dashboards for easy access if needed.
I agree with you @marktheknife. I have a few different presence sensors and the one thing that's kind of a bummer is the motion detection distance goes from 1.50 meters to 2.25 meters. For this use case, it would be tremendous if I were able to specify a value in between.
