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,
Hence all the problems. I think I'll remove it and add it again and start over.
Let the driver automatically determine the 'Device Profile' based on the fingerprint. Do not manually change the profile.
Will do
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?
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:
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
Can you try to follow precisely the steps 2-8, please?
@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?
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
No worries, we should be able to find a where the problem is. The same device seems to be working fine for others.
Thanks again for your help.
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)
Yes, as of now I have two of these toys, hardware is a bit different:
This one has Micro USB connector:
And this one has USB-C conector:
Both are working perfectly fine with 4-in-1 driver but for both I am using this profile:
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.
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 :
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.
OK, I will follow yours recommendations. These two sensors are in very WAF sensitive areas
(Bathroom and Kitchen lighting control). Braking these automation will be a disaster.
Just find the right time... : ) For me, these times are when my wife goes to visit her mother, who lives in another town! : )
To avoid any WAF risks, save a copy of version 1.3.7 and use it for these two sensors.
But you will need the latest versions of the 'standard' driver for any other Tuya mmWave sensors that you may decide to try later.
This one (potentially mmWave/PIR Combo with (maybe) battery backup) will be in tomorrow:
https://www.amazon.com/dp/B0CDRBX1CQ?psc=1&ref=ppx_yo2ov_dt_b_product_details
Let me see will it work (I hope). I'll certainly let you know my first impression.
After recommended steps
v:12182023-08-25 07:21:40.829 PMdebugKitchen 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 00636D02000400000000
dev:12182023-08-25 07:21:40.247 PMdebugKitchen Presence Sensor ignored illuminance event 3 lux - change is less than 5 lux threshold!
dev:12182023-08-25 07:21:40.244 PMdebugKitchen Presence Sensor Tuya cluster: dp_id=2 dp=104 fncmd=3
dev:12182023-08-25 07:21:40.241 PMdebugKitchen Presence Sensor parse (_TZE204_sxm7l9xa, 1.4.4 2023/08/18 10:43 PM) descMap = [raw:catchall: 0104 EF00 01 01 0040 00 335B 01 00 0000 02 01 00626802000400000003, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:335B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 62, 68, 02, 00, 04, 00, 00, 00, 03]]
dev:12182023-08-25 07:21:40.237 PMdebugKitchen 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 00626802000400000003
dev:12182023-08-25 07:21:39.691 PMdebugKitchen Presence Sensor ignored motion inactive event after 111s
dev:12182023-08-25 07:21:39.688 PMdebugKitchen Presence Sensor radar presence event DP=0x69 (105) fncmd = 0
dev:12182023-08-25 07:21:39.685 PMdebugKitchen Presence Sensor Tuya cluster: dp_id=4 dp=105 fncmd=0
dev:12182023-08-25 07:21:39.682 PMdebugKitchen Presence Sensor parse (_TZE204_sxm7l9xa, 1.4.4 2023/08/18 10:43 PM) descMap = [raw:catchall: 0104 EF00 01 01 0040 00 335B 01 00 0000 02 01 00616904000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:335B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 61, 69, 04, 00, 01, 00]]
dev:12182023-08-25 07:21:39.679 PMdebugKitchen 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 00616904000100
dev:12182023-08-25 07:21:39.623 PMdebugKitchen 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 00606D02000400000000
dev:12182023-08-25 07:21:39.575 PMdebugKitchen Presence Sensor Tuya cluster: dp_id=2 dp=110 fncmd=600
This text will be hidden
Thank you for the logs - what is included seems fine! Your 'fading time' parameter is set to 60 . so the presence sensor should report inactivity after 60 seconds without motion detected.
The logs are however incomplete, I can expect about 40-50 lines of debug logs to follow the power off/on sequence. You will need to select more than one page of the live logs - while holding the mouse left button down, rotate the mouse wheel - this will scroll down the live logs page, allowing you to select all of the logs.
When you click on the Refresh button, do you see a lot of debug logs? Some devices will report back all their specific parameters on the Refresh command, some will not. You can try copying these logs, that follow the Refresh command.
Actually, what problem are you experiencing at the moment? (with the right SXM7L9XA profile)
Download the Hubitat app
