[RELEASE] Linptech/Moes 24Ghz Presence Sensor ES1 ( TS0225 _TZ3218_awarhusb ) drivers

With respect to all of these various mmW sensors, motion is still the attribute (just like PIR sensors)... The attribute of "presence" is still exclusively used for Home-vs-Away geofencing-sorta stuff.

Maybe that all will change someday on the future as mmW sensors gain in popularity, but it would be a pretty big seismic change to introduce some kind of third attribute that's related to mmW-presence versus geofence-pressence.

3 Likes

It's going to be much more than just a third attribute. We'll need support for direction, motion/static detection, distance, etc., and all that for multiple targets. It's a hell of a UX challenge, especially considering the current Hubitat UI approach.

1 Like

Tks guys. Btw, does it also means that today there is no presence device that hubitat is compatible enough to inform, e.g., the zone in the room that got presence?

You can do it manually with the sensitivity and range settings (i.e., setting up the sensor to report "active" only when presence is detected in a part of your room), but obviously, it won't report then other parts of the room, etc.

Hello all,

I feel like this is such a noob question but I can't figure it out.

I got a Linptech 24Ghz Presence Sensor ES1 to turn on the laundry room light if someone is there. I installed @gassgs's driver to Hubitat.

But how do I add the sensor itself to Hubitat as a Device? It's WiFi, so I can't use Zigbee or Zwave. I don't have a Tuya hub or something to connect my Hubitat to. Can you please guide me in the right direction?

I tried adding it as a "Virtual Device" but all I'm seeing is this:

Thanks a lot!

All the discussions here are based on the Zigbee model, not the Wi-Fi version.

There's no way to connect the Wi-Fi version directly to the Hubitat hub. There may be a cloud connection option but I'm not aware of it. @kkossev?

My general recommendation would be to return it and purchase the Zigbee version if you still can.

2 Likes

Ah, that is exactly what I was worried about, thank you so much! I think I'll do that, because I tried the Tuya/Smart Life driver too but even with that this sensor did not work. I think I won't mess with it anymore. But thank you so much!

Linptech Zigbee version is very stable and works flawlessly.

2 Likes

Okay, I got the Zigbee version. But Add Device -> Zigbee did not work. I added it as Virtual Device, but it doesn't seem to be working. How should I add the device?

Thank you!

See the "How to Add a Zigbee Device" section in the Documentation here:

If you have this community driver already loaded, it will hopefully be added using that driver.

Otherwise, it should add using the native (built-in) Linptech driver.

1 Like

@cagrimertbakirci - what he (@hydro311) said. :slight_smile:

Well, I know that method. That's what I meant: Add Device -> Zigbee pairing did not work for some reason. The driver is installed and the sensor is blinking blue right out of the package, but HE does not discover it after 90 seconds. That's how you add it, right?

Sometimes you may need to do a reset of the device to get it to pair.

I haven't done it in a while but I think it's something like holding the button on the front of the sensor for a period of time. There should be something in the instructions you received with the device to tell you how to reset it and or just put it into pairing mode, try that.

If you have the WiFi model, it is better to return it if you can.

Make sure you have the Zigbee version.

1 Like

Yes, he just did that, and just received the Zigbee version. :slightly_smiling_face:

2 Likes

Yep, I just got the Zigbee version (returned the Wi-Fi one). I re-installed the driver too. But when I click on Add Device -> Zigbee, it runs for 90 seconds but cannot find it. I tried pressing on reset button for 5 seconds, it blinks, but nothing happens. :confused:

What is your HE hub model?

It's the Hubitat C8 Pro.

Try this Double luck vodoo.

C-8 Zigbee device pairing is improved in the latest beta platform versions. Until it is publically released you can try this workaround.

1 Like

Oh wow, just the first step solved it! It was only 2-3 ft away from the hub, I brought it to 1-2 inches and retried and it found it immediately. Is this a known issue? I've never had it before, but then again, maybe I was doing it closer before, I'm not sure.

1 Like