Hi!
I recently got this tuya water valve from Ali, but it does not seem to be supported correctly by Homeassistant/ZHA. It does pair without problems, but the device does not bring any entity up.
Some quick searching brought me to this zigbee2mqtt release, which says the device is supported, and to this docs page from tuya, which seems to document some zigbee ID shenanigans that elude me.
From that docs, it would seem like the device supports fancy things, like setting up irrigation cycles, reading sensors, and so on. I think that is nice but personally I would be super happy if, as a starting point, I could get it show as a simple on/off switch in homeassistant, and leverage automations for the rest.
Is there any place where I can request this? Or, perhaps, documentation around zha to see if it would be possible to do it myself?
You can post new device support request(s) to ZHA Device Handlers under issues in GitHub repository:
Zigbee devices that do not only use standard configuration and parameters (default ZCL clusters and attributes) but instead also implement custom manufacturer clusters and attributes (also known as “quirks”) will need a custom handler/converter/parser/translator as Python script code in the upstream “ZHA Device Handlers” library repository to extend custom manufacturer device “quirk” support for specific non-standard ZCL clusters and attributes (which Zigbee gateway implementations that depends on zigpy and the ZHA Device Handlers library, like Home Assistant s ZHA integration, then can make use of).
If you can not code that Python script code yourself to write the needed custom handler/converter/parser/translator for adding that specific device to the “ZHA Device Handlers” repository/library then suggest submitting a “device support request” (with device signature and diagnostic information) as new issues → https://github.com/zigpy/zha-device-handlers/issues
Without a “device support request” as a new issue posted to the “ZHA Device Handlers” repository/library requesting support for an unsupported device or device feature with Device signature and Diagnostic information the ZHA integration developers will not even know about the device unless they by random chance happened to have bought it themselves.
This is a lot of info, thanks for that!
I will take a look and see what I find.
If you can not code that Python script code yourself
I’m not a python expert but can probably put a few lines together. I am however not sure what is the best approach to test this with the real device. Is there any document somewhere where I can find instructions to set up a dev environment for those quirks that allows me to iterate reasonably quick?
The best is however to regardless open a new device support request to ZHA Device Handlers under issues in GitHub repository and then ask the same questions there on tios on how to get started.
I’m currently using one that identifies itself as TS0601. It does not have support for all the fancy things (e.g. metering), but it does turn on and off just fine.
I’ve lost the page where I originally bought it, but it looks like this
Hello,
finally it works the “switch” entity to turn on and off? I’m interested in order the one mention @MS419 in his URL if it’s confirmed that works in ZHA.
Thanks, regards.
