I have 7 of these and have not had to pull the power on any in quite some time now to get them out of freezing up staying active. Usually you could count on it happening after hub reboots from updating. Nothing differant except 2 new ones I have added to a 2nd hub, 1 a month ago and the other 6 weeks ago???
I would say just tiptoe quietly around the house and don't do anything to bother them.
I have one and have the drivers via Packet Manager but it does not seem to be working as a presence sensor rather just a motion sensor the gap between "active" and "inactive" is usually less than a minute and in that time I was defiantly present, jus standing still 6 ft from the sensor any suggestions?
Hubitat has a different definition of presence so these will never show as presence sensors within Hubitat.
While they’re always “motion” sensors as far as hubitat’s concerned, it should be possible to tweak the settings based on your needs.
I have played with the variables but is is NOT behaving as a presence sensor - I can extend the release time for motion - but I can do tha with a motions sensor. I need a presence sensor not a motion sensor. What presence sensors does Hubitat treat as presence?
Like all PIR sensors, the attribute used by all mmW sensors is still "motion", since the attribute of "presence" is already in use to denote home-vs-away status.
I think we may be at cross purposes. ! can live with the sensor sending a signal when a person is present that is treated like motion by Hubitat. But that is not the behavior I see. It is simply behaving as a motion sensor It I walk towards it and sit down still, it quickly clears the "motion" report and us back to the null state - I am sat still 4ft in front of sensor. Use case I need to trigger an event when an elderly relative has sat in front of the tv and not moved for a couple hours during daylight to send me a text to check in on them thats why I need to know presence A PIR will cover the motion bit, but I need to eliminate the cause of no motion being no presence
Sounds like you need to play w/the preferences for the sensor...(Detection Distance, Fade Time, Motion and Static Sensitivity). Some combination of settings should work. I have one of these in my wife's office and it keeps her "present" even when she's sitting very still, solved my long-standing problems w/her "Sphinx-mode" resulting in non-mmWave motion sensor automations turning off lights when she was at her desk. That was not a popular event.
Post a screen-shot of your settings. And just to confirm, you are using the device-specific community Linptech driver (Linptech 24Ghz Presence Sensor ES1), not the HE built-in driver (which the device may have defaulted to when first installed), correct? This topic is about the community Linptech driver. Multiple factors are involved so it can take a little tweaking to get things working in your particular situation. Nothing's perfect, but most of us have had good success w/these sensors.
Maybe you need a pressure sensor on the chair instead?
You may want to re-read what I wrote above.
You will not find a “presence” sensor compatible with Hubitat for this need (i.e. detecting a person in a room who is standing/sitting/lying still).
I think we understand what you mean by “presence,” and many mmWave device manufacturers are using this term to describe their sensors these days.
But it’s crucial for you to recognize that “presence” means something else in the context of the Hubitat platform.
For example. My phone is considered a presence sensor by Hubitat. It will send “arrival” and “departed” events when I enter or leave a geofence around my home.
I also have a zigbee key fob that does essentially the same thing. It reports when I am home (i.e. the sensor can connect to the zigbee mesh), but that’s all. It doesn’t know which room of the house I’m in (or not in).
That’s how “presence” works in Hubitat land.
It never means, “is someone present in a room or an area of a room where a mmWave sensor is installed?”
I think that most platforms also treat presence like that but not 100% sure.
It's maybe time for Hubitat to add a new capability to the drivers, how about calling the new capability "Occupancy". Just created a request for a new capability...