Pardon if this post is long -- I want to give as much information as I can.
I installed the C7 about 3 years ago - all zwave devices. Been working great!
I remodeled a lanai and installed more zwave. Great. Now I want to redo a back patch and have a garden I got a tuya zigebee irrigation device. I got the one in this post.
/release-tuya-zigbee-valve-driver-w-healthstatus/92788/294 and used the drivers that @kkosev has worked to develop.
I initially paired it to the C7 no issues, but once I put it in place it wouldn't work on the schedule I assumed it was to far away. The manual button did work and I would just run out and turn it on and off for a few days until the sonoff zigbee plugs arrived so I could extend the network to that side of that house. (those took 3 days to figure out how to pair - I had to plug in and add 2 at a time or zigbee wouldn't see them)
I did what I thought was an exclusion of the valve. I removed from the C7. I even removed the batteries for 30 minutes. I then included the device at the place I would be using it. It was found and added. I did have to go to device preference and change profile from unknown to the TS0049_IRRIGATION_VALVE.
The device now wont even turn on manually for longer than 20 seconds, after that it turns itself off. I checked it and it is again offline. I have repeated the exclusion and removed from C7 and still have the same results. It is currently offline and wont work for longer than 20 seconds manually.
I just had another thought -- they were fresh batteries but could they have heavily drained scanning and looking for the hub for 5 days and that is my issue?
1 Like
This means that your device was not recognised automatically as the correct type..
Please post the device model and manufacturer, as seen at the bottom of the web page - Device Details, Data section.
If you click on the Ping() button, do you see a RTT (Round-Trip Time) numeric value, or you get a Timeout! error?
1 Like
Thanks so much for helping!
- endpointId: 01
- application: 45
- manufacturer: _TZ3210_0jxeoadc
- model: TS0049
- tuyaVersion: 1.0.5
and the ping is timeout
- healthStatus : offline
- powerSource : unknown
- rtt : timeout
1 Like
This clearly states that the irrigation timer does not communicate to the hub.
Pair it again, this time close to the hub. Verify after 2 minutes that the device responds to the Ping() commands.
Then move it close to the mains-powered Zigbee device that is most close to the final placement in the garden. Ensure the valve responds to Ping commands again.
Lastly, move it to its final destination. Will the device still respond to pings ?
I will try that. What about the device preference/change profile? Should I have to do that or is it automatic? I have the driver code loaded into the hubitat.
OOOOK. So I followed your advice to the letter. The device is up and pinging now and has been in place for about 2 hours. However -- if I give it an open command it still only runs for 20 seconds and turns off. It is still in contact and I can see if its open or closed - shouldn't it stay on until I tell it to go off or have it on a schedule in a rule?
It sounds to me like you have an auto off timer set either based on time or volume. Do you have something like this on your device page?
Incidentally, I very much prefer to use the duration command rather than seperate on and off commands. It seems to be much more reliable for these "close to the edge of the mesh" devices, which most outdoor devices are.
1 Like
This is what I have. I have tried adjusting duration using time of 3600 seconds. That did not work.
Commands
Close
close
Configure
configure
Open
open
Ping
ping
Refresh
refresh
Set Irrigation Capacity
setIrrigationCapacity
Set Irrigation Mode
setIrrigationMode
Set Irrigation Timer
setIrrigationTimer
Current States
- battery : 100
- healthStatus : online
- irrigationDuration : 60
- powerSource : battery
- rtt : 777
- timerTimeLeft : 0
- valve : closed
State Variables
- deviceProfile : TS0049_IRRIGATION_VALVE
- lastTx : {pingTime=1716414448260}
- lastRx : {parseTime=1716429594527}
- stats : {RxCtr=414, TxCtr=364, rejoinCtr=29}
- driverVersion : 1.3.1 2024/04/30 7:56 AM
- comment : Works with Tuya TS0001 TS0011 TS011F TS0601 shutoff valves; Tuya, GiEX, Saswell, Lidl irrigation valves
- states : {debounce=false, isRefresh=false, isDigital=false, notPresentCtr=0, lastBattery=100, lastSwitch=closed}
Preferences
I also have the yellow rain seer at the top of this post t/release-tuya-zigbee-valve-driver-w-healthstatus/92788 from @kkossev
@hertzell - you have the same model TS0049 _TZ3210_0jxeoadc Rain Seer irrigation timer. Can you keep the valve open for more than 20..30 seconds?
@nextwavecomputers does the valve close automatically too soon even when you open it from the device physical start/stop button?
Can you make the following test:
- fill in a duration value of 120 seconds (under the 'Set Irrigation Timer' button) -
just prepare the number to be sent later,‘do not click on the button yet.
- click on the Open button
- wait 5 seconds
- click on the Set Irrigation Timer' button - this will send the 120 seconds timeout to the valve.
Will the valve stay open for 120 seconds in this command sequence?
I'll be able to test this next week hopefully. I use the valve on an RV to manage water input and it's not with me at the moment. I did not fully deploy it so I can't say I've seen the issue. Will test.
1 Like
The device would still only run for 30 seconds after a physical button push.
I just filled in duration following your instructions and the device has been open for 5 minutes. I have physically checked this. Also on the device page it is reading this..
- battery : 100
- healthStatus : online
- irrigationDuration : 120
- powerSource : battery
- rtt : 836
- timerTimeLeft : 120
- valve : open
it is showing the above after the 5 minutes. is this supposed to countdown? i assume this is somehow set for minutes rather than seconds.
This automatic closing of the valve seems to be some kind of safety feature, ensuring that the water flow will be stopped automatically, even when the connection to the hub is lost... For Saswell and GiEX the timeout seems to be in seconds, while for this TS0049 device may be in minutes.
@nextwavecomputers if the timer is in minutes and you send a duration of 2 minutes right after opening the valve, will it close automatically after 2 minutes?
The 'timerTimeLeft' attribute is expected to be a countdown...
FYI; I have found the Sonoff plugs to be terrible repeaters. The Sonoff Zigbee 3.0 dongle S is what you want if you’re still having connectivity problems.
Also, @kkossev , my Giex valve timeout is in minutes and works perfectly.
It appears that even with in GiEX there is not consistency. Mine are definitely seconds.
Hello - What I am seeing now is - what ever I have that timer set to is how long the valve runs - regardless of the method of opening the valve. If it is set to 60 minutes and I click open - or physically push the button on the device - it will stay open that length of time.
It will also apply this when I have a schedule set. I have a rule to open the valve for 30 minutes in the morning and again in the evening. If the irrigation timer setting on the configuration page is set to 2 minutes - the valve will close 2 minutes after the rule runs.
That behavior is consistent with what I've experienced.
1 Like
Back late to the party, but with valve in hand now it operates as noted above: in minutes as set and when turned on with physical button press or via HE button press.
