TS0601 _TZE204_sxm7l9xa defined but shows as not supported #17483
Comments
|
Could you check if the issue is fixed with the following external converter: https://gist.github.com/Koenkk/9295fc8afcc65f36027f9ab4d319ce64
external_converters:
- ext_converter.js
|
|
Thanks for the quick answer: I have now the lux working but get these errors: Here all the Infos in the log when adding the device |
|
To figure out what these datpoints mean (e.g. 109) you need a TuYa bridge: https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html |
|
ok thank you. Very sad. Then I have to think about investing 20more euros into that :-) |
|
I join The same problem! |
Just ordered the tuya box in china. Perhabs we find a solution as soon as we find the datapoints |
|
Огромное спасибо !!! Буду ждать с нетерпением ! |
|
same problem for me too |
|
same problem here, i have no tuya bridge |
|
I've got a bridge and today I've got four of those sensors. I'm going to try to check it out. |
Sound good, you also have the ones with the id: _TZE204_sxm7l9xa ? |
|
This is what I've found: |
I found this doku: https://www.zigbee2mqtt.io/advanced/support-new-devices/02_support_new_tuya_devices.html#_3-understanding-tuya-datapoints But not sure what to add to the external converter(https://gist.github.com/Koenkk/9295fc8afcc65f36027f9ab4d319ce64) |
|
I'll think there need to be a meta block something like this, I'm going to test it locally :-) : meta: {
tuyaDatapoints: [
[104, 'illuminance', tuya.valueConverter.raw],
[105, 'presence', tuya.valueConverter.boolean],
[106, 'radar_sensitivity', tuya.valueConverter.raw],
[107, 'maximum_range', tuya.valueConverter.raw],
[108, 'minimum_range', tuya.valueConverter.raw],
[109, 'target_distance', tuya.valueConverter.raw],
[110, 'detection_delay', tuya.valueConverter.raw],
[111, 'fading_time', tuya.valueConverter.raw],
],
},I'm not really familiar with the systems yet. |
hey thank you, I thought the same. But at the moment I still get the same errors as before. |
|
I've got it some kind of working with https://gist.github.com/RamonSmit/157f08633b8a05feb8e845d34872999f, need to finetune it obviously a bit more :-). It's a nice way of learning hehe. |
I found some examples where it was not |
|
Feel free to collaborate, I'm new in here 😄 |
Yeah, I already trying: this is how it looks like with: Has to be cm instead of m I think :-) |
|
Hahaha, good catch! My house is not that big indeed hehe. I also think that in the TuYa development portal its reported as 0.60M, so there has to be a conversion somewhere. |
Do i have to remove and readd the device after changing the converter? funny think I ordered 4 devices 2 came with : @Koenkk the _TZE204_ztc6ggyl is working without an external converter I removed it from the file and worked just as a short remark @RamonSmit you are right the one without the need of an external converter show 0,6m |
|
> Do i have to remove and readd the device after changing the converter? As far as I know, not. I've only needed to restart the system a couple of times |
|
I've managed to get mine working with the following: |
|
illuminance_lux and presence seems to be working however any attempts at setting the state for radar_sensitivity, maximum_range, minimum_range, detection_delay or fading_time gives an error log entry like the one below:
|
Thanks for the input. I have the same problem changing values |
|
It has something to do with the toZigbee converters I think. Issue 15729 looks like our issue for this device |
|
Here working ext_converter.js: |
|
It's work. Many thx. Your great. |
|
Same here. Getting the errors for human presence sensors: Zigbee2MQTT:debug 2023-07-03 23:39:41: Received Zigbee message from 'Living room presence sensor', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,0,0,0],"type":"Buffer"},"datatype":2,"dp":109}],"seq":6656}' from endpoint 1 with groupID 0 Any way to fix this ? Thank you. |
|
The functions are now available in |
|
Thank you for your quick response and the fix in the code. As I see, we should wait until you update the zigbee-herdsman-converters version in the zigbee2mqtt package.json on the dev branch, right? Edit: Now zigbee2mqtt dev branch updated and the external converter works again after changing tuya.getDataValue to legacy.getDataValue with the mentioned import. 👍 |
Thank you, @Koenkk, it's work. |
|
I've just got my TS0601 Human Presence Sensor, and tried to pair it.. Looks like it's a different ID to the above: warn 2023-09-25 12:21:22: Received message from unsupported device with Zigbee model 'TS0601' and manufacturer name '_TZE204_e5m9c5hl' Is this a variation of the one above? Do I need to raise a new request for specific support of this variation? It appears to be a 5.8GHZ mmWave / Zigbee / Wall mount version |
Exact same problem here ! Received mine today, the 24G version (not the 5.8G), I didn't realise that it wasn't the same one... Edit: I added the external converter of this link and replaced |
Can you be more specific on the external converted used please? |
Sorry, it was a bad link. I updated my comment with the good link. |
|
Same issue - just added a _TZE204_ijxvkhd0, was not recognised. Replaced _TZE204_sxm7l9xa with _TZE204_e5m9c5hl in here, but not entities working. 5.8GHZ mmWave / Zigbee / Wall mount version |
|
I think I bought the same: Zigbee Model I bought this one: 5,8g ceiling mount. It has a 16A relay as well, any clue how to get this working? |
|
Hi community, |
|
I managed to get it working via this converter: |
|
Hi @marciej123 thanks so much for sharing. I tried but with no joy. To be sure I did it right. I created a new script file within the zigbee2mqtt section, close to the configuration.yaml file, called TZE204_mtoaryre.js and pasted your code inside. couple of months ago, had the same issue with the 24G sensor, did this same thing and it worked. this one, unfortunately, doesn't. am I doing something wrong? |
|
This one works for me: Did you update here and restart?
|
|
Hi @chinswain that was the trick, I had not updated and restarted. done it now and it works nicely. Thanks to both @chinswain and @marciej123 |
i have the same device as you, it works for me this BUTT when i try to make a automation, the presence entity does not show up for me, is this the same case for you? (the presence enitity exists and updates but cant find it when making automations)
|
Do you have a TZE204_ijxvkhd0 like me? I tried your converter but basically it doesn't work, I had to replace the _TZE204_e5m9c5hl model code in it with _TZE204_ijxvkhd0. It works but it's not great, the brightness in lux works, but the presence changes once in a while and most of the parameters don't work... |
|
I get the following error when using the above external converter, any ideas what could cause this?
|
This works for me, is there a PR open to add support for this device? If not would you mind if I use this as a base to add native support? |
I have the same problem. With the config right above my reply, the presence state isn't usable in any motion-related automation. |
The same thing. It is impossible to create automation of turning on the light when motion is detected. When creating automation, there is no motion detection object. |
|
The presence sensor is incorrect in that config, it exposes the entity as a text based enum rather than an actual presence binary sensor.. I updated my converter so it is as follows which is working perfect for me:
|
|
Yes! This one works. Thanks very much! |
After replacing the external converter specified by pantherale0, everything worked. |
|
Had the exact same problem with the TS0601, manufacturer _TZE204_e5m9c5hl, with the code from @Almaz7791 I was able to add it. At this time I would hope this was already included officially, do we need to open a ticket for this? |
|
Hi @OakfieldDrive , Please can you put your code for "_TZE204_mtoaryre" here. Thanks |
Hi, did you finally get this to work? Got a few of this last week and struggling to get them to work. |
and others
What happened?
I have the tuya human presence sensor but with another manufacturer id.
_TZE204_sxm7l9xa is the one I have
Zigbee2MQTT Version [1.30.3]
Same as in Koenkk/zigbee-herdsman-converters#4940
What did you expect to happen?
The device with the new manufacturer ID workes loke the others.
How to reproduce it (minimal and precise)
Add the device
Zigbee2MQTT version
1.30.3
Adapter firmware version
6.10.3.0 build 297
Adapter
home assistant yellow
Debug log
No response
The text was updated successfully, but these errors were encountered: