Hello everyone, I am the manufacturer of GIEX SMART. Our company produces smart kits for garden irrigation and agricultural irrigation. I hope to listen to your feedback on our products here and provide after-sales service and assistance. Your support is greatly helpful for the improvement of our products. Our email is [email protected]. Feel free to contact me with any questions regarding product quality or usage. Thank you very much.
I am learning to use ZHA so that I can provide services for ZHA users in the future. I followed the tutorial from some experts on the website to add the GX-02 to ZHA. However, I noticed that in newly produced products, Tuya seems to have updated the chip model to _TZE284_7ytb3h8u instead of _TZE204_7ytb3h8u as mentioned in the tutorial. I tried replacing the code in the file from ‘_TZE204_7ytb3h8u’ to ‘_TZE284_7ytb3h8u’, but it still doesn’t work. Could any ZHA experts guide me on this?
ZHA matches on clusters also, make sure that there isn’t an additional input cluster, you can confirm in ZHA by looking at the device signature. Also, if you are the manufacturer anything Tuya is a giant pain to support, if your device follows Zigbee standards instead, it will just work and make all of our lives easier. I get that Tuya makes it easier as a manufacturer, just always want to advocate for standards compliance when I can.
Thank you so much for your advice. I’ll definitely take your suggestion into consideration. I’m currently exploring other Zigbee solutions on the market. In the meantime, I’d love to learn how to properly match my Tuya devices with ZHA. This way, I can better guide my users on how to use them with ZHA.
Thanks again for your help!
Best regards,
Raul
GIEX
1 Like
If you still have issues getting the valve quirk right post the signature and we can look at it further. I also saw someone was asking about your soil moisture sensor, might be good to get that one working as well.
Thank you so much for your help! However, I’m not yet sure how to post my device signature. I’m still new to this and recently set up a NAS to run Home Assistant, so I’m in the process of figuring things out. I’ll learn how to post the signature and let you know once I have it.
You seem to be quite experienced with ZHA. I have a new product coming soon—a 2-zone Tuya Zigbee water valve. Could you help me add it to ZHA’s quirk list? I’m worried that some regular users might have trouble using it with ZHA after purchasing. If you’re interested, I can send you the product for testing and feedback. It’s clear that learning ZHA is not an easy task for me, and I think I’ll need more time before I can properly guide my users on how to use our devices with ZHA.
Thanks again for your assistance!
To get the signature, go to settings, zha, find the device, click the three dot menu, and then choose manage device.
I downloaded the quirks from this website.
Are these data sufficient for you to proceed with the testing?
OK, that’s what I expected, I saw the cluster 0xed00 show up on a Tuya soil sensor I added support for a few weeks ago. Try the quirk below and see if it works for you.
class GiexValveVar02(CustomDevice):
"""GiEX valve device, variant 2."""
signature = {
MODELS_INFO: [
("_TZE284_7ytb3h8u", "TS0601"),
],
ENDPOINTS: {
# <SimpleDescriptor endpoint=1 profile=260 device_type=0x0051
# input_clusters=[0x0000, 0x0004, 0x0005, 0xed00, 0xef00]
# output_clusters=[0x000a, 0x0019]>
1: {
PROFILE_ID: zha.PROFILE_ID,
DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
0xed00,
GiexValveManufCluster.cluster_id,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
},
}
replacement = {
ENDPOINTS: {
1: {
DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
INPUT_CLUSTERS: [
Basic.cluster_id,
Groups.cluster_id,
Scenes.cluster_id,
TuyaOnOffNM,
TuyaPowerConfigurationCluster,
TuyaValveWaterConsumed,
GiexValveManufCluster,
],
OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
}
}
}
You’re amazing! It actually worked in ZHA. May I ask you a few more questions? The first question: Why is it that the GXM-01 soil moisture sensor can pair with ZHA and display both humidity and temperature directly without needing a quirks file, while the GX-02 water valve requires a quirks file to work properly? The second question: I noticed that the GX-02 has fewer functions in ZHA compared to 2MQTT. In ZHA, it only has the function to turn the water on and off, while in 2MQTT, almost all functions are available. Can I write these functions into the quirks file (e.g., how many gallons watered, watering time in seconds, watering cycles, etc.) so that ZHA can also have these features?
Two possibilities, either there is already a quirk for the GXM-01 added, or it uses standard ZCL clusters and is supported by default. If you have the device signature, I could answer that.
The original quirk developer added the logic for those data points already, zha-device-handlers/zhaquirks/tuya/ts0601_valve.py at d9c9df9768731e8ad7a3d167cfd8c8e565547c50 · zigpy/zha-device-handlers · GitHub. I would expect that you would see a metering sensor, in liters, that is built, zha-device-handlers/zhaquirks/tuya/ts0601_valve.py at d9c9df9768731e8ad7a3d167cfd8c8e565547c50 · zigpy/zha-device-handlers · GitHub. The rest would need to be mapped to an appropriate cluster similar to the volume sensor.
Based on your feedback, I created a PR for that device, Add GIEX Smart Valve Var02 (_TZE284_7ytb3h8u) by prairiesnpr · Pull Request #3378 · zigpy/zha-device-handlers (github.com)