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

Hi David,

This Linptech ES1 Zigbee device seems to be the same as the one that is already supported natively in Hubitat and supported by the two custom drivers available in HPM.

As we know, one and the same device can be sold by many different sellers on different platforms. Different sellers appear and disappear on the selling platforms (Amazon, Alixpress, etc..) Sometimes, the Zigbee identifier will be the same; sometimes, it may have a different 'manufacturer' ID. So, there is never a 100% guarantee of what you will receive, even when the device looks the same. There is no guarantee that the same seller will send you the same device, even in one purchase order - sellers' suppliers may have sourced the items from different manufacturers.

It doesn't make any difference whether you purchase such devices from AliExpress, eBay or the US Amazon (except the Amazon exceptional return policy, of course...). The sellers can not distinguish between the different versions because these Tuya devices are designed and they are always working with the Tuya hubs; any usage outside of the Tuya ecosystem is not guaranteed.

3 Likes

Good morning -

All the stuff quoted below is unnecessary and unwarranted. @kkossev or any other developer can speak for themselves; they've given no indication of needing an arbiter to deflect questions from community members.

If you dislike questions posed by a community member to a developer, you have the choice of ignoring that thread. There is no need for you to respond on the part of the developer.

@DGBQ was civil in his questions. If you dislike such questions, feel free to ignore them.

Continuing the discussion from [RELEASE] Linptech/Moes 24Ghz Presence Sensor ES1 ( TS0225 _TZ3218_awarhusb ) drivers:

5 Likes

Thank you for stepping in!

4 Likes

Hey @kkossev

Thanks for the insight. It sounds like the Linptech ES1 is already well-supported in Hubitat, which is good to know. The variability in Zigbee identifiers and manufacturers definitely makes purchasing Tuya-based devices a bit of a gamble, but it’s helpful that there are options like custom drivers to improve compatibility. I appreciate you taking the time to review the device and provide such a detailed explanation. Thanks again for sharing your knowledge!

2 Likes

I have 7 Linptech ES1's that are working perfectly, however there is 1 that refuses to report Illuminance.

I've tried changing drivers back and forth, refresh, config, etc., but no luck. Currently using the Linptech 24Ghz Presence Sensor ES1 driver. The setup on all ES1's look identical.

App: 46
Manufacturer: _TS3218_awarhusb
Model: TS0225
Tuya Ver: 1.0.6

The only discrepency i see is with the State Variables. Some devices have just 3, while others have 11 and still others have 5.

Any ideas on how to get this working? Many thanks.

I just realized today from another thread that these even do illuminance with this driver. So I swapped out the drivers for my five sensors with this driver, and I got illuminance values!

Though all my sensors got an initial illuminance value after updating to this driver, that was it. Logs show it never updates after first shot. I can reset the driver and I will again get one initial reading, then nothing after. The value it sends is an accurate illuminance value for that one send, it just doesn't keep sending. I've tested restarting the driver for them with different light levels, and it is getting a true value for light when it does send illuminance that one time. So there is a sensor in there, but it is not reporting based on continued change.

I does seem to wait for an illuminance change before it actually make the attribute first appear after a driver reset, but after that, no level of light change will send an update.

I have three Linptech and two MOES. All acting exactly the same with illuminance not reporting after initial driver install.

So, after all the help, i went back to basics and looked at the cable and power. I had the USB plugged into a dual port wall plug. I am using them elsewhere in the house...no problem.

In this particular case, the other port is being used by an iTach WF2IR unit. Once I plugged the Linptech into its own wall plug, problem solved. Is it possible that ES1 wasnt getting enough power to run the Lux sensor?

In any case, its working fine now, but I'd be interested in thoughts. Thanks again, all.

1 Like

The plug you're using and USB plugs in general is not one of my areas of expertise, but I suppose if the other device was being a power-hog it might have starved the Linptech. That, or:

  • There was a general problem w/the port on the double-plug the Linptech was connected to
  • The reboot of the Linptech when you unplugged/replugged it resolved the problem
  • Your visit to the Oracle of Delphi and offerings to the gods fixed it

I'm leaning towards the Oracle. :wink:

1 Like

+1 for the Oracle!!! We had done numerous restarts with nothing. A poor port does make sense, however.

1 Like

Is there any way to disable the blue LED when it detects motion?

With f/w 1.0.6, yes. Earlier firmware, no.

Not sure if there's newer f/w than 1.0.6 these days, but that was one of the updates (maybe the only one? :person_shrugging:) that came with 1.0.6

So I looked through the device using this driver and the built-in driver but couldn't find a way to update the firmware. Is there a special process on this device?

The one I'm currently using came with 1.0.6. I don't know if Hubitat has that version for updating or not.

Where does it show the firmware version at? From what I can tell neither driver shows it for me.

I'm using Krassimr's driver and it's in the Device Data section on the Device info page.

You can update the firmware using a Tuya hub, IIRC. Should be info earlier on in this thread...

@danabw Is there no way to do it without that hub?

@hydro311 This is all mine shows in that section.

Not that I remember...

This is mine...

I have 5 and all of them are like this