[New device support]: TS0601 _TZE204_7gclukjs #21738

ayasystems · 2024-03-09T22:29:48Z

Link

https://es.aliexpress.com/item/1005004704966668.html?spm=a2g0o.order_list.order_list_main.39.2d6d194dDYF1wq&gatewayAdapt=glo2esp

Database entry

{"id":12,"type":"Router","ieeeAddr":"0xa4c1385c2518322c","nwkAddr":57339,"manufId":4417,"manufName":"_TZE204_7gclukjs","powerSource":"Mains (single phase)","modelId":"TS0601","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[4,5,61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0601","manufacturerName":"_TZE204_7gclukjs","powerSource":1,"zclVersion":3,"appVersion":74,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":74,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1710022644573}

Comments

Version Zigbee 24G
manufacturerName _TZE204_7gclukjs

I don't have tuya brigde to get the correct datapoints

2024-03-09 23:29:10Datapoint 104 not defined for '_TZE204_7gclukjs' with value 1
2024-03-09 23:29:10Datapoint 104 not defined for '_TZE204_7gclukjs' with value 1
2024-03-09 23:29:10Datapoint 9 not defined for '_TZE204_7gclukjs' with value 13
2024-03-09 23:29:10Datapoint 103 not defined for '_TZE204_7gclukjs' with value 5
2024-03-09 23:29:10Datapoint 2 not defined for '_TZE204_7gclukjs' with value 0
2024-03-09 23:29:10Datapoint 102 not defined for '_TZE204_7gclukjs' with value 0
2024-03-09 23:29:11Datapoint 3 not defined for '_TZE204_7gclukjs' with value 75
2024-03-09 23:29:11Datapoint 4 not defined for '_TZE204_7gclukjs' with value 750
2024-03-09 23:29:11Datapoint 105 not defined for '_TZE204_7gclukjs' with value 5
2024-03-09 23:29:11Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:11Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:11Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:11Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:11Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:12Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:13Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:14Datapoint 255 not defined for '_TZE204_7gclukjs' with value false
2024-03-09 23:29:14Datapoint 255 not defined for '_TZE204_7gclukjs' with value false
2024-03-09 23:29:14Datapoint 1 not defined for '_TZE204_7gclukjs' with value 1
2024-03-09 23:29:14Datapoint 104 not defined for '_TZE204_7gclukjs' with value 1
2024-03-09 23:29:14Datapoint 9 not defined for '_TZE204_7gclukjs' with value 12
2024-03-09 23:29:14Datapoint 103 not defined for '_TZE204_7gclukjs' with value 5
2024-03-09 23:29:14Datapoint 2 not defined for '_TZE204_7gclukjs' with value 0
2024-03-09 23:29:14Datapoint 2 not defined for '_TZE204_7gclukjs' with value 0
2024-03-09 23:29:14Datapoint 102 not defined for '_TZE204_7gclukjs' with value 0
2024-03-09 23:29:14Datapoint 3 not defined for '_TZE204_7gclukjs' with value 75

External definition

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
            e.presence(), e.illuminance_lux(), 
        ],
        meta: {
            tuyaDatapoints: [
     
            ],
    },
};

module.exports = definition;

ayasystems · 2024-03-09T22:58:33Z

Atacched an excel with all datapoints registered in debug mode

datapoints_debug.xlsx

DataPOint 1 has 0 1 2 values
DataPoint 2 is always 0
DataPoint 3 is always 75
DataPoint 4 is always 750
DataPoint 9 seems be distance
DataPoint 102 always 0
DataPoint 103 seems be other distance
DataPoint 104 has 0 and 1 value
DataPoint 105 is always 5
Datapoint 255 is always false

I hope it can be usefull to create the conversion.

Regards!

ayasystems · 2024-03-10T07:55:03Z

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				exposes.enum('approach_distance', ea.STATE, ['none', 'small_movement', 'large_movement'])
					.withDescription('traffic of movement from the point of view of the radar'),
				e.presence(), 
				 exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				 exposes.numeric('current_distance2', ea.STATE).withDescription('Distance to target 2').withUnit('cm'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'approach_distance', tuya.valueConverterBasic.lookup({'none': 0, 'small_movement': 1, 'large_movement': 2})],
				[103, 'current_distance', tuya.valueConverter.raw],
				[9, 'current_distance2', tuya.valueConverter.raw],
            ],
    },
};

module.exports = definition;

I've tested this settings and here is the result:

ayasystems · 2024-03-15T11:48:39Z

I have bought a zigbee bridge to extract all datapoints. I will back soon

yarik-m · 2024-03-18T16:25:02Z

hi, DP103 its illuminance

Vallefor · 2024-03-19T22:53:55Z

Updated it a little. Can't determine delay datapoint, but in other parameters I am sure (have tuya gateway).

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				exposes.enum('state', ea.STATE, ['none', 'presence', 'move']),
				e.presence(), 
				 exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				 exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				 exposes.numeric('radar_sensitivity', ea.STATE_SET).withValueMin(0).withValueMax(9).withValueStep(1).withDescription('sensitivity of the radar'),
				 exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Minimum range').withUnit('cm'),
				 exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Maximum range').withUnit('cm'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'presence': 1, 'move': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
                		[105, 'radar_sensitivity', tuya.valueConverter.raw],
                		[3, 'minimum_range', tuya.valueConverter.raw],
                		[4, 'maximum_range', tuya.valueConverter.raw],
                
            ],
    },
};

module.exports = definition;

ayasystems · 2024-03-22T11:26:41Z

I can see these values with tuya bridge on iot.tuya cloud

{"1":"Induction state"
,"2":"Motion Sensitivity"
,"3":"Near Detection"
,"4":"Far Detection"
,"9":"Target distance"
,"102":"Presence Sensitivity"
,"103":"Illuminance Value"
,"104":"有无人状态"
,"105":"Delay Time"}

and these options to set values

So i think this is correct.

Note that state has beed changed to none/presence/Move and presence and seems works fine


const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(), 
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay_time', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),		
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),		
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay_time',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],
				
            ],
    },
};

module.exports = definition;

Koenkk · 2024-03-23T09:02:50Z

looks good, could you make a pull request?

justicepng · 2024-03-23T11:55:48Z

I can see these values with tuya bridge on iot.tuya cloud

{"1":"Induction state" ,"2":"Motion Sensitivity" ,"3":"Near Detection" ,"4":"Far Detection" ,"9":"Target distance" ,"102":"Presence Sensitivity" ,"103":"Illuminance Value" ,"104":"有无人状态" ,"105":"Delay Time"}

and these options to set values

So i think this is correct.

Note that state has beed changed to none/presence/Move and presence and seems works fine


const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(), 
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay_time', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),		
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),		
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay_time',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],
				
            ],
    },
};

module.exports = definition;

I can't change any value like sensitivity.....

BartCardan · 2024-04-05T09:59:09Z

I am trying to integrate exact this device. Is it already possible to add it with an external convertor? Or should I wait a bit? Could you please give me instructions how to?

smithbill17 · 2024-04-05T10:53:37Z

I've also just bought this device & trying to understand where I can find the latest appropriate external converter to try?

smithbill17 · 2024-04-05T13:33:13Z

I just bought one of these devices on AliExpress & discovered that Zigbee2MQTT didn't recognise it. Google brought me here & using the details that the clever guys above posted, I've got it working now - thank you!

Just to help others that Google brings here, I simply copied the code ayasystems posted above pasted it into a file I named _TZE204_7gclukjs.js (I don't know if I needed to, but I removed the 'const extend' line mentioned in issue #22026 ), then saved the file in my zigbee2mqtt folder within HomeAssistant.

Then I went to the Zigbee2MQTT frontend & within the menu there I selected Settings > External converters and then added the _TZE204_7gclukjs.js file I saved earlier.

Restarted HomeAssistant & now my Presence sensor seems to be working fine 😁

I'm not sure about all the various available parameters as essentially I'm just using presence yes/no, but it works fine, so I'm happy.

Thank you guys 👍

Vallefor · 2024-04-05T13:46:41Z

This converter works fine for me. I used all from @ayasystems comment and changed delay_time to delay. Do not know why but delay_time everytime throw an error. May be it some kind of reserved property...

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(), 
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(1).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),		
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),		
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay', tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],
				
            ],
    },
};

module.exports = definition;

anushian · 2024-04-06T14:28:35Z

I just bought one of these devices on AliExpress & discovered that Zigbee2MQTT didn't recognise it. Google brought me here & using the details that the clever guys above posted, I've got it working now - thank you!

Just to help others that Google brings here, I simply copied the code ayasystems posted above pasted it into a file I named _TZE204_7gclukjs.js (I don't know if I needed to, but I removed the 'const extend' line mentioned in issue #22026 ), then saved the file in my zigbee2mqtt folder within HomeAssistant.

Then I went to the Zigbee2MQTT frontend & within the menu there I selected Settings > External converters and then added the _TZE204_7gclukjs.js file I saved earlier.

Restarted HomeAssistant & now my Presence sensor seems to be working fine 😁

I'm not sure about all the various available parameters as essentially I'm just using presence yes/no, but it works fine, so I'm happy.

Thank you guys 👍

Thanks for taking the time to write these helpful step by step instructions, my sensor appears to be working fine now 👍. Just to note. I did need to remove the 'const extend' line mentioned in issue #22026 for it to work (didnt work if I left it in).

And thanks to all the other posters above for their work on getting this supported!

shalak · 2024-04-11T11:42:03Z

This one appears to work correctly:

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(),
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],

            ],
    },
};

module.exports = definition;

(i.e. without the const extend = ... and delay_time -> delay)

However, the problem is that it's triggering the presence sensor when nobody's around. I tried tuning the motion_sensitivity - both with low and high values, and it's still detecting motion. I have another sensor, but of 5GHz type and that one works just fine.

May this be a case of a faulty unit, or is there something I can try to fix this?

anno73 · 2024-04-11T15:44:54Z

I have same device. Upon first plugin and registering I got a whole lot of error messages in z2m.
With initial instructions from #21738 (comment) and file from #21738 (comment) (I had to place the file within docker_data_dir/data) errors are gone now.
But I only get linkquality messages and no motion.
Also when I check the exposes tab in the device I only see "Empty exposes definition". Is this to be expected?

ayasystems · 2024-04-11T16:22:44Z

I have same device. Upon first plugin and registering I got a whole lot of error messages in z2m. With initial instructions from #21738 (comment) and file from #21738 (comment) (I had to place the file within docker_data_dir/data) errors are gone now. But I only get linkquality messages and no motion. Also when I check the exposes tab in the device I only see "Empty exposes definition". Is this to be expected?

Did you set external_converter into yaml ?

anno73 · 2024-04-11T17:16:24Z

Yes it is there.
I moved the file to the same directory as configuration.yaml and after a restart the Exposes tab shows a lot entries. And so do the mqtt messages. Seems to work now :-)

heiko1988 · 2024-04-11T17:25:01Z

Thank you, this has been very helpful!

I've been able to integrate z2m successfully and it's working quite well within iobroker.
I'm running z2m separately without any issues. However, I'm encountering a single problem:
the current_distance value consistently displays between 10-50cm, while my actual distance is around 300-400cm.

yarik-m · 2024-04-12T08:26:57Z

Hi, this in log zigbee2mqtt "Note that external converters are not meant for long term usage, it's meant for local testing after which a pull request should be created to add out-of-the-box support for the device"

yarik-m · 2024-04-12T08:31:16Z

Does everyone's external converter fall off?

thombec · 2024-04-12T08:40:03Z

Hello, I have the issue, that the vendor: _TZE204_7gclukjs is unknown at Homeassistant/zigbee2mqtt for zigbeemodel TS0601
I found your code here at this page to let the radar sensor run - how I have to implement it into zigbe2mqtt in homeassistant?
thank you in advance for help :-)

smithbill17 · 2024-04-12T08:44:34Z

Hello, I have the issue, that the vendor: _TZE204_7gclukjs is unknown at Homeassistant/zigbee2mqtt for zigbeemodel TS0601 I found your code here at this page to let the radar sensor run - how I have to implement it into zigbe2mqtt in homeassistant? thank you in advance for help :-)

See my comment above for basic instructions.

shalak · 2024-04-12T09:33:23Z

Hello, I have the issue, that the vendor: _TZE204_7gclukjs is unknown at Homeassistant/zigbee2mqtt for zigbeemodel TS0601 I found your code here at this page to let the radar sensor run - how I have to implement it into zigbe2mqtt in homeassistant? thank you in advance for help :-)

You need to:

Create a file with e.g. _TZE204_7gclukjs.js in /share/zigbee2mqtt folder in Home Assistant and paste the content there
Add the _TZE204_7gclukjs.js via the zigbee2mqtt Settings -> Settings -> External Converters -> "+"
Restart zigbee2mqtt via the Add-On panel

ayasystems · 2024-04-12T09:34:49Z

looks good, could you make a pull request?

I dont know the steps to do it. Could you do it?

Regards

casa3c · 2024-04-13T07:00:06Z

Can I use this converter code for ZHA by adding the code as a new quirk file?
I do not use zigbee2mqtt

thombec · 2024-04-13T08:20:28Z

After implementing the code above via "external converters" my device now shows the right parameters. Perfect - thank you!

But a problem was discovered after adding the device. Battery-powered sensors nearby have lost connection to the server after start running the device. A large number of errors from this devices suddenly appear in the log from Zigbee2MQTT.

one example of the errors:

After deleting of the device this problem was gone. It seems that the repeater functionality does not work properly. Did you also notice this behaviour?

opravdin · 2024-04-25T10:25:32Z

For people struggling to make this thing work stable: I found this setup working good.

Sensitivity 8/10
Detection range 375 to 675 cm
Delay 1s

It looks like value decoding is some way wrong, so these values don't make sense, but actually it works perfectly fine in 3*4 meters kitchen (both motion and presence detection). Distance detection is a mess (showing 20ish cm while I'm 2.5 meters away).
UPD: I have 24Ghz version of this sensor
UPD2: I'm using the external converter from @Vallefor #21738 (comment)

matte-a · 2024-04-28T18:13:39Z

For people struggling to make this thing work stable: I found this setup working good.

Sensitivity 8/10

Detection range 375 to 675 cm

Delay 1s

It looks like value decoding is some way wrong, so these values don't make sense, but actually it works perfectly fine in 3*4 meters kitchen (both motion and presence detection). Distance detection is a mess (showing 20ish cm while I'm 2.5 meters away). UPD: I have 24Ghz version of this sensor

With your advices the sensor is extremely fast to react. I couldn't believe it. Thank you so much!

Aksenov3000 · 2024-05-07T20:41:23Z

looks good, could you make a pull request?

Hello! Where I need place file with this converter to make pull request ?

gabriel403 · 2024-05-08T14:08:02Z

I'm trying to get this working on my haos on my rpi5
I've got the file in the right place with the content from one of the above comments , but it still says unsupported device

Warning 2024-05-08 15:04:54Device '0xa4c138522d992e20' with Zigbee model 'TS0601' and manufacturer name '_TZE204_7gclukjs' is NOT supported, please follow https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

gabriel403 · 2024-05-08T20:12:44Z

#22083 (comment)
This fixed it for me, looks like an update to ha needed some tweaks

exurb1aTR · 2024-05-21T21:03:43Z

This one appears to work correctly:

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(),
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],

            ],
    },
};

module.exports = definition;

(i.e. without the const extend = ... and delay_time -> delay)

However, the problem is that it's triggering the presence sensor when nobody's around. I tried tuning the motion_sensitivity - both with low and high values, and it's still detecting motion. I have another sensor, but of 5GHz type and that one works just fine.

May this be a case of a faulty unit, or is there something I can try to fix this?

I just used this exact converter and the device is up and running. However here is the problem, as you say motion_sensitivity does not affect the way sensor works. When i check the state it seem there are way more options to tweak:

We need more data points!!! @ayasystems

- reference - https://github.com/wzwenzhi/Wenzhi-ZigBee2mqtt/blob/main/zmzn24g.NEW.js - related links - Koenkk/zigbee2mqtt#22790 - Koenkk/zigbee2mqtt#21910 - Koenkk/zigbee2mqtt#21738

* fix(detect): Fix datapoints of `_TZE204_7gclukjs` - reference - https://github.com/wzwenzhi/Wenzhi-ZigBee2mqtt/blob/main/zmzn24g.NEW.js - related links - Koenkk/zigbee2mqtt#22790 - Koenkk/zigbee2mqtt#21910 - Koenkk/zigbee2mqtt#21738 * fix lint error and model name

pimpmytechno · 2024-06-03T19:26:09Z

This one appears to work correctly:

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(),
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],

            ],
    },
};

module.exports = definition;

(i.e. without the const extend = ... and delay_time -> delay)

However, the problem is that it's triggering the presence sensor when nobody's around. I tried tuning the motion_sensitivity - both with low and high values, and it's still detecting motion. I have another sensor, but of 5GHz type and that one works just fine.

May this be a case of a faulty unit, or is there something I can try to fix this?

I encountered an issue with the accuracy of the "Current Distance" measurement. When standing 2 meters away from the sensor, it indicates a distance of 20 cm. Can this be fixed somehow? Otherwise, the converter works without any complaints.

LeeWiu · 2024-06-14T14:13:25Z

This one appears to work correctly:

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'TS0601',
    vendor: 'TuYa',
    description: 'RadarTuya',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
        fromZigbee: [tuya.fz.datapoints],
        toZigbee: [tuya.tz.datapoints],
        exposes: [
				e.enum('state', ea.STATE, ['none', 'Presence', 'Move and presence']).withDescription('state of taget'),
				e.presence(),
				exposes.numeric('illuminance_lux', ea.STATE).withDescription('Illuminance').withUnit('lux'),
				exposes.numeric('current_distance', ea.STATE).withDescription('Distance to target').withUnit('cm'),
				exposes.numeric('delay', ea.STATE_SET).withValueMin(0).withValueMax(600).withValueStep(5).withDescription('Delay time').withUnit('s'),
				exposes.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(825).withValueStep(75).withDescription('Near Detection').withUnit('cm'),
				exposes.numeric('maximum_range', ea.STATE_SET).withValueMin(75).withValueMax(900).withValueStep(75).withDescription('Far Detection').withUnit('cm'),
				exposes.numeric('motion_sensitivity', ea.STATE_SET).withDescription('Motion Sensitivity').withValueMin(0).withValueMax(10).withValueStep(1).withDescription('Motion Sensitivity'),
        ],
        meta: {
            tuyaDatapoints: [
				[104, 'presence', tuya.valueConverter.trueFalse1],
				[1, 'state', tuya.valueConverterBasic.lookup({'none': 0, 'Presence': 1, 'Move and presence': 2})],
				[103, 'illuminance_lux', tuya.valueConverter.raw],
				[9, 'current_distance', tuya.valueConverter.raw],
				[105, 'delay',   tuya.valueConverter.raw],
                [3, 'minimum_range', tuya.valueConverter.raw],
                [4, 'maximum_range', tuya.valueConverter.raw],
                [2, 'motion_sensitivity', tuya.valueConverter.raw],

            ],
    },
};

module.exports = definition;

(i.e. without the const extend = ... and delay_time -> delay)
However, the problem is that it's triggering the presence sensor when nobody's around. I tried tuning the motion_sensitivity - both with low and high values, and it's still detecting motion. I have another sensor, but of 5GHz type and that one works just fine.
May this be a case of a faulty unit, or is there something I can try to fix this?

I encountered an issue with the accuracy of the "Current Distance" measurement. When standing 2 meters away from the sensor, it indicates a distance of 20 cm. Can this be fixed somehow? Otherwise, the converter works without any complaints.

Same here, usually stays at -3 cm and sometimes 20 cm but the biggest issue is with the log flooding every second...
This converter works only with Z2M Edge, on master branch will not detect motion.

Proncio · 2024-08-31T10:50:17Z

Quick note: there are 2 versions of the sensor, in and on wall. Code above is related to In Wall, to be used for On Wall, manufacturer name should be set to _TZE204_ya4ft0w4 in place of _TZE204_7gclukjs - otherwise it's not recognized

garanda21 · 2024-09-07T20:57:36Z

Quick note: there are 2 versions of the sensor, in and on wall. Code above is related to In Wall, to be used for On Wall, manufacturer name should be set to _TZE204_ya4ft0w4 in place of _TZE204_7gclukjs - otherwise it's not recognized

Just bought it the 24ghz On wall version but z2mqtt recognizes it as TZE204_7gclukjs and shows wrong image. On my case the device works it’s just recognizing it wrong.

EDIT: My actual device is this: https://www.zigbee2mqtt.io/devices/ZY-M100-24GV3.html (Detected one is ZY-M100-24GV2)

Also Distance value seems wrong, it shows negative number and values lower than 1, like 0.2 or 0.3, not corresponding to values on meters or centimeters like min distance and max distance values:

drupry · 2024-09-09T21:23:27Z

I have the _TZE204_7gclukjs ceiling version, so for me, the image is correct. However, I also have an issue with the Distance value. The default is -0.3, and when someone is present, the values are quite random, ranging from 0.1 to 0.5 approx. I don’t know what this Distance value represents because it has no unit. Should it be meters?

Another problem is with the Move sensitivity and Presence sensitivity sliders. The values are integers from 0 to 10, but no matter what number I set, after a couple of seconds, they revert to 0. I don’t know if they work at all.

opravdin · 2024-09-10T18:01:48Z

Another problem is with the Move sensitivity and Presence sensitivity sliders. The values are integers from 0 to 10, but no matter what number I set, after a couple of seconds, they revert to 0. I don’t know if they work at all.

I had the same behavior. The only thing helped me is to power cycle the device. Change some parameters, reboot, fix wrong values and reboot again. Repeat until each value will be saved in a way you want it to. Also, I would highly recommend you a combination of values from my comment above. Got this thing working perfectly since then.

drupry · 2024-09-11T10:42:51Z

Change some parameters, reboot, fix wrong values and reboot again.

reboot how ? because every time I cut it from power, it sets random parameter to detection distance min and detection distance max and of course presence and motion sensitivity to 0

drupry · 2024-09-22T09:29:23Z

I bought exactly the same sensor (ceiling 24 GHz version 80-220V from the same vendor from Ali) _TZE204_7gclukjs and it pair itself as wall sensor _TZE204_ya4ft0w4. I tried to re-pair it several times but it always report itself as _ya4ft0w4.
Now the fun part: it works flawless! Distance still has no units (meters) but it reports correct values and I have none of the above mentioned issues!!!
Can someone fix this one (ceiling version) to work just perfect like the wall version _TZE204_ya4ft0w4 ?

Testingfor101 · 2024-09-29T09:33:54Z

With this configuration motion and presence sensitivity remains the same without going back to 0 or 1.
The original converter was using the incorrect value converter type.

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'ZY-M100-24GV2',
    vendor: 'Tuya',
    description: '24G MmWave radar human presence motion sensorEDITED',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    configure: tuya.configureMagicPacket,
    exposes: [
        e.enum('state', ea.STATE, ['none', 'presence', 'move']).withDescription('Presence state sensor'),
        e.presence().withDescription('Occupancy'),
        e.numeric('distance', ea.STATE).withDescription('Target distance'),
        e.illuminance_lux().withDescription('Illuminance sensor'),
        e.numeric('move_sensitivity', ea.STATE_SET)
            .withValueMin(1).withValueMax(10).withValueStep(1)
            .withDescription('Motion Sensitivity'),
        e.numeric('presence_sensitivity', ea.STATE_SET)
            .withValueMin(1).withValueMax(10).withValueStep(1)
            .withDescription('Presence Sensitivity'),
        e.numeric('detection_distance_min', ea.STATE_SET)
            .withValueMin(0).withValueMax(8.25).withValueStep(0.75)
            .withUnit('m').withDescription('Minimum range'),
        e.numeric('detection_distance_max', ea.STATE_SET)
            .withValueMin(0.75).withValueMax(9.0).withValueStep(0.75)
            .withUnit('m').withDescription('Maximum range'),
        e.numeric('presence_timeout', ea.STATE_SET)
            .withValueMin(1).withValueMax(1500).withValueStep(1)
            .withUnit('s').withDescription('Fade time'),
    ],
    meta: {
        tuyaDatapoints: [
            [104, 'presence', tuya.valueConverter.trueFalse1],
            [2, 'move_sensitivity', tuya.valueConverter.raw],
            [102, 'presence_sensitivity', tuya.valueConverter.raw],
            [3, 'detection_distance_min', tuya.valueConverter.divideBy100],
            [4, 'detection_distance_max', tuya.valueConverter.divideBy100],
            [9, 'distance', tuya.valueConverter.divideBy100],
            [105, 'presence_timeout', tuya.valueConverter.raw],
            [103, 'illuminance_lux', tuya.valueConverter.raw],
            [1, 'state', tuya.valueConverterBasic.lookup({none: 0, presence: 1, move: 2})],
        ],
    },
};

module.exports = definition;

drupry · 2024-09-29T21:02:16Z

With this configuration motion and presence sensitivity remains the same without going back to 0 or 1.
The original converter was using the incorrect value converter type.

Oh yes, this is working! Thank you @Testingfor101! I edited distance parametr to show unit (meters) and set divide parametr to 10 - now it's showing right values BUT!! the default value is still negative, in my case -0,3.

const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0601',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZE204_7gclukjs',
        },
    ],
    model: 'ZY-M100-24GV2',
    vendor: 'Tuya',
    description: '24G MmWave radar human presence motion sensorEDITED',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    configure: tuya.configureMagicPacket,
    exposes: [
        e.enum('state', ea.STATE, ['none', 'presence', 'move']).withDescription('Presence state sensor'),
        e.presence().withDescription('Occupancy'),
        e.numeric('distance', ea.STATE).withUnit('m').withDescription('Target distance'), 
        e.illuminance_lux().withDescription('Illuminance sensor'),
        e.numeric('move_sensitivity', ea.STATE_SET)
            .withValueMin(1).withValueMax(10).withValueStep(1)
            .withDescription('Motion Sensitivity'),
        e.numeric('presence_sensitivity', ea.STATE_SET)
            .withValueMin(1).withValueMax(10).withValueStep(1)
            .withDescription('Presence Sensitivity'),
        e.numeric('detection_distance_min', ea.STATE_SET)
            .withValueMin(0).withValueMax(8.25).withValueStep(0.75)
            .withUnit('m').withDescription('Minimum range'),
        e.numeric('detection_distance_max', ea.STATE_SET)
            .withValueMin(0.75).withValueMax(9.0).withValueStep(0.75)
            .withUnit('m').withDescription('Maximum range'),
        e.numeric('presence_timeout', ea.STATE_SET)
            .withValueMin(1).withValueMax(1500).withValueStep(1)
            .withUnit('s').withDescription('Fade time'),
    ],
    meta: {
        tuyaDatapoints: [
            [104, 'presence', tuya.valueConverter.trueFalse1],
            [2, 'move_sensitivity', tuya.valueConverter.raw],
            [102, 'presence_sensitivity', tuya.valueConverter.raw],
            [3, 'detection_distance_min', tuya.valueConverter.divideBy100],
            [4, 'detection_distance_max', tuya.valueConverter.divideBy100],
            [9, 'distance', tuya.valueConverter.divideBy10],
            [105, 'presence_timeout', tuya.valueConverter.raw],
            [103, 'illuminance_lux', tuya.valueConverter.raw],
            [1, 'state', tuya.valueConverterBasic.lookup({none: 0, presence: 1, move: 2})],
        ],
    },
};

module.exports = definition;

Bjk8kds · 2024-09-30T10:31:41Z

Thanks alot of you ALL... Now my sensor working properly as it should!

Koenkk · 2024-10-01T18:51:58Z

Integrated the converter, will be available in todays release.

drupry · 2024-10-14T21:24:14Z

After a few days, the presence sensitivity and move sensitivity settings reset themselves to 0 again. I’m not sure if these settings are actually working because I haven’t noticed any difference in behavior. So, I’m okay with it.

jkaberg · 2024-10-15T05:35:32Z

After a few days, the presence sensitivity and move sensitivity settings reset themselves to 0 again. I’m not sure if these settings are actually working because I haven’t noticed any difference in behavior. So, I’m okay with it.

I'm seeing this aswell, and this in turn results in the following log spam in/from Home Assistant

2024-10-15 07:34:08.140 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_presence_sensitivity: 0 (range 1.0 - 10.0)
2024-10-15 07:34:08.140 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_move_sensitivity: 0 (range 1.0 - 10.0)
2024-10-15 07:34:08.190 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_presence_sensitivity: 0 (range 1.0 - 10.0)
2024-10-15 07:34:08.191 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_move_sensitivity: 0 (range 1.0 - 10.0)
2024-10-15 07:34:08.236 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_presence_sensitivity: 0 (range 1.0 - 10.0)
2024-10-15 07:34:08.236 ERROR (MainThread) [homeassistant.components.mqtt.number] Invalid value for number.inngang_bevegelsesensor_move_sensitivity: 0 (range 1.0 - 10.0)

Setting these back to 1 in the Z2M UI resolves it until next "reset" (which happens every other day it seems)

Is this the intended behavior @Koenkk ?

Koenkk · 2024-10-16T19:52:43Z

There are 2 errors here:

The value resetting to 0, this seems to be an issue of the device (can likely not be solved from z2m)
The Invalid value error in HA -> this will be fixed in the next z2m release (1 November), at least for the _TZE204_7gclukjs (not sure if you have a different one)

semsem54 · 2024-11-12T22:26:14Z

after hours of trying i finally managed to add my device and I see some values. I used the "ZY-M100-24GV3" from the converter of koenkk and this works best so far for my device. but the value for "target distance" is not korrekt (output is something around 30m). Presence sensitivity seems like an on/off switch and not a value...
TS0601_TZE200_clrdrnya 24G Motion Sensor
maybe someone as an idea how to configure properly?

github-actions · 2025-01-12T00:03:28Z

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

ayasystems added the new device support New device support request label Mar 9, 2024

yhbyhb mentioned this issue Jun 3, 2024

Fix datapoints of Tuya TS0601 _TZE204_7gclukjs Koenkk/zigbee-herdsman-converters#7600

Merged

cygnusb mentioned this issue Jul 4, 2024

[Device Support Request] TS0601 _TZE204_7gclukjs . Presence Sensor zigpy/zha-device-handlers#3112

Closed

Bjk8kds mentioned this issue Sep 30, 2024

ZY-M100-24GV2 cannot change the Move and Presence Sensitivity setting #23949

Closed

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Oct 1, 2024

fix: Fix Tuya ZY-M100-24GV2 integration Koenkk/zigbee2mqtt#21738

fedd916

Koenkk mentioned this issue Oct 1, 2024

chore(master): release 20.21.0 Koenkk/zigbee-herdsman-converters#8052

Merged

xf1nk3lx mentioned this issue Nov 18, 2024

Zigbee Human Presence Sensor TS0601 from _TZE204_7gclukjs ioBroker/ioBroker.zigbee#2295

Closed

github-actions bot added the stale Stale issues label Jan 12, 2025

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2025

[New device support]: TS0601 _TZE204_7gclukjs #21738

[New device support]: TS0601 _TZE204_7gclukjs #21738

Comments

ayasystems commented Mar 9, 2024

Link

Database entry

Comments

External definition

ayasystems commented Mar 9, 2024 • edited Loading

ayasystems commented Mar 10, 2024 • edited Loading

ayasystems commented Mar 15, 2024

yarik-m commented Mar 18, 2024

Vallefor commented Mar 19, 2024

ayasystems commented Mar 22, 2024 • edited Loading

Koenkk commented Mar 23, 2024

justicepng commented Mar 23, 2024

BartCardan commented Apr 5, 2024

smithbill17 commented Apr 5, 2024

smithbill17 commented Apr 5, 2024

Vallefor commented Apr 5, 2024

anushian commented Apr 6, 2024

shalak commented Apr 11, 2024

anno73 commented Apr 11, 2024

ayasystems commented Apr 11, 2024

anno73 commented Apr 11, 2024

heiko1988 commented Apr 11, 2024

yarik-m commented Apr 12, 2024 • edited Loading

yarik-m commented Apr 12, 2024

thombec commented Apr 12, 2024

smithbill17 commented Apr 12, 2024

shalak commented Apr 12, 2024

ayasystems commented Apr 12, 2024

casa3c commented Apr 13, 2024 • edited Loading

thombec commented Apr 13, 2024

opravdin commented Apr 25, 2024 • edited Loading

matte-a commented Apr 28, 2024

Aksenov3000 commented May 7, 2024 • edited Loading

gabriel403 commented May 8, 2024

gabriel403 commented May 8, 2024

exurb1aTR commented May 21, 2024 • edited Loading

pimpmytechno commented Jun 3, 2024

LeeWiu commented Jun 14, 2024

Proncio commented Aug 31, 2024

garanda21 commented Sep 7, 2024 • edited Loading

drupry commented Sep 9, 2024

opravdin commented Sep 10, 2024

drupry commented Sep 11, 2024

drupry commented Sep 22, 2024

Testingfor101 commented Sep 29, 2024

drupry commented Sep 29, 2024 • edited Loading

Bjk8kds commented Sep 30, 2024 • edited Loading

Koenkk commented Oct 1, 2024

drupry commented Oct 14, 2024

jkaberg commented Oct 15, 2024 • edited Loading

Koenkk commented Oct 16, 2024

semsem54 commented Nov 12, 2024

github-actions bot commented Jan 12, 2025

ayasystems commented Mar 9, 2024 •

edited

Loading

ayasystems commented Mar 10, 2024 •

edited

Loading

ayasystems commented Mar 22, 2024 •

edited

Loading

yarik-m commented Apr 12, 2024 •

edited

Loading

casa3c commented Apr 13, 2024 •

edited

Loading

opravdin commented Apr 25, 2024 •

edited

Loading

Aksenov3000 commented May 7, 2024 •

edited

Loading

exurb1aTR commented May 21, 2024 •

edited

Loading

garanda21 commented Sep 7, 2024 •

edited

Loading

drupry commented Sep 29, 2024 •

edited

Loading

Bjk8kds commented Sep 30, 2024 •

edited

Loading

jkaberg commented Oct 15, 2024 •

edited

Loading