Update, the valve joined up perfectly. It joined as a Device, obviously no driver exists for it yet. I switched to the Sinope water valve Driver and I can operate it. Battery is reading 100%, and open and close works. Maybe lots of information below to make it fully functional / develop a driver for it @mike.maxwell
Update 2, a few attributes are being skipped with the Sinope Water Valve driver, as expected. I would assume one of these are for the water flow. You can see the value increasing as the time goes on with the valve open
Yes it will work, but having the proper driver will ensure the battery level reads correctly, and the flow is being reported and / or any other special functions. It will prevent errors from popping up in the logs, right now the driver doesn't know what to do with the extra messages being received from the device, it is either ignored or an error is thrown. Some use the flow to shut off the device, i.e. x liters of water then close the valve. Also good in case a valve is left on or missed the close command as a second shut off.
I ordered one of these and its been working fine with simple Open/Closed commands provided via the Sinope driver.
In the last couple of days though controlling the valve either through HE or via the Open/Close button on the device itself opens the valve for 1 second before it then closes itself. I doubt the issue is with HE as it is the same issue using the button on the device but I thought I would share on here.
I've messaged Sonoff for help, will see if they can suggest anything before I return it.
I really love the valve (when it worked) and it would be great to get an official driver for this to potentially unlock the other features.
I recently got 3 of these and I'm using the native Sinope Water Valve driver, which does work but has some deficiencies. The full battery level always starts off showing 62%, and I have to refresh the device in order to get feedback to confirm position changes, and flow rate seems to not work at all. Anybody working on/aware of a new or better driver for this device yet?
*** UPDATE ***
Somehow I missed post above about the Tuya driver; after installing that driver, turning on Advanced Options, and selecting the SONOFF_SWV_VALVE model, things are working much better. Only thing that still doesn't seem functional is the Rate, although at least now there is now a value for irrigationVolume.
I just purchased one to test and and found the generic switch driver also works but the Tuya driver was a much better fit.
In case anyone is interested, I ran a flow test against the orbit Bhyve and found that the Sonoff valve had a much better flow rate. My flow directly from the spigot is around 10gpm at 50psi. The Bhyve restricted the flow rate to 7.5gpm. The Sonoff's flow approached the 10gpm rate. I was pretty impressed with a sub $30 zigbee water valve.
The tests were performed using a 5 gallon bucket and a stop watch.
I just got one, and chose the Tuya driver. It works from the devices panel in HE. But the HomeKit integration doesn't quite work. You can turn it on, but it doesn't get the correct status (just says it's updating...) and in a few minutes indicates that it's off. I have to turn it on and off again in the Home app to get it to actually turn off. I'll try another driver mentioned in this thread, but it would be nice to have one specifically for this device. Anyone working on one?
Update to say I went on vacation this past week and while away I noticed the hose timer switch was on! I quickly logged into my HE remotely and saw that it had two conflicting statuses:
switch: on
valve: closed
Don't know how the switch status changed but at least I didn't come home to a flood.
Long story short, I have yet to find a fully functioning driver.
Until the core reason for the HomeKit integration issue is found and a solution is available, you could try the HE inbuilt 'Mirror' app. Map a virtual switch attribute (on/off) to the Zonoff device valve attribute (open/closed), then expose the virtual switch to HomeKit.
I’ve noticed that HomeKit reports correctly, but only when I go into the valve driver and click refresh, and the valve state updates from closed to open.
But then it also says “waiting”. Not sure what for
There is no need to refresh the valve state, this is done automatically as soon as the valve confirms the open or the closed position. The problem is somewhere else...
Do we have any HE inbuilt valve driver that works as expected with the homeKit integration?
I could compare the capabilities/attributes then... but I need a stock driver for a reference.
- I had a conflicting rule which was impacting the valve.
