[New device support]: Zigbee Chlorine Meter PH ORP EC TDS Salinity Temp CL- _TZE200_v1jqz5cy #18704
Comments
|
im giving it a crack Gor my first error |
|
@Koenkk where is a list of the supported datapoints? |
|
Here is a list of all standard exposes, but you can easily create new ones: example |
|
Is the device already available in z2m or hast anybody a solution? |
|
no its not, i dont know what im doing lol |
thanks but I don't really know what im looking for |
|
I just got the very same device here, connected to my Home Assistant server, through ZHA. @cloudbr34k84 Brad, how did you get the Data Points? |
|
i follow the the instructions on Z2M
https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html
…On Thu, 7 Sept 2023 at 05:44, Thomas Schiex ***@***.***> wrote:
I just got the very same device here, connected to my Home Assistant
server, through ZHA.
I would be happy to help here. I can write code, but am a
ZigBee/Z2MQTT/ZHA newbie...
@cloudbr34k84 <https://github.com/cloudbr34k84> Brad, how did you get the
Data Points?
—
Reply to this email directly, view it on GitHub
<#18704 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOB2WBER4VB3X5EG7OOUEOLXZDHDLANCNFSM6AAAAAA33LB5ZE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Koenkk any chance you can help create the converter pls? |
|
Yes, that would bei great! |
|
That would be great for me too!!! |
|
With the following ext converter, what shows up in the z2m frontend -> device -> state page? https://gist.github.com/Koenkk/7262a8a36bb84327ff563e0b8256024b |
|
Sorry Koenkk, I don't have Z2M installed on HA, but ZHA. Is it easy to switch back and forth? BTW, I bought a Tuya Gateway and followed the instructions on Z2M and found more DP Ids: 1: TDS (Translation of Chinese by Google Translate camera from Tuya IoT platform website). There are apparently 2 pH calibration DP Ids (and there are 2 pH calibration standards: Asia uses 6.86/4.00/9.18, EU uses 7/4/10). The two pH calibration DPs could be these 2 maybe? I was told the device apparently works on deconz: https://forum.phoscon.de/t/tuya-tze200-v1jqz5cy-zigbee-chlorine-meter/3930 (see zigpy/zha-device-handlers#2565). |
|
|
Brad, I'm not a Z2M specialist, but the fact that Z2M says:
may be a hint that Koenkk's handler above is not accessible to Zigbee2MQTT in your setup. |
|
Or may be the handler is wrong.... Looking into it, I see: I assume the modelId is important for recognizing the device? Because it reports 'TS0601' not 'BLE-YL01'. Brad, I suppose you should edit Koenkk's script and replace the by |
It's a wok in progress ... ;-) |
|
Made a mistake, updated https://gist.github.com/Koenkk/7262a8a36bb84327ff563e0b8256024b |
Hey @Koenkk Thanks, its now added correctly, but it has not exposed any entities |
I'm not an expert but if you look at the other tuya converters that are using datapoints in zigbee-herdsman-convert/src/devices/tuya.ts, you also need to add the corresponding entries in the expose section, i.e.: exposes: [e.tds, e.temperature, etc... example: So maybe try this? : |
|
Please make a screenshot of the z2m frontend -> device page -> state page? |
|
|
With the following converter: https://gist.github.com/Koenkk/7262a8a36bb84327ff563e0b8256024b , can you provide the debug log when pairing the device + 5 minutes after this? See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
Hey @Koenkk thanks for helping on this |
|
I forgot to mention that this converter only works with the latest-dev branch. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
|
tried this, same issue as when I attempted. i don't understand how to create a new function
|
|
@Koenkk |
Can you explain how to send this command? Thank you |
|
I have not been able to use this device with Z2M. |
|
@Mushupm |
|
No one have a solution for negative orp ? |
I'm looking at that device, and wonder why you are refering to command 0x03 to do the Tuya Data Query while when looking a sniff, the Tuya GW does a Command 0x00 on DP 0x69 Type 0x02 with a Payload of 0x00000001 thanks for your view |
|
@Koenkk I can add the device, trigger a call to cluster 0xEF00, attribute 0x03, get values, but there's no way it will poll. Once it's added, call triggered, that's it.. |
Hi @hsdneo, How did you manage to send the command, I tried a few things in the Dev console, but no luck, I can't just add the cluster id, command and attribute, as there is no attribute textbox in the dev console (not one you can freely input text for anyway)
This is for a BLE-YL01 BTW, it mis missing pretty much everything Thanks! { |
Seen here: https://youtu.be/8zGAHyCan0c?t=326: It does not work for me, I get "Error: no datapoint defined for 'command'" like you. |
|
Same problem with the second Device I received from Domadoo. "z2m: Publish 'set' 'command' to '0x94b216fffe900a1c' failed: 'Error: No datapoint defined for 'command" even with Z2M edge version. The first device i received accepted successfully this modification and was sending values after. How can i make it work, I don't have Zigbee bridge yet? Thanks in advance, ### EDIT : I finally get it work back. For all who had the _"Error: No datapoint defined for 'command'" issue when tring to send the "Console Dev" 0xEF00 0x03 command I had to come back to Zigbee2MQTT 1.39.0 version. (it was impossible with the 1.40.x version). Whith version 1.39.0 instead if 1.40.0 I could get back the result "Invoked '61184.3' with payload '{}' and then values like : |
|
how can I revert to an older version of Z2M? My BLE-YL01 also no longer transmits data. Z2M Version 1.40.2 |
|
Same issue here with a Tuya TS0601/BLE-YL01. It stopped getting data from sensors, Z2M 1.40.2. |
Great find snyfear! |
|
I tried to upgrade again After the downgrade but thé data stop to update so i kept the 1.39 |
|
I can confirm: I've been using my pool monitoring without issues (expect for the weird values mentionned above) for months and suddenly a few weeks ago all values stopped updating except for linkQuality signal strength. Thanks to the above comments, I've restore Z2M 1.39.1 version (was 1.40.2) and values are back! To downgrade Z2M, I went to HA settings -> system -> backups, and found a zigbee2mqtt module backup in 1.39.1 version, then select it and click on "restore" option. |
|
Is there a solution available for those without a backup on version 1.39.1? Any way of installing an older version of it from scratch? |
Should looks like this: "devices": []Example (Don't modify the rest of the values, I changed for XXXX to not expose my config)
|
How can I revert the image to 1.39.1 without a backup with that version? |
You don't need a backup of z2m, you can use the image hosted on DockerHub -> https://hub.docker.com/layers/koenkk/zigbee2mqtt/1.39.1/images/sha256-a342efc7d6f04c29b8310ab2890a7a2697c955b5066d892dfe00aef65c1b4107?context=explore If you use Docker / DockerComposer / Kubernetes you only need is modify the tag of the |
Oh i see, i use Home assistant native OS. Sadly i don’t think is that easy within this environment or at least not in a way i know 😅 thank you though |
Sorry, I use Kubernetes on my env. But I just saw the code of the HAOS, and they basically use docker to handle the addons, Please before to anything backup all of your folder just in case. https://github.com/catrielmuller/hassio-zigbee2mqtt-1-39-1 I cannot tested properly because I don't have any VM software to test HAOS quick on my pc (So I use a devcontainer and looks like works). Here is an small tutorial -> https://www.youtube.com/watch?v=nV3wWkEyt8w |
|
Thank you very much @catrielmuller Just downgraded Z2M to 1.39.1 on latest aarch64 Hassio thanks to your repo and now:
|
|
PROBLEM RESOLVED! Now all that's needed is the ability to calibrate it, which is apparently rather important for the sensors this device uses. The guys working on getting this device working with ZHA have already made some progress. @tschiex has identified the Data Point ID's used for calibration: zigpy/zha-device-handlers#2565 (comment) Unfortunately I'm personally too inexperienced to make use of that information and get it working with Z2M (for now!), but perhaps someone else will find it useful. |
|
Hi! I'm having more or less the same issue. Just received this device with z2m 2.0.0-2, and I'm having issues after the initial association. I initially seemed to work but after a couple of minutes, I started to get this message (twice) every 3-4 minutes: So I tried to enter the and I don't have any backup of I then tried to See full log in here:tuya.txt Any ideas? Thanks! |
|
After reading other comments, apparently sending commands with 1.39 and upgrading back to 1.4x doesn't seem to work (no values sent). I found an old 1.37 backup but I would definitely like to make it work (by sending the famous command and upgrade) or out of the box on 2.x. @Koenkk any ideas? I'm able to provide any relevant information needed. Thanks! |
|
Did upgrading past 1.41.0 help other folks? |
|
For the information of Home Assistant users, note that the device is now supported natively by ZHA.
The PR is ongoing: the « ZHA quirk v2 » with integrated refresh is available here: zigpy/zha-device-handlers#3673
|
|
Good news on my side. |
and others
Link
https://www.aliexpress.com/item/1005005575336871.html?spm=a2g0o.order_list.order_list_main.11.28e31802Wxn6Wl
Database entry
{"id":115,"type":"EndDevice","ieeeAddr":"0xe0798dfffeb87446","nwkAddr":42479,"manufId":4098,"manufName":"_TZE200_v1jqz5cy","powerSource":"Battery","modelId":"TS0601","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":81,"inClusterList":[0,4,5,61184],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"65503":"\u00195y,f\u00195y,\u0012\u001a5y,\u0012\u001e5y,\u0011"5y,\u0011","65506":31,"65508":0,"appVersion":65,"modelId":"TS0601","manufacturerName":"_TZE200_v1jqz5cy","stackVersion":0,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":65,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1692789799130,"defaultSendRequestWhen":"immediate"}
Comments
Would someone be willing to make a converter> here are the Data Points
1: TDS
2: temperature
101: ORP
102: CL
7: Battery Percentage
105: backlight Value
10: ph Value
11: EC Value
108: EC Max Value
109: EC Min Value
110: ORP max
111: ORP min
112: CL Max Value
113: CL Min Value
114: PH??
115: EC??
116: ORP??
117: Salt
External converter
No response
Supported color modes
No response
Color temperature range
No response
The text was updated successfully, but these errors were encountered: