It should have worked with the old version too... 
Hey there @kkossev I'm hoping you can assist me please.
I'm trying to get this wretched device to work...
It pairs almost instantly, using your 4-in-1 driver. I was happy!!! 
However, I'm not getting any motion activity.
Trawling the threads here I saw reference to your mmWave driver so I'm also tried that, unfortunately also without success.
I am sad!!! 
Any ideas what I can try next? Unfortunately I was stupid and bought a whole bunch of these duh
Here's some screenshots of the device pages, in case they help shed some light on the problem...
Hi Angus,
First, make sure you are on the development branch version of the Tuya mmWave Sensors driver :
You can use this procedure for a quick manual update of the driver.
1 Like
ok, thank you i will try it.
1 Like
No Angus, this is a picture, just pixels... "ZY-M100-L" are just letters, numbers and dashes printed on the box... A device built on the Tuya platform can not be identified by this.
1 Like
ok 
OMG it works!!!
You are a star
Thank you so much for all your hard work.
1 Like
Is there a way for the TS0225 to reset to 0 targetDistance after idle/inactive like the FP1E?
@kkossev
1 Like
Here’s a custom profile for this random $4 aliexpress sensor. Works great.
CK-BL702 Type 1 mmWave presence (motion-only) (ZG-204ZE)
{
"deviceProfiles": {
"CK_BL702_MWS_01_RADAR": {
"description": "CK-BL702 mmWave presence sensor (ZG-204ZE)",
"device": { "powerSource": "battery" },
"capabilities": { "MotionSensor": true, "Battery": true, "IlluminanceMeasurement": false },
"preferences": {
"radarSensitivity": "2",
"fadingTime": "102",
"ledIndicator": "108"
},
"fingerprints": [
{
"profileId": "0104",
"endpointId": "01",
"model": "CK-BL702-MWS-01(7016)",
"manufacturer": "ZG-204ZE",
"deviceJoinName": "CK-BL702 mmWave presence sensor"
}
],
"attributes": [
{
"at": "0x0406:0x0000",
"name": "motion",
"type": "enum",
"rw": "ro",
"min": 0,
"max": 1,
"defVal": "0",
"scale": 1,
"map": { "0": "inactive", "1": "active" },
"title": "<b>Occupancy state</b>",
"description": "<i>Occupancy state</i>"
}
],
"tuyaDPs": [
{
"dp": 1,
"name": "motion",
"type": "enum",
"rw": "ro",
"min": 0,
"max": 1,
"defVal": "0",
"scale": 1,
"map": { "0": "inactive", "1": "active" },
"title": "<b>Presence state</b>",
"description": "<i>Presence state</i>"
},
{
"dp": 110,
"name": "battery",
"type": "number",
"rw": "ro",
"min": 0,
"max": 100,
"defVal": "0",
"scale": 1,
"unit": "%",
"title": "<b>Battery</b>",
"description": "<i>Battery percentage</i>"
},
{
"dp": 2,
"name": "radarSensitivity",
"type": "number",
"rw": "rw",
"min": 0,
"max": 19,
"defVal": 10,
"scale": 1,
"unit": "x",
"title": "<b>Radar sensitivity</b>",
"description": "<i>The larger the value, the more sensitive it is (refresh and update only while active)</i>"
},
{
"dp": 102,
"name": "fadingTime",
"type": "number",
"rw": "rw",
"min": 0,
"max": 28800,
"defVal": 30,
"scale": 1,
"unit": "seconds",
"title": "<b>Fading time</b>",
"description": "<i>Motion keep time</i>"
},
{
"dp": 108,
"name": "ledIndicator",
"type": "enum",
"rw": "rw",
"map": { "0": "OFF", "1": "ON" },
"defVal": "1",
"title": "<b>LED indicator</b>",
"description": "<i>LED indicator mode</i>"
}
],
"refresh": ["queryAllTuyaDP"],
"configuration": { "battery": true },
"comments": ["CK_BL702_MWS_01_RADAR",
"https://www.aliexpress.us/item/3256809396163686.html?gatewayAdapt=glo2usa"
]
}
},
"version": "4.2.0",
"timestamp": "2026-2-20 8:58 PM",
"description": "CUSTOM Device profiles for Tuya Zigbee mmWave Sensor",
"author": "kkossev"
}
2 Likes
The Type 1 is for Z2M. I haven't used MQTT on my hub before. Would I need to buy or install anything in addition to getting the sensor?
no, they say it's only supported by zibgee2mqtt but it's just standard zigbee. hub finds it just fine and it works with the base driver but this profile lets you configure the sensitivity.
1 Like
Maybe someone has a normally working drivers presence sensor: Manufacturer_TZE204_aai5grix Model TS0601. Thanks
1 Like
This is a new manufacturer (new SoC hardware version) of the "Wenzhi MTD285-ZB Human Presence Sensor" radar (rather complex device ...). Its fingerprint is not in the current JSON file, until I add it there, you can manually set the correct device profile:
2 Likes
Thanks, I will try.
1 Like
It works, but if a person sits still, the motion sensor becomes inactive. Can this sensor not register a person's presence?
I'm having trouble with ZG-204ZV showing illuminance values, however I can configure the offset.
Loaded from Github, loaded all defaults. Still no go, strange thing is I got one sensor to work and couldn't get the other 2 working.
Appreciate any help/ideas.
I'm using this device: _TZ3218_t9ynfz4x with the ver. 4.0.3 driver. The device is set with a "fading time" of 10sec. The actual time to transition from "active" to "inactive" can often be many minutes. Is this a quirk of the device over which the driver has no control, and is the error indicated in the log snippet below related to the problem?
EDIT: device profile is "TS0225_LINPTECH_RADAR"; running on a C-8, firmware 2.4.4.155.
dev:732026-03-30 12:08:01.593 AMinfo
Motion Sensor - Presence - Office (round) TU Motion is active 120s
dev:732026-03-30 12:07:01.871 AMinfo
Motion Sensor - Presence - Office (round) TU occupiedTime is 1 minutes
dev:732026-03-30 12:07:01.817 AMinfo
Motion Sensor - Presence - Office (round) TU Motion is active 60s
dev:732026-03-30 12:06:02.040 AMinfo
Motion Sensor - Presence - Office (round) TU Detected motion
dev:732026-03-30 12:05:42.806 AMerror
groovy.lang.MissingMethodException: No signature of method: user_driver_kkossev_Tuya_Zigbee_mmWave_Sensor_743.refresh() is applicable for argument types: (java.lang.String) values: [inactive]
dev:732026-03-30 12:05:34.744 AMinfo
Motion Sensor - Presence - Office (round) TU occupiedTime is 0 minutes
dev:732026-03-30 12:05:32.397 AMinfo
Motion Sensor - Presence - Office (round) TU Motion reset to inactive after 476s
dev:732026-03-30 12:04:35.038 AMinfo
Motion Sensor - Presence - Office (round) TU occupiedTime is 7 minutes [refresh]
dev:732026-03-30 12:04:34.972 AMinfo
Motion Sensor - Presence - Office (round) TU Motion is active 418s
dev:732026-03-30 12:04:32.664 AMinfo
Motion Sensor - Presence - Office (round) TU staticDetectionSensitivity is 5 [refresh]
Hi John,
Please update the driver to the latest version 4.2.1 (2025-10-19). Also, click on the "Load Standard Profiles From GitHub" button to ensure you have the latest device profile definitions.
The 'No signature...' error is rather strange, please check in the Events tab if any app is calling the 'refresh()' method?
A 'fading time' of 10 seconds is difficult to achieve with most of the cheap mmWave sensors. The sensor must operate in nearly ideal conditions - no interference sources, no electromagnetic fields nearby, no multi-path reflections, carefully selected sensitivity parameters (both static sensitivity and motion sensitivity), limited max distance ranges, etc, etc..
Try decreasing the Static Detection Sensitivity.
4 Likes
Thank you, the latest driver, setting a 30s fade time, and decreasing the Static Detection Sensitivity to medium seems to have worked perfectly!
3 Likes