Sorry to resurrect this. has anyone got this going?
I've got MarkC's driver, but the devices is not updating the heating set point and not reporting a current temperature.
Any ideas?
1 Like
Sure it's my driver? I haven't got battery reporting to work. And it's working ok for me
Just removed and re-added. it comes up straight away with your driver by default, with the battery. But no current temp and no working set point.
The battery does change a lot, every few seconds if you play with the trv,
Have you set preference on the device, like time and away/off set point, have you changed mode to heat/manual. If in auto it won't accept commands as it will run on its own schedual
Hello @mark.cockcroft, it looks the same for me
The battery status seems to be changing randomly here as well.
I'am using version 2020-12-01 of your Zigbee Driver
The valves I'm using are bought directly from a vendor that sells Tuya branded products.
Have you set the device up on the device? Time, heating setpoints something in my mind says you need to set the temp for the aeroplane icon (it's off mode)
Take a picture of the device
You have to set up the trv on the trv itself.
Go through all the settings in the manual at set the away/holiday temperature
These are two pictures (the second one is to see all possible display options.)
The manual states that the clock icon is the mode in which the the TRV is programmable to the automatic time set temperature changes.
When set to this mode and pressing "Configure" in hubitat, the only thing that happens is the log "logging"
warn configure...
info Zigbee - Tuya TRV updated...
No other changes on the device page.
That's not the model i have
It's not what I have either. I think you'll need to uncomment the log.debug line in the parse method of the driver and provide us with some more data of what the device reports when you see the battery information changing.
1 Like
Hi,
I too have the same TRV which @danirtoma has, I think I've commented out the right log debug part of the Driver Code, this is the output:
dev:11232021-04-22 07:26:02.256 pm debug
Unhandled Event IGNORE THIS - description:read attr - raw: 9D0A0100000A00002003, dni: 9D0A, endpoint: 01, cluster: 0000, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 03 | msgMap:[raw:9D0A0100000A00002003, dni:9D0A, endpoint:01, cluster:0000, size:0A, attrId:0000, encoding:20, command:01, value:03, clusterInt:0, attrInt:0, valueParsed:3]
Does that help in any way?
Cheers
Guy
Could you post a picture of what you do have please?
That line in the driver catches information from the device that isnt being handled. Currently, the battery information report is being handled (line 203 and another case line 210).
Therefore, you want to add a debugging line such as:
log.debug "Battery debug: desc: ${description} | msgMap: ${msgMap}"
On lines 204 and 211. Hopefully that will give the info needed
Hi,
I think I've added the right comment in the code after hitting refresh:
dev:11232021-04-23 02:20:36.479 pm infoOn/heat/manual command
dev:11232021-04-23 02:20:33.771 pm infoheating setpoint to 21
dev:11232021-04-23 02:20:17.020 pm warnpase lin 59 used - read attr - raw: 9D0A0100000A00002003, dni: 9D0A, endpoint: 01, cluster: 0000, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 03
dev:11232021-04-23 02:20:17.000 pm warnpase lin 59 used - read attr - raw: 9D0A0100000A00002003, dni: 9D0A, endpoint: 01, cluster: 0000, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 03
dev:11232021-04-23 02:20:16.956 pm warnpase lin 59 used - read attr - raw: 9D0A0100000A00002003, dni: 9D0A, endpoint: 01, cluster: 0000, size: 0A, attrId: 0000, encoding: 20, command: 01, value: 03
dev:11232021-04-23 02:20:13.692 pm debugrefresh
Best wishes,
Guy
I've just ordered one these ones (just in case) 
Just got one of these and am testing now.
No luck with kkosev's driver, nor Mark's.
- application: 43
- endpointId: 01
- inClusters: 0004,0005,EF00,0000
- lastRunningMode: heat
- manufacturer: _TZE200_6rdj8dzm
- model: TS0601
- outClusters: 0019,000A
- profileId: 0104
Anyone got any other driver suggestions ?
