[New device support]: for Tuya M100S with 24G radar #18237

DosPH · 2023-07-07T09:52:07Z

Link

https://shopee.ph/ZigBee-Wifi-24G-MmWave-Radar-Human-Presence-Motion-Sensor-With-Luminosity-Distance-Detection-5-110-220V-Tuya-Smart-Life-Home-DIY-i.458442746.21881172707?sp_atk=c89bca14-cb63-4ccb-acdf-36f123ccff3e&xptdk=c89bca14-cb63-4ccb-acdf-36f123ccff3e

Database entry

{"id":65,"type":"Router","ieeeAddr":"0xa4c13855222f4904","nwkAddr":2607,"manufId":4417,"manufName":"_TZE204_ijxvkhd0","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_ijxvkhd0","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":1688723423810,"defaultSendRequestWhen":"immediate"}

Comments

anyone have tried to have this new tuya m100s with 24G radar working? this is the same square wallmount type with a Type C connector as power source.

External converter

No response

Supported color modes

No response

Color temperature range

No response

vitaleg · 2023-07-12T22:35:26Z

I tried to connect using quirks in ZHA based on previous device models, and also with zigbee2mqtt using a converter from previous models. Nothing worked.
Looks like it's a brand new sensor, works on a completely different principle.

So, +1, add support, please.

DosPH · 2023-07-13T11:52:23Z

yes this new one. Tried ZHA and latest converter also not working.

mrstormbyte · 2023-07-18T17:01:01Z

Also waiting for support

TheDIYEd · 2023-07-19T13:40:40Z

I am trying to get the same for TZE204_qasjif9e. Nothing works so far.
I managed to make it work on ZHA but no control over sensitivity or anything so just sucks.
I am hoping a new converter in z2q might do the job.

rpearl · 2023-07-23T02:15:27Z

Try this https://gist.github.com/rpearl/553184b310b8aa50d7e37f6a000fac51 (for TZE204_qasjif9e at least)

gevorgmansuryan · 2023-07-24T12:02:03Z

Try this https://gist.github.com/rpearl/553184b310b8aa50d7e37f6a000fac51 (for TZE204_qasjif9e at least)

this one is not working correctly. _TZE204_ijxvkhd0 supports new events, move and presence

rpearl · 2023-07-24T17:35:56Z

So it goes. This was for TZE204_qasjif9e, and I don't have _TZE204_ijxvkhd0.

I was able to identify these datapoints by observing the Datapoint 'X' with value 'Y' not defined for '_TZE204_qasjif9e' log messages in zigbee2mqtt. I recommend trying the same for your device. This is not as easy as using the tuya gateway stuff but it can work.

VladKorr · 2023-07-27T06:09:28Z

I have _TZE204_ijxvkhd0 and tried to get datapoints by means of tuya gateway.
I got the results for DP:
DP; DP Name
1; Switch 1
2; Switch 2
7; Timer 1
8; Timer 2
101; Work Mode
102; Bright Value
103; Temp Value
104; Illuminance Value
105; 感应状态 (? inductive state)
106; 运动灵敏度 (? motion sensitivity)
107; Longest distance
109; target_distence
110; Delay time
111; 静止灵敏度 (?static sensitivity)
112; 有无人状态 (?unoccupied state)
Some DPs are in Chinese - (Google translation in brackets)

VladKorr · 2023-07-27T06:50:05Z

_TZE204_ijxvkhd0 is 24GHz and and it's different from a similar 5 GHz sensor.
I tried to make a converter for Z2M, but it doesn't work quite right with the sensor settings (Delay time, static sensitivity) and there is no way to set the minimum sensor response distance.
The current code of my converter is here:
https://github.com/VladKorr/ZY-M100-24G/blob/main/ZY-M100-24G.js

vincentBesseau · 2023-07-28T23:43:02Z

Hello @rpearl , how can I add your file for the "_TZE204_qasjif9e" device on my zigbee2mqtt ?
Do you have any process?
Thx in advance !

rpearl · 2023-07-28T23:45:25Z

https://www.zigbee2mqtt.io/guide/configuration/more-config-options.html#external-converters

Carabin79 · 2023-08-03T20:06:43Z

Hello, please help me add this new device _TZE204_ijxvkhd0 in Z2q , it's a new device that works in 24g.

Igor-Andrusevic · 2023-08-04T07:24:13Z

Hello!! Add this new device _TZE204_ijxvkhd0 in zigbee2mqtt

VladKorr · 2023-08-04T11:31:31Z

Hello, please help me add this new device _TZE204_ijxvkhd0 in Z2q , it's a new device that works in 24g.

Hello, try to add external converters to your z2m from link:
https://github.com/VladKorr/ZY-M100-24G/blob/main/ZY-M100-24G.js
How to do it you can see at:
https://www.zigbee2mqtt.io/guide/configuration/more-config-options.html#external-converters

Igor-Andrusevic · 2023-08-04T11:44:01Z

Благодарю. Буду проверять, на данный момент работает.

Hello, please help me add this new device _TZE204_ijxvkhd0 in Z2q , it's a new device that works in 24g.

Hello, try to add external converters to your z2m from link: https://github.com/VladKorr/ZY-M100-24G/blob/main/ZY-M100-24G.js How to do it you can see at: https://www.zigbee2mqtt.io/guide/configuration/more-config-options.html#external-converters

Carabin79 · 2023-08-04T19:36:51Z

Thank you it works

Koenkk · 2023-08-05T06:35:26Z

I've added the device for out-of-the-box support (from 1 September release). Thanks @VladKorr

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

BeFygo · 2023-08-05T12:13:10Z

I've added the device for out-of-the-box support (from 1 September release). Thanks @VladKorr

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

Hi,
Great work guys.

I noticed with the latest-dev docker that the Tuya M100S gets recognized out-of-the-box but throws (no converter available for '') for all the adjustable parameters except "fading_time".

Koenkk · 2023-08-06T06:55:31Z

@BeFygo fixed!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

leroyloren · 2023-08-06T07:57:07Z

Please, does this device flood the network like the previous model (ZY-M100-S_1)?

MTokarev · 2023-08-06T23:00:17Z

Try this https://gist.github.com/rpearl/553184b310b8aa50d7e37f6a000fac51 (for TZE204_qasjif9e at least)

I am a new user here and missing almost everything ;)
I have tried to add a custom converter and it works perfect.
The only thing here is illuminance. Looks like the value is coming divided by 10. If real illuminance is 40 then it shows 4.

Again, since I don't know how it works inside (I believe it should be fixed somewhere down in the code) I made a nasty workaround (pay attention to lookup_dictionary and the basic converter):

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 ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;

const maxLuxAvailableDividedBy10 = 100
const lookup_dictionary = {};
const range = [...Array(maxLuxAvailableDividedBy10).keys()];
range.forEach(key => lookup_dictionary[key * 10] = key);


const definition = {
    fingerprint: tuya.fingerprint('TS0601', ['_TZE204_qasjif9e']),
    model: 'ZY-M100-S',
    vendor: 'TuYa',
    description: 'Mini Human Breathe Sensor',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    exposes: [
        e.illuminance_lux(), e.presence(),
        e.numeric('target_distance', ea.STATE).withDescription('Distance to target').withUnit('m'),
        e.numeric('radar_sensitivity', ea.STATE_SET).withValueMin(0).withValueMax(9).withValueStep(1)
            .withDescription('sensitivity of the radar'),
        e.numeric('minimum_range', ea.STATE_SET).withValueMin(0).withValueMax(9.5).withValueStep(0.15)
            .withDescription('Minimum range').withUnit('m'),
        e.numeric('maximum_range', ea.STATE_SET).withValueMin(0).withValueMax(9.5).withValueStep(0.15)
            .withDescription('Maximum range').withUnit('m'),
        e.numeric('detection_delay', ea.STATE_SET).withValueMin(0).withValueMax(10).withValueStep(0.1)
            .withDescription('Detection delay').withUnit('s'),
        e.numeric('fading_time', ea.STATE_SET).withValueMin(0.5).withValueMax(1500).withValueStep(1)
            .withDescription('Fading time').withUnit('s'),
    ],
    meta: {
        tuyaDatapoints: [
            [1, 'presence', tuya.valueConverter.trueFalse1],
            [9, 'target_distance', tuya.valueConverter.divideBy100],
           
	    // This is a nasty fix to change illuminance report. We must multiply the value by 10
            // to get accurate value. The problem here is that the step = 10. So you won't see the value like 11 or 15
            // Only 10, 20, 30...
            [104, 'illuminance_lux', tuya.valueConverterBasic.lookup(lookup_dictionary)],
            
	    [2, 'radar_sensitivity', tuya.valueConverter.raw],
            [4, 'maximum_range', tuya.valueConverter.divideBy100],
            [3, 'minimum_range', tuya.valueConverter.divideBy100],
            [102, 'fading_time', tuya.valueConverter.divideBy10],
            [101, 'detection_delay', tuya.valueConverter.divideBy10],
        ],
    },
};

module.exports = definition;

BeFygo · 2023-08-07T17:00:12Z

@BeFygo fixed!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

Confirmed, great work!

BeFygo · 2023-08-07T17:05:16Z

@VladKorr great work!

I noticed when trying to change the values for "move_sensitivity" & "presence_sensitivity" that over time the changes get overwritten to standard values.

device: _TZE204_ijxvkhd0

sozoalvin · 2024-01-23T02:57:43Z

which is the current converter that is working now? reading a few posts up; looks like different people are using different converters posted by different people

imatrixcz · 2024-01-24T20:25:48Z

So this is manual for dummies like me:

In HA open File Editor
Click on Folder and down where is folder zigbee2mqt - open it
Click on icon "New File" and give it name ZY-M100-24G.js and inside paste the whole code "Updated My Aliexpress converter":

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 legacy = require('zigbee-herdsman-converters/lib/legacy');

const tuya = require('zigbee-herdsman-converters/lib/tuya');

const dataTypes = {
	raw: 0, // [ bytes ]
	bool: 1, // [0/1]
	number: 2, // [ 4 byte value ]
	string: 3, // [ N byte string ]
	enum: 4, // [ 0-255 ]
	bitmap: 5, // [ 1,2,4 bytes ] as bits
};

const dpMap = {
	dpPresenceState: 112, //是否存在，仅上报
	dpState: 105, //感应状态
	dpMoveSensitivity: 106, //灵敏度
	dpPresenceSensitivity: 111, //灵敏度

	dpTimeout: 110, //感应延迟

	dpDistance: 109, //目标距离


	dpRange: 107, //最远距离范围
	dpIlluminanceLux: 104, //光照度




};
const fzLocal = {
	cluster: 'manuSpecificTuya',
	type: ['commandDataResponse', 'commandDataReport'],
	convert: (model, msg, publish, options, meta) => {
		const dp = msg.data.dpValues[0].dp;
		const data = msg.data;
		const value = legacy.getDataValue(data.dpValues[0]);
		const result = {};

		switch (dp) {
			case dpMap.dpPresenceState:
				result.presence = value ? true : false;
				break;
			case dpMap.dpMoveSensitivity: //Sensitivity
				result.motion_sensitivity = (value / 10);
				break;
			case dpMap.dpPresenceSensitivity: //Resting sensitivity
				result.presence_sensitivity = (value / 10);
				break;
			case dpMap.dpRange: //Radar range 15-55
				result.detection_distance_max = (value / 100);
				break;
			case dpMap.dpDistance: //Target distance
				result.target_distance = (value / 100);
				break;
			case dpMap.dpTimeout: //Delay 0-600
				result.presence_timeout = (value);
				break;
			case dpMap.dpIlluminanceLux: //Light illuminance
				result.illuminance_lux = (value);
				break;

			case dpMap.dpState:
				result.presence_state = {
					0: 'none',
					1: 'Present',
					2: 'Moving'
				} [value];
				break;

				// meta.logger.debug(
				// 	`未解析的数据DP: ${dp} DATA: ${JSON.stringify(msg.data)}`
				// );

		}
		return result;
	},
}
const tzLocal = {
	key: [
		'motion_sensitivity',
		'presence_sensitivity',
		'detection_distance_max',
		'presence_timeout',

	],
	convertSet: async (entity, key, value, meta) => {

		switch (key) {
			case 'motion_sensitivity':
				await legacy.sendDataPointValue(entity, dpMap.dpMoveSensitivity, value);
				break;
			case 'presence_sensitivity':
				await legacy.sendDataPointValue(entity, dpMap.dpPresenceSensitivity, value);
				break;
			case 'detection_distance_max':
				await legacy.sendDataPointValue(entity, dpMap.dpRange, value * 100);
				break;
			case 'presence_timeout':
				await legacy.sendDataPointValue(entity, dpMap.dpTimeout, value);
				break;

		}
		return {
			key: value
		};
	},

}


module.exports = [{
	fingerprint: [{
		modelID: 'TS0601',
		manufacturerName: '_TZE204_ijxvkhd0',
	}],
	model: 'ZY-M100-24G',
	vendor: 'TuYa',
	description: 'Micro Motion Sensor v1.2',
	fromZigbee: [fzLocal],
	toZigbee: [tzLocal],
	onEvent: legacy.onEventSetLocalTime,
	exposes: [

		exposes.enum('presence_state', ea.STATE, ['none', 'Present', 'Moving'])
		.withDescription('Presence state'),

		e.presence().withDescription('Presence detected'),


		exposes.numeric('target_distance', ea.STATE)
		.withDescription('Distance to target'),

		e.illuminance_lux(),
		exposes.numeric('motion_sensitivity', ea.STATE_SET).withValueMin(1)
		.withValueMax(10)
		.withValueStep(1)
		.withDescription('Motion sensitivity'),

		exposes.numeric('presence_sensitivity', ea.STATE_SET).withValueMin(1)
		.withValueMax(10)
		.withValueStep(1)
		.withDescription('Presence sensitivity'),

		exposes.numeric('detection_distance_max', ea.STATE_SET).withValueMin(1.5)
		.withValueMax(5.5)
		.withValueStep(1)
		.withUnit('m').withDescription('Detection distance'),


		exposes.numeric('presence_timeout', ea.STATE_SET).withValueMin(1)
		.withValueMax(600)
		.withValueStep(1)
		.withUnit('s').withDescription('Delay timeout'),



	],
	meta: {
		multiEndpoint: true,
		tuyaDatapoints: [



			[112, 'presence', tuya.valueConverter.trueFalse1],
			[106, 'motion_sensitivity', tuya.valueConverter.divideBy10],
			[111, 'presence_sensitivity', tuya.valueConverter.divideBy10],

			[107, 'detection_distance_max', tuya.valueConverter.divideBy100],
			[109, 'target_distance', tuya.valueConverter.divideBy100],
			[110, 'presence_timeout', tuya.valueConverter.raw],
			[104, 'illuminance_lux', tuya.valueConverter.raw],
			[105, 'presence_state', tuya.valueConverterBasic.lookup({
				'none': 0,
				'Present': 1,
				'Moving': 2
			})],

		],
	},
}, ];

Save file
Open file configuration.yaml in this zigbee2mqtt folder and at the end of file add:

external_converters:
  - ZY-M100-24G.js

Save
Restart HA
In Zigbee devices find this problematic device and choose Level from the new menu, dont touch moving bars
It works again!

Blackduke77 · 2024-01-25T21:24:14Z

which is the current converter that is working now? reading a few posts up; looks like different people are using different converters posted by different people

I think we have gone with @OwlBawl version

juan11perez · 2024-01-27T10:26:29Z

all I've created the pull request using @OwlBawl version

Koenkk/zigbee-herdsman-converters#6959

* Update tuya.ts modify per Koenkk/zigbee2mqtt#18237 * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts * Update tuya.ts

mDieli · 2024-01-29T16:04:29Z

Is this PR with the inverted sensitivity? (low number = more sensitive, high number = less sensitive)

juan11perez · 2024-01-29T18:45:33Z

It's not that is inverted. If you look at the sensor datasheet that is the default behaviour. I.e. high number is lower sensitivity and vicebersa.

mDieli · 2024-01-29T20:21:33Z

It's not that is inverted. If you look at the sensor datasheet that is the default behaviour. I.e. high number is lower sensitivity and vicebersa.

Datasheet aside, isn't it very contradictory when a high number means lower sensitivity?

I mean, i am just a user but when i have x number of devices and settings where a higher number means more, then this makes no sense to me?

sygad · 2024-02-07T23:26:07Z

Has this now been added to the Z2M main release?

I am new to Z2M (v1.35.3) and have the problem of the sliders not retaining their changes.

Do I need to create a converter?

djcrawleravp · 2024-02-08T15:04:20Z

Be sure to reset the device first. ( i did that a vew times to be sure) I noticed with the previous converters i tested that sometimes when i entered the room, sometimes the sensor would not detect me... or it would take up to 20 seconds... also sometimes i noticed some false positives... randomly... Runing a few days now with this one and everything stil runs smooth.. and a lot of less traffic ..

I have 3 different types of these sensors...

_TZE204_sxm7l9xa Floods the network * using a converter with filter.. _TZE204_ztc6ggyl Less Flooding no converter needed.. _TZE204_ijxvkhd0 Floods the network * using a converter with filter..

Excuse-me, what is the "converter" workaround? I'm my 6 M100 are _TZE204_sxm7l9xa :/

Thanks in advance!

sygad · 2024-02-10T20:44:58Z

For those looking as I was on how to get a customer converter working, I've written some basic instructions that also have a ZHA equivalent:

ZHA
Create a new folder in root folder, "custom_zha_quirks"
Inside new custom_zha_quirks folder, create new file for [custom-code.py]

In root folder
In the configuration.yaml
add the following entry

zha:
  custom_quirks_path: /config/custom_zha_quirks/

Z2M
In the "zigbee2mqtt" folder
Create a new file for [custom-code.js]
In the configuration.yaml (Z2M version)
add the following to the end of the file

external_converters:
  - [custom-code.js]

Open the zigbee2mqtt integration in HA
Settings > External converters
Add a new converter, filename input [custom-code.js]
Submit

Reboot HA
Reset and re-add zigbee device

kingunlim · 2024-02-11T01:59:36Z

still dont know if the best converter is now added to edge or stable?
does someone know which converter works the best and also dont spam the zigbee network?
and maybe someone knows how i can check that it spams/flodds the network?

thx!

dinde · 2024-02-11T02:09:31Z

still dont know if the best converter is now added to edge or stable? does someone know which converter works the best and also dont spam the zigbee network? and maybe someone knows how i can check that it spams/flodds the network?

I wish I knew as well. I've one 24G waiting in its box for a stable.
Regarding the chatty device here i checked with Z2M > Logs > Debug
It sends updates every 1s - 2s but it's with the 5G version if it helps.

kenni · 2024-02-11T08:37:48Z

still dont know if the best converter is now added to edge or stable? does someone know which converter works the best and also dont spam the zigbee network? and maybe someone knows how i can check that it spams/flodds the network?

thx!

You can use current stable version 1.35.3, no need for external converters anymore. If your device has been "bricked" by an incorrect external converter and has one or more of its settings locked, you will need to pair the device with a Tuya bridge or alternatively attempt to play around with the settings with one of the external converters, until it gets unlocked and the settings can be changed again.

In regards to the spamming of the Zigbee network, then you cannot do anything about it. It is not configurable and Tuya support has even confirmed that they can't fix it with a firmware update, as it is the vendor of their Zigbee chip that has implemented it.

aslomko · 2024-02-18T13:25:23Z

still dont know if the best converter is now added to edge or stable? does someone know which converter works the best and also dont spam the zigbee network? and maybe someone knows how i can check that it spams/flodds the network?
thx!

You can use current stable version 1.35.3, no need for external converters anymore. If your device has been "bricked" by an incorrect external converter and has one or more of its settings locked, you will need to pair the device with a Tuya bridge or alternatively attempt to play around with the settings with one of the external converters, until it gets unlocked and the settings can be changed again.

In regards to the spamming of the Zigbee network, then you cannot do anything about it. It is not configurable and Tuya support has even confirmed that they can't fix it with a firmware update, as it is the vendor of their Zigbee chip that has implemented it.

Can you please explain or link if there is an external converter to use that will allow the changing of the settings? It seems like the latest one is now officially in z2m but doesn't fix the settings reverting? I don't have a tuya bridge to make the second method work

kenni · 2024-02-20T11:17:22Z

still dont know if the best converter is now added to edge or stable? does someone know which converter works the b
Can you please explain or link if there is an external converter to use that will allow the changing of the settings? It seems like the latest one is now officially in z2m but doesn't fix the settings reverting? I don't have a tuya bridge to make the second method work

@aslomko, I believe I unbricked my own sensors using the Tuya bridge, but you might also be able to do it with one of the external converters in the wild by trial and error - It's a complete hit'n'miss, suddently it doesn't work, then afterwards it does work. I purchased the Tuya bridge specifically for unbricking the sensors, nothing else, but afterwards I actually ended up putting the Tuya bridge "into production", running a seperate Zigbee network in parallel to my primary Z2M network, just for getting the noisy Tuya sensors off my primary Z2M network. I only have three sensors currently, but it was enough to make my (otherwise rock-stable) ~100 devices Z2M Zigbee network unstable. Moving the three noisy devices to their own dedicated Tuya Zigbee network with LocalTuya made my Z2M Zigbee network rock-stable again.

I don't remember which external converter(s) that I potentially used for unbricking a device, I tried several of the early ones in this thread and some from another similar thread.

If relevant for anyone, I purchased the "Zigbee Gateway" from the following listing to unbrick the devices:
https://www.aliexpress.com/item/1005005538112925.html

mattchoo2 · 2024-02-20T11:53:26Z

If you don't have many things set up in Tuya Local, you can try Tuya Cloud for this device.
For this wifi model, i didnt manage to set 0.1s delay time (even via Tuya Local). Thus, automation responses will take from instantly to about 30s for lights to turn on for example.

kenni · 2024-02-20T12:18:17Z

If you don't have many things set up in Tuya Local, you can try Tuya Cloud for this device. For this wifi model, i didnt manage to set 0.1s delay time (even via Tuya Local). Thus, automation responses will take from instantly to about 30s for lights to turn on for example.

@mattchoo2 Assuming that this comment was meant for me, then I'm not having any issues with delays with the Zigbee version of the sensor + the Zigbee/wifi Tuya gateway I linked in my last post. However, I'm using the LocalTuya fork from
xZetsubou (https://github.com/xZetsubou), which has great support for subdevices (Tuya Zigbee devices behind a Tuya wifi gateway). Anyway, we're getting quite off-topic :)

kingunlim · 2024-02-24T21:12:32Z

If you don't have many things set up in Tuya Local, you can try Tuya Cloud for this device. For this wifi model, i didnt manage to set 0.1s delay time (even via Tuya Local). Thus, automation responses will take from instantly to about 30s for lights to turn on for example.

@mattchoo2 Assuming that this comment was meant for me, then I'm not having any issues with delays with the Zigbee version of the sensor + the Zigbee/wifi Tuya gateway I linked in my last post. However, I'm using the LocalTuya fork from

xZetsubou (https://github.com/xZetsubou), which has great support for subdevices (Tuya Zigbee devices behind a Tuya wifi gateway). Anyway, we're getting quite off-topic :)

can you tell me how to configure the presence sensor the right way with this local tuya fork?
i did configure everything but the sensor looks like this in home assistant :(

kenni · 2024-02-24T22:12:44Z

If you don't have many things set up in Tuya Local, you can try Tuya Cloud for this device. For this wifi model, i didnt manage to set 0.1s delay time (even via Tuya Local). Thus, automation responses will take from instantly to about 30s for lights to turn on for example.

@mattchoo2 Assuming that this comment was meant for me, then I'm not having any issues with delays with the Zigbee version of the sensor + the Zigbee/wifi Tuya gateway I linked in my last post. However, I'm using the LocalTuya fork from
xZetsubou (https://github.com/xZetsubou), which has great support for subdevices (Tuya Zigbee devices behind a Tuya wifi gateway). Anyway, we're getting quite off-topic :)

can you tell me how to configure the presence sensor the right way with this local tuya fork? i did configure everything but the sensor looks like this in home assistant :

Yes, see my comment here:
home-assistant/core#104626 (comment)

kingunlim · 2024-02-24T22:32:38Z

thank you very much!
i will try this tomorrow.

kingunlim · 2024-02-25T04:40:19Z

what i dont get, what is the actual problem of the device, what does the spamming means?
this is my z2mqtt log looks like after a reset with the tuya gateway and newest z2mqtt edge version without any external converter!

and maybe someone know how to calibrate the lux the right way?

juan11perez · 2024-02-25T04:57:03Z

In my opinion it's just a bad device.
I bought 3 and they're just unreliable.
I have 5 of the 5G version they're just better.
The extra 'sensitivity' of the 24G does not compensate its unreliability.

kingunlim · 2024-02-25T06:46:34Z

yeah i already knew that but thanks, i dont know if i buy them again also not the 5g version.

but maybe someone has some insights on my questions

Dillton · 2024-02-25T17:01:29Z

yeah i already knew that but thanks, i dont know if i buy them again also not the 5g version.

but maybe someone has some insights on my questions

Hello, I think this is the right time to share my experince with these sensors.

EXPERIENCE:
I have 4 ceiling and 2 wall mount 24G sensors and for me they are working as expected for 2 months now.
My only problem is that the 2 wall mount sensors I am using in relatively small rooms where sensitivity settings can't be further improved for better performance so more conditions then has to be made in automations.
Also some negative if you are changing the sensitivity settings rapidly sensor might freeze in always detected state no idea why. Only cut of the power helps - this happened for me 2-3 times in the early phase of setting up.
Other than that no complains about 24G versions.
Sensors are actually fast enough so I don't need to use them in combination with additional PIR sensor.

ILLUMINANCE:
There seems to be more HW variants depending on manufacturer at least for ceiling version.
I have bought 2 celings from Arteco store on aliexpress and they came in packaging from Loginovo manufacturer.
Then I ordered after a month additional 2 ceilings from Wenzhi official store which seems to be the main manufacturer of these devices as far as I know.

The 2 two from Wenzhi store had on top of the cover a small ball of some plexi glass which sits directly above the lux sensor and results in reflecting more light to the sensor itself. Lux values are fine out of the box on these two.

On the other hand the 2 from Arteco store (Loginovo manufacturer) came without this plexi only with a very little drilled hole (1mm) and the lux readings were terrible. I wasn't able to get above 15lx. So I have took the cover and drilled bigger hole for lux sensor (I think I used 4mm drill bit). Since then the lux readings on these 2 sensors are also fine.
The same I had to do with the other 2 wall mounts.
Readings for reference from Loginovo manufacturer sensors in my living room oriented to south and looking directly to windows thats why there is 1500lx over noon. It perfectly correspond with sun shine outside:

For comparison both sensors:
Wenzhi

Logivnovo

SPAMMING:
Currently I have 43 devices in zigbee network and yeah the spamming well thats just the firmware of these devices as mentioned many times before in this thread however I personally did not encounter any issues like zigbee or mqtt freezing or some weird readings etc...
But if you want to lighten at least mqtt side there was a functional external converter which filtered Target Distance out of mqtt broadcast if I remember correctly somewhere in previous comment.

SUMMARY:
I would not say the device is bad it just requires more time and effort to set up correctly.
From my experience I do recommend these sensors but only for bigger rooms.
They are not perfect for rooms like 2x2m bathroom or 3x1m corridor otherwise there will be additional effort requierd in declaring more conditions within automations and maybe using additional PIR sensor to confirm the presence state in certain situations.

Hope this helps a bit and answer some questions.
Have a nice rest of the weekend.

Cyberbeni · 2024-02-26T00:34:49Z

Did anyone try to set radar range to an integer value?

Zuz666 · 2024-02-26T09:24:53Z

Hope this helps a bit and answer some questions. Have a nice rest of the weekend.

Thanks for the shared experience!
What frame (model) did you use to mount the sensors? Is this wall mount?

Dillton · 2024-02-27T10:52:55Z

Hope this helps a bit and answer some questions. Have a nice rest of the weekend.

Thanks for the shared experience! What frame (model) did you use to mount the sensors? Is this wall mount?

On the pictures those are ceiling version sensors and I have used spare Legrand plug/light switch frames which remained after reconstruction of my apartment.
Luckily these sensors prfectly fits inside the frames with no further adjustment needed 😄

One more thing regarding the mount place. I was thinking at first that I will really mount sensonrs to ceilings in every room but this would be a bit more diffucult to get power there so instead I actually tried to use them as wall mounts next to my light switches by the doors to rooms where I took the power easily and they perfectly covers whole rooms.
Basically this is final result and I am happy:

glecoz · 2024-03-29T15:11:05Z

Just for information, I've been in touch with the manufacturer through Aliexpress, and he sent me this repository, didn't test the scripts yet, waiting the devices shipping, I will update here once tested.

UPDATE :
All my 3 sensors ZY-M100-24GV2 (Wenzhi) are perfectly bound with Z2M for all settings, but they keep flooding the broker by sending their payload every second.
A firmware upgrade seems to be in progress.

DosPH added the new device support New device support request label Jul 7, 2023

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Aug 5, 2023

feat(add): ZY-M100-24G Koenkk/zigbee2mqtt#18237

d61c2f3

Koenkk mentioned this issue Aug 5, 2023

chore(master): release 15.54.0 Koenkk/zigbee-herdsman-converters#6050

Merged

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Aug 5, 2023

feat(add): ZY-M100-24G @VladKorr Koenkk/zigbee2mqtt#18237

39f13a9

Koenkk closed this as completed Aug 5, 2023

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Aug 6, 2023

fix(ignore): Fix missing ZY-M100-24G keys. Koenkk/zigbee2mqtt#18237

d0e8519

Koenkk mentioned this issue Aug 6, 2023

chore(master): release 15.54.1 Koenkk/zigbee-herdsman-converters#6051

Merged

juan11perez mentioned this issue Jan 26, 2024

Update tuya.ts to correct presence sensor ZY-M100-24G Koenkk/zigbee-herdsman-converters#6959

Merged

[New device support]: for Tuya M100S with 24G radar #18237

[New device support]: for Tuya M100S with 24G radar #18237

Comments

DosPH commented Jul 7, 2023

Link

Database entry

Comments

External converter

Supported color modes

Color temperature range

vitaleg commented Jul 12, 2023

DosPH commented Jul 13, 2023

mrstormbyte commented Jul 18, 2023

TheDIYEd commented Jul 19, 2023

rpearl commented Jul 23, 2023

gevorgmansuryan commented Jul 24, 2023

rpearl commented Jul 24, 2023

VladKorr commented Jul 27, 2023

VladKorr commented Jul 27, 2023

vincentBesseau commented Jul 28, 2023

rpearl commented Jul 28, 2023

Carabin79 commented Aug 3, 2023

Igor-Andrusevic commented Aug 4, 2023

VladKorr commented Aug 4, 2023

Igor-Andrusevic commented Aug 4, 2023 • edited

Carabin79 commented Aug 4, 2023

Koenkk commented Aug 5, 2023 • edited

BeFygo commented Aug 5, 2023

Koenkk commented Aug 6, 2023

leroyloren commented Aug 6, 2023

MTokarev commented Aug 6, 2023

BeFygo commented Aug 7, 2023

BeFygo commented Aug 7, 2023

sozoalvin commented Jan 23, 2024

imatrixcz commented Jan 24, 2024

Blackduke77 commented Jan 25, 2024

juan11perez commented Jan 27, 2024

mDieli commented Jan 29, 2024

juan11perez commented Jan 29, 2024

mDieli commented Jan 29, 2024

sygad commented Feb 7, 2024

djcrawleravp commented Feb 8, 2024

sygad commented Feb 10, 2024 • edited

kingunlim commented Feb 11, 2024

dinde commented Feb 11, 2024

kenni commented Feb 11, 2024

aslomko commented Feb 18, 2024

kenni commented Feb 20, 2024

mattchoo2 commented Feb 20, 2024

kenni commented Feb 20, 2024

kingunlim commented Feb 24, 2024

kenni commented Feb 24, 2024

kingunlim commented Feb 24, 2024

kingunlim commented Feb 25, 2024 • edited

juan11perez commented Feb 25, 2024

kingunlim commented Feb 25, 2024

Dillton commented Feb 25, 2024 • edited

Cyberbeni commented Feb 26, 2024

Zuz666 commented Feb 26, 2024 • edited

Dillton commented Feb 27, 2024 • edited

glecoz commented Mar 29, 2024 • edited

Igor-Andrusevic commented Aug 4, 2023 •

edited

Koenkk commented Aug 5, 2023 •

edited

sygad commented Feb 10, 2024 •

edited

kingunlim commented Feb 25, 2024 •

edited

Dillton commented Feb 25, 2024 •

edited

Zuz666 commented Feb 26, 2024 •

edited

Dillton commented Feb 27, 2024 •

edited

glecoz commented Mar 29, 2024 •

edited