[New device support]: for Tuya M100S with 24G radar #18237
Comments
|
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. So, +1, add support, please. |
|
yes this new one. Tried ZHA and latest converter also not working. |
|
Also waiting for support |
|
I am trying to get the same for TZE204_qasjif9e. Nothing works so far. |
|
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 |
|
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 |
|
I have _TZE204_ijxvkhd0 and tried to get datapoints by means of tuya gateway. |
|
_TZE204_ijxvkhd0 is 24GHz and and it's different from a similar 5 GHz sensor. |
|
Hello @rpearl , how can I add your file for the "_TZE204_qasjif9e" device on my zigbee2mqtt ? |
|
Hello, please help me add this new device _TZE204_ijxvkhd0 in Z2q , it's a new device that works in 24g. |
|
Hello!! Add this new device _TZE204_ijxvkhd0 in zigbee2mqtt |
Hello, try to add external converters to your z2m from link: |
|
Благодарю. Буду проверять, на данный момент работает.
|
|
Thank you it works |
|
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, 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". |
|
@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) |
|
Please, does this device flood the network like the previous model (ZY-M100-S_1)? |
I am a new user here and missing almost everything ;) 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; |
Confirmed, great work! |
|
@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 |
|
all I've created the pull request using @OwlBawl version |
* 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
|
Is this PR with the inverted sensitivity? (low number = more sensitive, high number = less sensitive) |
|
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? |
|
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? |
Excuse-me, what is the "converter" workaround? I'm my 6 M100 are _TZE204_sxm7l9xa :/ Thanks in advance! |
|
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 In root folder Z2M Open the zigbee2mqtt integration in HA Reboot HA |
|
still dont know if the best converter is now added to edge or stable? thx! |
I wish I knew as well. I've one 24G waiting in its box for a stable. |
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 |
@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: |
|
If you don't have many things set up in Tuya Local, you can try Tuya Cloud for this device. |
@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 |
can you tell me how to configure the presence sensor the right way with this local tuya fork? |
Yes, see my comment here: |
|
thank you very much! |
|
what i dont get, what is the actual problem of the device, what does the spamming means? and maybe someone know how to calibrate the lux the right way? |
|
In my opinion it's just a bad device. |
|
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: ILLUMINANCE: 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. For comparison both sensors: Logivnovo SPAMMING: SUMMARY: Hope this helps a bit and answer some questions. |
|
Did anyone try to set radar range to an integer value? |
Thanks for the shared experience! |
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. 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. |
|
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 : |
|
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days |
and others
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
The text was updated successfully, but these errors were encountered: