Tuya Smart Human Presence Sensor Micromotion Detect Human Motion Detector ZigBee (TS0601 _TZE204_sxm7l9xa)

🛎️ Get Help Devices
21

Hi Art K,

The support of the many different models of mmWave presence sensors built on Tuya platform is rather complicated... not just in HE, but also in all other home automation systems different than Tuya,

Currently, the 4-in1 driver supports a total of 32 (thirty-two!) different Tuya-based mmWave radars, grouped in 13 (thirteen) different 'Device Profiles'.

In this thread, you mention this device :

image
image371×529 29.5 KB

This fingerprint corresponds to this device :

image
image1004×495 44 KB

Do you have this device?? It is totally different from the rest of the 12 mmWave radars.

In your last message the screenshot refers to _TZE204_sxm7l9xa. Is this the device you are trying to make working now?

Let's talk only about one device is this thread.

Also, I will need some debug logs copied and pasted as a text from a PC browser. I can not use mobile screenshots to simulate a device that I don't have when trying to reproduce a problem.

So, if we are going to continue with this _TZE204_sxm7l9xa radar:

  1. Switch to SXM7L9XA device profile. Do not use any other profiles, this is the profile intended to work with this device.
    image
    image547×563 58.2 KB
  2. Make sure the Debug logging is on.
  3. Turn off the device power supply for 10 seconds
  4. Clear the live logs
  5. Power on the device again
  6. Wait 10 seconds
  7. Copy and paste as a text all the debug logs that follow the moment when the device was powered on
  8. Please hide the log multiple lines in a Summary section like this (use the forum editor cog wheel tool) :
Summary

dev:41212023-08-25 13:43:53.323debugRadar TS0225 _TZE200_hl0ss9oa ignored illuminance event 92 lux - change is less than 10 lux threshold!
dev:41212023-08-25 13:43:53.319debugRadar TS0225 _TZE200_hl0ss9oa Tuya cluster: dp_id=2 dp=20 fncmd=916
dev:41212023-08-25 13:43:53.315debugRadar TS0225 _TZE200_hl0ss9oa parse: (_TZE200_hl0ss9oa, 1.5.0 2023/08/25 11:24 AM) descMap = [raw:catchall: 0104 EF00 01 01 0040 00 E9F1 01 00 0000 02 01 00371402000400000394, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:E9F1, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 37, 14, 02, 00, 04, 00, 00, 03, 94]]

1 Like
22

_TZE204_sxm7l9xa this it the device that I have. The white wall mount. I'll be back at about 10am or so and get back to you.
Appreciate your help.

1 Like
23

I just want to emphasize the fact that the device form factor ( round, rectangle, wall mount, ceiling mount, pedestal mount) doesn't matter.

The power supply (DC 5V (USB), DC 12V, or direct AC 230/110V) doesn't matter as well.

The device white label ( 'Moes', 'Avatto', 'Loginovo', 'Brilliant Smart', 'Nue', 'Ikuu', etc, etc...) doesn't matter as well. It is one and the same Tuya-based product inside.

The 'model' printed on the box ( 'M100', 'XYZ', etc...) doesn't matter also.

What uniquely identifies a Zigbee product are these 3 properties, which can be found on HE device web page, 'Device Details':

  • model
  • manufacturer
  • application
1 Like
24

That's an old one I had. Too much spam.

25

https://m.aliexpress.us/item/3256805291297545.html?spm=a2g0n.order_detail.order_detail_item.3.36def19cpjh4lC&gatewayAdapt=glo2usa

This is the one I have

26

AliExpress sellers add even more confusion - there are 2 dffierent form-factor Zigbee device and one WiFi device in this link.

AliExpress (also Amazon, also 3A Smart Home, also all other sites) do not mention the device model and manufacturer, as they don't know it.

It is not uncommon to receive two or more different devices even in one and the same batch / purchase order. The sellers don't make any difference, because they all work the same (or in a very similar way) with Tuya Zigbe gateways,

27

Hence all the problems. I think I'll remove it and add it again and start over.

1 Like
28

Let the driver automatically determine the 'Device Profile' based on the fingerprint. Do not manually change the profile.

29

Will do

30

I forgot to ask. After I reinstall the device should I update the device driver. Or update the driver first, or just keep the current driver?

31

Make sure you are always using the latest dev. branch version, when troubleshooting new devices.
It can be manually downloaded from the second link in the Tuya Zigbee Multi-Sensor 4 In 1 driver thread or from here:
https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Multi%20Sensor%204%20In%201/Tuya%20Multi%20Sensor%204%20In%201.groovy

A faster way to update is to click on the Import button:

image
image1499×568 87.8 KB

32

I installed new driver and reinstalled device...debug code below.

dev:12182023-08-25 11:13:36.117 AMdebugKitchen Presence Sensor parse (_TZE204_sxm7l9xa, 1.4.4 2023/08/18 10:43 PM) description = catchall: 0104 EF00 01 01 0040 00 335B 01 00 0000 02 01 00936D02000400000122

33

Can you try to follow precisely the steps 2-8, please?

34

@a.mcdear @user6222 @vitaliy_kh you have the same model/manufacturer device _TZE204_sxm7l9xa.

Is it working OK with the Tuya 4-in-1 driver version ver. 1.4.4 and SXM7L9XA profile?

35

I haven't done anything yet. My wife is working in that room so I can't mess with it yet. But since I installed the new driver and reincluded the detector the light hasn't gone off with the room occupied. Before it would turn off wait for the delay and turn on every 5 mins or so. But the debug is still showing.

Kitchen Presence Sensor parse (_TZE204_sxm7l9xa, 1.4.4 2023/08/18 10:43 PM) description = catchall: 0104 EF00 01 01 0040 00 335B 01 00 0000 02 01 00186D0200040000012D

36

No worries, we should be able to find a where the problem is. The same device seems to be working fine for others.

37

Thanks again for your help.

38

Yes. So far it seems to work mostly fine. I haven't really dug into it too much yet, but on a surface level, the driver and device appear to work properly. I have not noticed any immediate issues other than the chattiness of the device itself. (using the 1.4.4 18/8/23 driver)

1 Like
39

Yes, as of now I have two of these toys, hardware is a bit different:

This one has Micro USB connector:
image

And this one has USB-C conector:
image

Both are working perfectly fine with 4-in-1 driver but for both I am using this profile:
image

image

Whatever should be native and more appropriate profile produced a bit unstable performance
(I am sorry, I forgot what I did not like with SXM7L9XA profile).

And, BTW driver version is still 1.3.7 I did not upgrade to the latest driver version because
so far everything is working just fine and i don't want to brake things.

40

Yes, I remember now...

You can make a copy of the driver version that works fine - copy all the code, then click on 'New Driver' button and paste the copied code.

Then (before saving the code!), edit the driver name like this :
image

Finally, click on the Save button.

This way, the devices that are working fine with this old version can be assigned the modified driver with the new driver name.

For other devices that may need a newer version, use the latest 'standard' version from HPM or from the dev, branch version links.

I don't recommend using other device profiles for this _TZE204_sxm7l9xa device, some may work, but this is not guaranteed.

1 Like