Mine has been working perfectly so far. No hiccups or disconnection. I am on the c8 hub though.
2 Likes
@peterbrown77.pb let us know if your device manages to pair and stay connected to the C-8 hub in your environment. Then, I will add a warning in the top post that it works only with C-8 (there are already at least two other devices that require a Zigbee 3,0 hub and will not fall back to the previous protocol version as required by the Zigbee specifications).
2 Likes
I have several TS0601_IRRIGATION_VALVE
Model: TS0601s and they collect to my Hubitat C8 with no problem but I seem to have only one way communications. I can see the device react to my manually changing the state but I cannot use the app to control the valve. Same result if I try the Sinope Water Valve driver. Here is what I see.
Any help?
Ahovis
Log:
ev:272024-02-07 03:59:59.667 PMinfoFront water valve LIDL frost state (6C) is: 90
dev:272024-02-07 03:59:58.394 PMinfoFront water valve LastIrrigationDuration (72) is: 808791088
dev:272024-02-07 03:59:58.263 PMinfoFront water valve IrrigationEndTime (66) is: 04:28:55
dev:272024-02-07 03:59:57.848 PMinfoFront water valve Front water valve is closed [physical]
dev:272024-02-07 03:59:57.812 PMinfoFront water valve Water Valve State (dp=02) is disabled (0)
dev:272024-02-07 03:59:57.686 PMinfoFront water valve CycleIrrigationNumTimes (67) is: 0
dev:272024-02-07 03:59:57.563 PMinfoFront water valve ?CurrentTempurature? (6A) is: 0
dev:272024-02-07 03:59:53.364 PMinfoFront water valve IrrigationStartTime (65) is: 04:28:50
dev:272024-02-07 03:59:53.265 PMinfoFront water valve Front water valve is open [physical]
dev:272024-02-07 03:59:53.217 PMinfoFront water valve Water Valve State (dp=02) is active (on) (1)
dev:272024-02-07 03:59:53.080 PMinfoFront water valve WaterConsumed (6F) is: 0 (Litres)
dev:272024-02-07 03:59:52.965 PMinfoFront water valve IrrigationEndTime (66) is: --:--:--
dev:272024-02-07 03:59:48.636 PMinfoFront water valve LastIrrigationDuration (72) is: 892808240
dev:272024-02-07 03:59:48.560 PMinfoFront water valve IrrigationEndTime (66) is: 04:28:46
dev:272024-02-07 03:59:48.450 PMinfoFront water valve Front water valve is closed [physical]
dev:272024-02-07 03:59:48.382 PMinfoFront water valve Water Valve State (dp=02) is disabled (0)
dev:272024-02-07 03:59:48.276 PMinfoFront water valve CycleIrrigationNumTimes (67) is: 0
dev:272024-02-07 03:59:48.180 PMinfoFront water valve ?CurrentTempurature? (6A) is: 0
dev:272024-02-07 03:58:05.376 PMinfoFront water valve LIDL frost state (6C) is: 90
More info from debug log:
dev:272024-02-07 04:10:46.550 PMinfoFront water valve Round-trip time : timeout
dev:272024-02-07 04:10:46.547 PMwarnFront water valve no response received (sleepy device or offline?)
dev:272024-02-07 04:10:36.522 PMdebugFront water valve refresh()...
dev:272024-02-07 04:10:36.188 PMdebugFront water valve parseZHAcommand writeAttributeResponse cluster: 0000 status:00
dev:272024-02-07 04:10:36.185 PMdebugFront water valve Desc Map: [raw:catchall: 0104 0000 01 01 0040 00 FA0F 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:FA0F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:272024-02-07 04:10:36.183 PMdebugFront water valve parse: description is catchall: 0104 0000 01 01 0040 00 FA0F 00 00 0000 04 01 00
dev:272024-02-07 04:10:36.168 PMdebugFront water valve parseZHAcommand writeAttributeResponse cluster: E001 status:86
dev:272024-02-07 04:10:36.166 PMdebugFront water valve Desc Map: [raw:catchall: 0104 E001 01 01 0040 00 FA0F 00 00 0000 04 01 8610D0, profileId:0104, clusterId:E001, clusterInt:57345, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:FA0F, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[86, 10, D0]]
dev:272024-02-07 04:10:36.164 PMdebugFront water valve parse: description is catchall: 0104 E001 01 01 0040 00 FA0F 00 00 0000 04 01 8610D0
dev:272024-02-07 04:10:36.148 PMdebugFront water valve Model is : TS0601
dev:272024-02-07 04:10:36.147 PMdebugFront water valve Tuya check-in message (attribute 0001 reported: 48)
dev:272024-02-07 04:10:36.146 PMdebugFront water valve zclVersion is : 03
dev:272024-02-07 04:10:36.144 PMdebugFront water valve Manufacturer is : _TZE200_a7sghmms
dev:272024-02-07 04:10:36.141 PMdebugFront water valve Desc Map: [raw:FA0F01000068040042105F545A453230305F61377367686D6D730000002003010000204805000042065453303630310700003003FEFF003000, dni:FA0F, endpoint:01, cluster:0000, size:68, attrId:0004, encoding:42, command:01, value:_TZE200_a7sghmms, clusterInt:0, attrInt:4, additionalAttrs:[[value:03, encoding:20, attrId:0000, consumedBytes:4, attrInt:0], [value:48, encoding:20, attrId:0001, consumedBytes:4, attrInt:1], [value:TS0601, encoding:42, attrId:0005, consumedBytes:9, attrInt:5]]]
dev:272024-02-07 04:10:36.135 PMdebugFront water valve exception caught while parsing description: read attr - raw:
Is this the LIDL irrigation timer?
I think this is the first report by someone using this model, so there may be something specific for it that must be changed in the driver.
The most important question is whether the valve stays connected to your hub. If you enable the debug logs, do you see periodic messages shown in the live logs tab in a browser? You should also see debug logs when you manually operate the valve from the physical button.
I’m sorry that I’m not very familiar with this process but I have attached the live log and you can see that there seems to be no activity between the last time I made a change and this time (pic 1). Then I manually changed the state and got this (pic 2). Just for interest I also have a Homebridge system available and when I pair it using zigbee2mqtt the plugin finds the device and I can control it fine from zigbee2mqtt but when it is presented in Apple home I see it but have no controls to turn it on or off. With your driver in Hubitat, in HomeKit I have a nice on-off slide switch shown under water but unfortunately, at present it does nothing and the same in the device driver page in Hubitat. I assume I should be able to turn the valve on and off in the Hubitat device driver page without any other settings being changed right?
Pic 1.
Pic 2.
Ok, I left the live log running and indeed it seems to send data every few minutes from what I see below. That answer your question regarding connectivity?
1 Like
Yes, the debug data is enough - thank you!
This maybe way off base but I was wondering if since my zigbee2mqtt with homebridge recognizes my water valve and can control it from the exposes tab could this data be passed to your valve driver by zigbee2mqtt as described in BirdsOnWire’s thread using his driver? I see you were working on some integration there. I need the HA to pass the correct information to Apple Home from zigbee2mqtt to control the valve. If I just use homebridge I get a “device not supported” icon in Apple Home with no controls or automation, however with your driver I see all the controls but unfortunately they don’t control the valve. Anything possible?
Sorry, was “Birdslikewire”
I have the TS0601. I can get it to add to my C8 hub but I have no control or feedback from the device. Health sits at unknown. Any suggestions?
I was able to connect this without an issue to my C7 hub. I am setup is a hubconnect server and my C7 is primarily for just running the automations.
Yep, other users experience the same problem - some new Zigbee 3.0 devices will not stay connected to C-8. These devices are working just fine on C-7.
Could you please advise how to setup for ||manufacturer: _TZ3210|
| --- | --- |
||_Ojxeoadc|
|Data|• model: TS0049|
Here the link of the product
https://amzn.asia/d/hIK3Tos
At the moment I’ve tried all devices profile I get offline or unknown for health check status
1 Like
Hi @sruty9 ,
This in an interesting new device (currently not supported in HE by this driver), but to continue we need to have it stay connected to the Hubitat hub.
The state variables screenshot above shows that this device has left the Zigbee network (we don't have anything in the stats: {RxCtr} which counts the number of the ZigBee messages received).
You must delete it and pair it again with your HE hub.
Then, with the default 'Device' driver, hitting the 'Get Info' button should result in receiving the complete fingerprint in the live logs.
Finally, changing to this driver and clicking on the 'Ping()' button should result in a round-trip time measurement value different than 'timeout'.
Can you try pairing it again?
And what is your hub - C8 or C-7 ?
2 Likes
Just wanted to say you are the man, @kkossev -- I'm not a big Tuya user myself, but your awesome support of the Tuya universe here in Hubitat is really amazing. Thank you - you are a rockstar!
5 Likes
I have all the info I need now. Please wait for a driver update, hopefully this weekend.
1 Like
@sruty9 please update to the dev. branch version 1.3.0.
First, remove the device from your hub and pair it again. This driver must be selected automatically during the pairing process, otherwise the valve will not work in HE.
In the 'State Variables' section of the device page, you must see * deviceProfile : TS0049_IRRIGATION_VALVE.
Enable the debug logs from the Preferences section. When you manually switch on or off the irrigation timer, do you see the valve attribute changing or something else in the live logs?
