SonOff Smart Water Valve?

[MarenB]

Hi,

Unfortunately I checked the compatibility list of the genuine zigbee2mqtt instead of its tasmota implemetation before ordering the part.
Now I have this irrigation valve on my desk and my ZbBridge with Tasmota 14.6.0 publishes some data, for example

{
"ZbReceived": {
"Versenkregner": {
"Device": "0xC717",
"Name": "Versenkregner",
"FC11/5006": 4,
"FC11/5007": 0,
"FC11/500E": 1744879573,
"Endpoint": 1,
"LinkQuality": 94
}
}
}

but I can't do a lot with it.
Any chance to get this fully implemeted and supported?

[s-hadinger]

If you find the meaning of the attributes, you can create a plug-in file to convert them to a more readable format. If Zigbee2MQTT did the work, you may find some help here (or in its source code)

[MarenB]

Thanks! I replied to the comment below because you both pointed into the same direction, but I appreciated your response too, of course :)

[sfromis]

While I know nothing about the device, a quick Google search on the cluster and attribute codes brought up something looking quite relevant, linking those attribute codes to something Sonoff irrigation.
https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Zigbee%20Valve/Tuya%20Zigbee%20Valve.groovy
That looks like your 3 attributes could be duration, volume and end time.
The time value 1744879573 converts to 2025-04-17 10:46:13

[MarenB]

Some testing later:

I can open and close the valve, that's fine. But I failed to set advanced features, such as auto-off-timer. More than one command per zbsend is not allowed and it doesn't recognize the related datapoints, if I understand correctly.

For example, these payloads are rejected:

{
"device": "Versenkregner",
"send": { "TuyaSend": "3,600" }
}

{
"device": "Versenkregner",
"send": { "DpType2Id3": 600 }
}

It would be great, if someone could give me a hint, before I replace my bridge with a full zigbee2mqtt implementation on a Pi.

[sfromis]

Where did you even get the idea of Tuya-related names applying to a Sonoff device? Tuya has the "bad habit" of not caring about Zigbee standards, but do something very different. Your first post showed attributes without names.

The preferable way (as s-hadinger alluded to) would be to create a device plugin definition file with names/types for the attributes, to work with "normal" ZbSend commands.
https://tasmota.github.io/docs/Zigbee/#advanced-topic-zigbee-device-plugin

IIRC, you can also use the "numerical" formats for attribute when you have not assigned names.

But if you already are using Zigbee2MQTT, you could consider having the coordinator function there, instead of the narrower support from Zigbee2Tasmota.

[MarenB]

When I started setting up my smarthome system, I had issues with zigbee2mqtt, that's why I switched to zigbee2tasmota, although the bridge is my only Tasmota device.

I guess, using Tuya's DP was the idea of ChatGPT. I just have too many projects to completely learn every programming language, etc. in detail, that's why I tried to short cut this here.

Actually, the only thing I am missing currenty is the auto-off-timer. In case of connection issues while the sprinkler is on I don't want to flood my garden, so it must turn off after some time independently.

Guess I need to find out how to combine this
https://github.com/arendst/Tasmota/blob/development/tasmota/zigbee/giex_water.zb
with this:
https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/sonoff.ts
to get the complete plugin-file. Correct?

[MarenB]

Finally, I understood it, I hope :)

For the records and anybody else who want to use this valve:

Create a textfile "sonoff_swv" but with ending "zb" ( = sonoff_swv.zb) and upload it to the filesystem (or create it directly there).

The file needs to contain the following:

#Z2Tv1
# Sonoff SWV - Smart Water Valve
:SWV,

# Proprietärer Cluster 0xFC11
FC11/5006,lastValveOpenDuration      
FC11/5007,irrigationVolume,mul:0.1   
FC11/500C,valveStatus                
FC11/500D,irrigationStartTime   
FC11/500E,irrigationEndTime     
FC11/500F,dailyIrrigationVolume     
FC11/5010,workState                 

FC11/5008,cyclicTimedIrrigation     
FC11/5009,cyclicVolumeIrrigation    
FC11/500A,weeklySchedule            
FC11/500B,scheduleSkip            

It's actually much simpler than the lenght of the documentation implies :)

[tobiasisenberg]

Hi @MarenB ,

Thanks a lot for this information. I wonder if you have figured out some more information in the meantime. In particular, what are the units for FC11/5006,lastValveOpenDuration and FC11/500F,dailyIrrigationVolume, what are possible values and their meanings for FC11/500C,valveStatus and FC11/5010,workState, and how do you set FC11/5008,cyclicTimedIrrigation, FC11/5009,cyclicVolumeIrrigation, FC11/500A,weeklySchedule, and FC11/500B,scheduleSkip? I figured out that FC11/500D,irrigationStartTime and FC11/500E,irrigationEndTime are given in Linux Epoch time (provided that the correct time zone was set for Tasmota (use https://tasmotatimezone.com/ to do that). Finally, did you figure out how to set the auto_close_when_water_shortage value that is mentioned for the device in ZigBee2MQTT, or is this one of the status/state values you already have? And out of curiosity, how did you match the addresses to their meanings? I did not find the respective info in the ZigBee2MQTT code base to which you linked.

Thanks a lot in advance!

[MarenB]

Hi Tobias,
tbh, I have no clue how to use the more sophisticated settings such as related to the Schedule. I assume, if you have the genuine Sonoff Hub and use the related app, you could get some actual readings, but I simply don't use it.

I searched my browser history, but I can't find the actual source of this. However, this might by useful at least:
https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/sonoff.ts (SWV starts at line 1504).
And further:
https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Zigbee%20Valve/Tuya%20Zigbee%20Valve.groovy

I built a Node-RED flow to control the valve and analyze the realtime data returned. It's basically "turn the valve on, wait for the desired total amount of water to be reported, close valve". I don't use any of the other integrated functions, except for the battery state, maybe.

[tobiasisenberg]

Many thanks! The second link is great. I am testing currently and hope to get a better idea of how things work soon.

[MarenB]

Ah, yes, there it is! Starting as of
"void parseSonoffCluster(Map it, String description) {... "
somewhere a little below the middle of the file.

[dirkseidel]

Hi @MarenB,

you mentioned that you managed to switch the SWV on and off. Unfortunately I am unable to achieve this.
After creating both files sonoff_swv.zb and sonoff_swv.js I get the following console output when switching the valve on and off manually:

console.txt

But I don't know what command I have to publish in Loxone to get this to work.
Using e.g. "publish cmnd/tasmota/POWER ON" leads to

21:29:16.264 CMD: Grp 0, Cmd 'POWER', Idx 1, Len 2, Pld 1, Data 'ON'
21:29:16.268 MQT: stat/tasmota/RESULT = {"Command":"Error","Input":"POWER ON"}

Of course this can't be correct anyway, as it does not even include the device("SWV") to send the command to.
Can you please help me?

[sfromis]

While I know nothing about how to use that device, in general sending commands is not the usual Tasmota commands (like Power) for locally connected relays etc, but specific Zigbee commands. One example:
ZbSend {"Device":"SWV","Send":{"Power":1}}
This assumes that you've already used the command ZbName to assign the name SWV

(Not trying to say "this will work", only mentioning how it usually can be done)

[dirkseidel]

That did the trick, thanks a lot!

[tobiasisenberg]

@dirkseidel I don't know why you used a *.js file, but the only file that you need to create on Tasmota is the sonoff_swv.zb file. Here's an update based most recent tests (the FC11/5007 value does not have to be divided by 10):

#Z2Tv1
# Sonoff SWV - Smart Water Valve
# device info: https://www.zigbee2mqtt.io/devices/SWV.html
# device info: https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Zigbee%20Valve/Tuya%20Zigbee%20Valve.groovy
# device discussion: https://github.com/arendst/Tasmota/discussions/23308
:SWV,SONOFF
# proprietary cluster 0xFC11
FC11/5006,LastValveOpenDuration         # real-time irrigation duration, in seconds, but somehow unclear how it really works
FC11/5007,TotalIrrigationVolume         # some other water volume counter, accumulates the daily counts, in liters; unclear when it gets reset to 0
FC11/500C,ValveStatus                   # 0 - normal state, 1 - water shortage, 2 - water leakage, 3 - water shortage & water leakage
FC11/500D,IrrigationStartTime           # this and next in Unix Epoch time in seconds, but time zone on Tasmota does not seem to matter, always seems to sends epoch in local time
FC11/500E,IrrigationEndTime             # btw, one can use https://tasmotatimezone.com/ to configure one's timezone for Tasmota
FC11/500F,DailyIrrigationVolume         # total daily irrigation volume, in liters; only gets reset to 0 upon starting a new irrigation
FC11/5010,WorkState                     # 0 - manual control; 1 - cycle timing / quantity control; 2 - schedule control
FC11/5008,CyclicTimedIrrigation         # string, see kkossev/Hubitat link above; reported empty by default when polled
FC11/5009,CyclicVolumeIrrigation        # string, see kkossev/Hubitat link above; reported empty by default when polled
FC11/500A,WeeklySchedule                # string, see kkossev/Hubitat link above; not reported when polled
FC11/500B,ScheduleSkip                  # see kkossev/Hubitat link above; not reported when polled
# what end point is auto_close_when_water_shortage ?

[dirkseidel]

I don't know what impact, if any, the .js file has. I hoped it would help, which of course didn't, as I always send the wrong commands to the bridge...
Thanks for the updated .zb file!