Edge driver for an external Vaticas zigbee water valve actuator

Sorry.
Here it is

Manufacturer: T-
ZE200_dOypnbvn
Model: TS0601
FingerPrinted_EndPoint.Id: 0x01
App Version: 0×46
ZCL Version: Unknown
Network ID: OxE26C
Zigbee EUl: A4C13873B9C394E5
Device ID: Ob49b382-d887-44f8-8fb4-f4802249b443
12:50 PM
Server Cluster:
Ep: 0x01={ 0004,0005,EF00,0000
?
Client Clusters:
Ep: OxF2={ 0021}
Ep: 0x01={ 0019,000A }
Signal Metrics:
LQI: 249 … RSSI: -80 dbm

It use EF00 cluster

How do I do to set the “personal devices EF00 driver”. Do you some tutorial?

Hi @Mariano_Colmenarejo
Thinking in how our smart devices can be used to adapt our behaviour to the changing environment situation.
An example… related to the water restrictions due to lack of rain in some regions like mine in Catalonia Spain, I wonder if your “Zigbee Valve Mc” driver could include an additional slider to open and close the valve partially. The intention is to permanently reduce the flow of water in the circuit.
Thanks in advance.

Hi @Bernfp

That depends on the type of valve.

Normal valves in this driver, Tuya for example, are open close type and have limit switches and stop the movement of the motor.
One is to identify the open position and another the closed position.

I don’t know if there are other types of more complex valves in zwave that monitor the position of the valve and can stop in intermediate positions.

Hi @Mariano_Colmenarejo

Could you help to add the driver for the valve purchased with the link below?

Regen Ziener Tuya Zigbee Tuin Home Irrigatie Watering Timer Wifi Water Timer Mobiele Telefoon Afstandsbediening - AliExpress

Manufacturer : _TZ3210_0jxeoadc
Model : TS0049

Tuya water valve (TS0049 by _TZ3210_0jxeoadc) · Issue #2377 · zigpy/zha-device-handlers · GitHub

Sorry, this device uses EF00 tuya cluster and does not work with my drivers.

You could try with Personal tuya EF00 driver

Hi @Mariano_Colmenarejo

Can you please check if the Valve below is compatible? And if it is, add the fingerprint to your driver?

Manufacturer: _TZ3000_tvuarksa
Model: TS011F
FingerPrinted_EndPoint.Id: 0x01
App Version: 0x43
ZCL Version: 0x03
Network ID: 0xDE49
Zigbee EUI: A4C138E0629EF6A4
Device ID: 99f23f07-3b6b-4836-b68c-8768beb7d225
Server Cluster: Ep: 0x01={ 0000,0003,0004,0005,0006,E000,E001 }
Client Clusters: Ep: 0x01={ 000A }

Thank you very much!

Hi @Rahul_Isola

This device exist in my driver zigbee valve Mc since 2023.

Install the driver from my channel in your hub and reinstall device with app and search nearby option

Interesting. I already use your channel and have it installed. But when I added the device it gets added as a switch and not a valve. I don’t see valve as one of the options when trying to change drivers too. What am I missing?

Thank you very much again for looking into this!

Sorry, there is an error in model.
Fixed in this driver version

───────────────────────────────────────────────────
 Name         Zigbee Valve Mc
 Version      2024-12-05T11:55:44.544145562        
───────────────────────────────────────────────────

Thank you. I’m able to select the updated driver now.
But it doesn’t seem to be working properly.
It is stuck in ‘Open’ status, while the device is actually closed.
It works just once at startup to actually close the device from open, but the status keeps loading and stuck at opening.
Changing it back to switch, or manually clicking the button seems to make it work properly.

Hi @Mariano_Colmenarejo,

Following up on this. Is there anything I am doing wrong? I tried removing and readding the device, same behavior. Doesn’t close with the Zigbee Valve Mv driver but works fine with the standard zigbee switch driver.

Additionally, do you also have a door / window open / close sensor driver by any chance? I have one that is detected with a ‘generic sensor’ profile which I wanted to change to ‘contact-battery-tamperalert’.

Thanks again for all the help you do for the community!

Physically the valve closes and the closed status is not updated in the app or does it not close physically?

It is logical that it works well with the zigbee switch driver since it works as a switch.

The only difference in the driver is that the valve driver works with the valve defaults from the hub libraries and the switch driver works with the switch libraries. The only difference is that the valve defaults do not handle the default_response command and it is possible that this device responds to the Off and On command with the default_response command.

To verify that this is the problem, I would need you to send me an answer to the first question and send me some logs with the CLI of when you press Off or On in the app.

Sorry, I don’t have any profile in the driver that handles tamper, It would need to modify the whole driver to be able to handle tamper and open close events manually instead of using the defaults from the hub libraries.
When smartthings adds tamper to the zigbee defaults then I will add it

@Mariano_Colmenarejo - It is the 1st case - Physically the valve closes and the closed status is not updated in the app

Logs below:
{Deleted logs to clean up thread}

I’ll be happy to provide further logs of specific events if you need. Please let me know what you need and I’ll send it over.

Thanks

It’s very strange.
The driver sends the Off command to the device

The device responds:

  • with the reportAttribute command which is Open (true or On)

2024-12-09T17:32:54.561948983Z INFO Zigbee Valve Mc <ZigbeeDevice: 8a06d327-4527-44fa-84db-92ae17970681 [0x88D1] (Water Valve)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x88D1, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -58, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint8, OnOff: true > > > >

  • with the defaultResponse command which is Closed (0x00 or Off)

2024-12-09T17:32:54.571234483Z INFO Zigbee Valve Mc <ZigbeeDevice: 8a06d327-4527-44fa-84db-92ae17970681 [0x88D1] (Water Valve)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x88D1, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -58, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x14, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >

As the zigbee valve driver only handles the reportAttribute command it sends event Open.

2024-12-09T17:32:54.580073483Z INFO Zigbee Valve Mc <ZigbeeDevice: 8a06d327-4527-44fa-84db-92ae17970681 [0x88D1] (Water Valve)> emitting event: {“attribute_id”:“valve”,“capability_id”:“valve”,“component_id”:“main”,“state”:{“value”:“open”}}

As the zigbee switch handles both commands and defaultResponse arrives after reporAttribute then it sends On and then Off.

Can you send me when you try to open, let’s see what it sends?

Try installing this driver version.
I added a new subdriver for this device

───────────────────────────────────────────────────
 Name         Zigbee Valve Mc
 Version      2024-12-09T18:26:16.687919176        
───────────────────────────────────────────────────

@Mariano_Colmenarejo Thanks. Tried with the new driver, same issue. How do I get the logs for opening the valve? When I use your driver, it is always on ‘Open’ state. So no possibility for me to try opening it from closed state without switching it back to switch. Do you want me to change to switch and send the logs?

It can’t be that it works the same.

How did you install it, with the CLI?
Can you send me the logs of closing the valve with the new driver?

@Mariano_Colmenarejo I changed the driver to switch, went to your channel, uninstalled and reinstalled the valve driver and changed the device back to the valve. Verified the version to be what you mentioned above.
BTW - apologies. Now it doesn’t respond physically too. And I see a few errors in the logs now.

Logs below:
{Deleted logs to clean up thread}