Yes you configure your Zigbee2mqtt integration in external mode, with the information you displayed on screen! (You will need to change the broker URL to use the correct IP)
Thanks @Will_71 for the image!
And so first test at my place:
At first glance, apart from the switch, nothing else works for me 
However, on the source, I do have the info:
Interesting thing but I don’t know why.
I launched MQTT Explorer to check after the first test and there: nothing in the valve topic (except the on state).
Then I sent an on to my production and all the info appeared in MQTT Explorer 
Of course I had the info in test Gladys:
I set it to
on in test and a few values changed: water flow rate, daily irrigation volume, and current irrigation volume. However, there was no change in the current irrigation duration.This being written, it also doesn’t change in Z2M (version 2.12.1) whereas it was working before (<2.12.0). Well anyway, we get the correct values back so I’d say okay.
A few remarks if you can:
- water flow rate: no need for seconds or liters, it’s a volume/time
- current irrigation program: not sure if it’s relevant as it seems to correspond to what can be set in Z2M. However, if we can retrieve everything, it can avoid creating scenes to set 10 minutes of watering for example.
- Water valve state: 3 states, I don’t know if you have them. I don’t know when they occur.
It looks great! Plus, we can retrieve all the information. Thanks @Will_71
Thanks for the tests.
For the valve status, I saw that it is well detected
Did you add it to your list?
No problem with the units, I’ll look into correcting them.
For the current irrigation program, I’ll see what I can do, but if it allows access in scenes, it could be useful
I didn’t express myself well 
I do have the state in Gladys, no worries, I just wanted to say that there are 3 states in total and to know if the other 2 exist in Gladys to display them along with their translations.
Actually, we manage:
- either the switch-ons, timing, water flowing in the scenes
- or we manage with these parameters but outside the scenes, a bit like we would manually control the air conditioning or shutters.
I had understood perfectly
For the state, yes, no problem, I have all the texts:
And the translations, of course.
@mutmut, I made some changes if you can retest on the same image.
I created a new display for the setting because with large values, whether the slider or the numerical value, it wasn’t optimal for modifying the values.
Here’s what it looks like (ignore the values as it’s just a test).
Keep me posted!
Thanks for the update!
On the MQTT Explorer side, I do see the reflection when I change a value, but nothing in Z2M or rather an error:
z2m: Publish 'set' 'cyclic_quantitative_irrigation' to 'robinet_arrosage' failed: 'Error: ZCL command 0x44e2f8fffe051863/1 customClusterEwelink.write({"20489":{"value":{"0":10,"1":0,"2":0,"3":0,"4":0,"5":0,"6":83,"7":0,"8":0,"9":0,"10":0},"type":66}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'INVALID_VALUE')'
z2m: Publish 'set' 'cyclic_quantitative_irrigation' to 'robinet_arrosage' failed: 'Error: ZCL command 0x44e2f8fffe051863/1 customClusterEwelink.write({"20489":{"value":{"0":10,"1":0,"2":0,"3":0,"4":0,"5":0,"6":226,"7":0,"8":0,"9":0,"10":0},"type":66}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'INVALID_VALUE')'
z2m: Publish 'set' 'cyclic_quantitative_irrigation' to 'robinet_arrosage' failed: 'Error: ZCL command 0x44e2f8fffe051863/1 customClusterEwelink.write({"20489":{"value":{"0":10,"1":0,"2":0,"3":0,"4":0,"5":0,"6":0,"7":0,"8":0,"9":0,"10":0},"type":66}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'INVALID_VALUE')'
That said, I’ve never managed to change these values directly in Z2M and have them stay fixed (it always goes back to the default « neutral » value).
EDIT:
and when I modify directly in Z2M, I get this:
z2m: Publish 'set' 'cyclic_timed_irrigation' to 'robinet_arrosage' failed: 'Error: ZCL command 0x44e2f8fffe051863/1 customClusterEwelink.write({"20488":{"value":{"0":10,"1":0,"2":10,"3":0,"4":0,"5":0,"6":0,"7":0,"8":0,"9":0,"10":0},"type":66}}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Status 'INVALID_VALUE')'
So, what actually works? Because if there are issues with MQTT Explorer and Z2M, there will be the same with Gladys. So is it worth adding them?
For me, it’s not worth adding all the cyclic_xxxxx_irrigation.
OK, in that case, I’ll remove Cyclic timed irrigation (composite) and Cyclic quantitative irrigation (composite).
I’ll create a new image as soon as possible.
@mutmut, I deleted these slides. The image is available
@mutmut, have you tested the latest image?
Not yet and I won’t be home until Sunday, so it’s not possible before that, sorry.
no problem have a good weekend
@Will_71 I just tested your latest image, everything is fine with the units and we no longer have the « cyclic blabla » so it’s great. The zigbee2mqtt:robinet_arrosage:water-valve:valve-work-state:valve_work_state feature seems to be linked to the « cyclic » so in my opinion, it’s not necessary either:
Hi @Will_71,
I just bought one… But in Tuya, I’ll create a PR for that, but I’ll wait to align with yours (well, to merge it to get your new categories and types). 
I’ll follow to see when it’s integrable.
After that, it’s just a binary value, it will be present if one day it works on the valve.
If it is really not used, I would remove it.