[RELEASE] Tuya Wall Mount Thermostat (Water/Electric Floor Heating) Zigbee driver

Hi @kkossev is this new device also supported in the new dev branch?

Sorry @amithalp , not yet - all this new Matter stuff took my free time in the last week...
This driver is one of my firsts, and it became very difficult to maintain and add new models.
Your TRV will be added to the new driver, hopefully, I can restore the work on it soon.


1 Like

Oh, I've just realised that the set points are altering as expected but the room temperature isn't reporting back to to HE from the TRV. It appears to be stuck on 22 degrees when I look at the current states


Sometimes, the current states are not updated on the device web page, but the attributes are actually changed. Press F5 in the PC browser to double-check this.

I will need the Debug logs that include the time when the room temperature is changed on the TRV.
Please use a desktop PC browser and select/copy/paste the debug logs as a text (I need the text logs to be able to simulate your device).

I use a hair dryer to change the temperature rapidly for tests.

hi @kkossev i hope these logs are adequate. i've artificially inflated the room temperature by warming the TRV. I do hope the logs provide the necessary info to correct this issue. Appreciated...Stu

dev:14842023-12-29 00:39:26.840warnnot parsed : [raw:catchall: 0104 EF00 01 01 0040 00 AA55 01 00 0000 11 01 003851, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:AA55, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 38, 51]]

dev:14842023-12-29 00:39:06.866debugTRV MILES device has received Tuya cluster ZCL command 0x24 response 0x00 data = [24, 00]

dev:14842023-12-29 00:39:06.698debugTRV MILES sending time data : [he cmd 0xAA55 0x01 0xEF00 0x24 {0008658E152A658E152A}, delay 2000]

dev:14842023-12-29 00:39:06.695debugTRV MILES timezone offset of current location is 0 (0 hours), current hour is 0 h

dev:14842023-12-29 00:39:06.599debugTRV MILES time synchronization request from device, descMap = [raw:catchall: 0104 EF00 01 01 0040 00 AA55 01 00 0000 24 01 0037, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:AA55, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[00, 37]]

dev:14842023-12-29 00:38:56.291warnnot parsed : [raw:catchall: 0000 0013 00 00 0040 00 AA55 00 00 0000 00 00 8555AA5A632DFEFFEA359080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:AA55, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[85, 55, AA, 5A, 63, 2D, FE, FF, EA, 35, 90, 80]]

dev:14842023-12-29 00:38:55.818debug(duplicate) transid=176 dp_id=2 dp=3 fncmd=250 command=01 data = [01, B0, 03, 02, 00, 04, 00, 00, 00, FA]

dev:14842023-12-29 00:38:25.499debugTRV MILES HY369 mode (dp=3, fncmd=250) not processed!

dev:14842023-12-29 00:38:25.497debugTRV MILES processing command dp=3 fncmd=250 (lastThermostatMode=heat)

dev:14842023-12-29 00:38:25.495debugTRV MILES dp_id=2 dp=3 fncmd=250

dev:14842023-12-29 00:38:12.531warnTRV MILES Thermostat model group HY369 is not processed! (dp=4, fncmd=2)

dev:14842023-12-29 00:38:12.529debugTRV MILES dp_id=4 dp=4 fncmd=2

dev:14842023-12-29 00:38:12.322debugTRV MILES HY369 mode (dp=3, fncmd=245) not processed!

dev:14842023-12-29 00:38:12.320debugTRV MILES processing command dp=3 fncmd=245 (lastThermostatMode=heat)

dev:14842023-12-29 00:38:12.318debugTRV MILES dp_id=2 dp=3 fncmd=245

dev:14842023-12-29 00:38:12.105infoTRV MILES heatingSetpoint is: 25.0°C

dev:14842023-12-29 00:38:12.101debugTRV MILES dp_id=2 dp=2 fncmd=250

dev:14842023-12-29 00:38:10.278warnTRV MILES Thermostat model group HY369 is not processed! (dp=4, fncmd=2)

dev:14842023-12-29 00:38:10.273debugTRV MILES dp_id=4 dp=4 fncmd=2

dev:14842023-12-29 00:38:10.065debugTRV MILES HY369 mode (dp=3, fncmd=245) not processed!

dev:14842023-12-29 00:38:10.063debugTRV MILES processing command dp=3 fncmd=245 (lastThermostatMode=heat)

dev:14842023-12-29 00:38:10.061debugTRV MILES dp_id=2 dp=3 fncmd=245

dev:14842023-12-29 00:38:09.899infoTRV MILES heatingSetpoint is: 24.0°C

dev:14842023-12-29 00:38:09.891debugTRV MILES dp_id=2 dp=2 fncmd=240

dev:14842023-12-29 00:29:46.627debugTRV MILES HY369 mode (dp=3, fncmd=235) not processed!

dev:14842023-12-29 00:29:46.626debugTRV MILES processing command dp=3 fncmd=235 (lastThermostatMode=heat)

dev:14842023-12-29 00:29:46.624debugTRV MILES dp_id=2 dp=3 fncmd=235

dev:14842023-12-29 00:00:07.517infoTRV MILES HY367/HY369 valve opening percentage (dp=109) is: 25 %

dev:14842023-12-29 00:00:07.513debugTRV MILES dp_id=2 dp=109 fncmd=25

dev:14842023-12-29 00:00:07.274debugTRV MILES HY369 mode (dp=3, fncmd=235) not processed!

dev:14842023-12-29 00:00:07.270debugTRV MILES processing command dp=3 fncmd=235 (lastThermostatMode=heat)

dev:14842023-12-29 00:00:07.266debugTRV MILES dp_id=2 dp=3 fncmd=235

dev:14842023-12-28 23:59:32.667debugTRV MILES device has received Tuya cluster ZCL command 0x24 response 0x00 data = [24, 00]

dev:14842023-12-28 23:59:32.513debugTRV MILES sending time data : [he cmd 0xAA55 0x01 0xEF00 0x24 {0008658E0BE4658E0BE4}, delay 2000]

dev:14842023-12-28 23:59:32.509debugTRV MILES timezone offset of current location is 0 (0 hours), current hour is 23 h

dev:14842023-12-28 23:59:32.506debugTRV MILES time synchronization request from device, descMap = [raw:catchall: 0104 EF00 01 01 0040 00 AA55 01 00 0000 24 01 0035, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:AA55, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[00, 35]]

dev:14842023-12-28 23:44:46.746infoTRV MILES HY367/HY369 valve opening percentage (dp=109) is: 100 %

dev:14842023-12-28 23:44:46.738debugTRV MILES dp_id=2 dp=109 fncmd=100

dev:14842023-12-28 23:44:46.575debugTRV MILES HY369 mode (dp=3, fncmd=235) not processed!

dev:14842023-12-28 23:44:46.573debugTRV MILES processing command dp=3 fncmd=235 (lastThermostatMode=heat)

dev:14842023-12-28 23:44:46.571debugTRV MILES dp_id=2 dp=3 fncmd=235

1 Like

@kkossev
I am confused, I should expect the TVR's are covered in this post/driver [ALPHA] Tuya / Moes BRT-100 TRV driver - :gear: Custom Apps and Drivers / Custom Drivers - Hubitat
Does the driver from this topic supports wall mount and TVR?

Hi Bruno,

You are correct - the new models of TRVs and thermostats should be covered in the new driver.
The TRV07, HY367 and HY369 were the last models added to this old driver a month ago.

@stueyhughes I see now that your TRV does not match the HY369 group.
I will add it to the new driver, but it will take some more time.

1 Like

Thanks @kkossev. What a real shame. I was hoping to plug and play but eagerly await your driver update. Much appreciated and look forwards to your help once again. Appreciated...Stu

Hi. Will you be supporting the TZE204_aoclfnxz TS0601? I note that there is a quirk for it at
https://community.home-assistant.io/t/newly-added-custom-quirk-for-ts0601-by-tze204-aoclfnxz-not-recognized-solved/635370
Many thanks in advance for your response
Toby

I am looking to add thermostat to my pellet stove which would need to have remote capiably and the contact box switch need to be remote as well too since wood stove location and themstat would be across room from each other.

I am looking at something like this Tuya Wifi RF Smart Thermostat Switch Temperature Controller for Gas Boiler Water Heating Support Alexa Google Home Yandex Alice - Walmart.com

Would this driver work with this?

Why do you prefer WiFi?
All WiFi devices use proprietary protocols and are cloud-dependent...

You can try one of the Zigbee thermostats - as an example, this one: Air Conditioning Floor Heating 2-in-1 Zigbee/WiFi Mobile Control Thermostat - Walmart.com

Note, that there is no guarantee that what you will receive will be one of the models supported in this driver. Purchasing Tuya devices is always a risk.

I been looking for zigbee or zwave version .. let me go look ..

Does it come with a remote contact switch box or it have to be wired directly to the pellet stove?

Reason I was looking at the wifi version is because it come with a contact box that is hooked up to source for off/on switch then thermostat control the contact box wirelessly

The one you linked is wire directly to the thermostat. It won't work for me since I need the thermostat to be mounted on wall on other side of the room so it doesn't shut off the pellet wood stove prematurely before filling the room with heat to the other side.

I would have prefer remote control with thermostat built into it with wall mount and it have a wireless contact box for pellet stove but unfortunely I am unable to find anything with zigbee or zwave included into the system yet .. - Amazon.com

I been searching everywhere on Aliexpress but no luck yet or nobody have manufactured one yet

Hi @kkossev apologies for the request. Do you have an indication when you would be able to amend the driver to incorporate this TRV. Appreciated in advance :slight_smile:

Hi @stueyhughes , hopefully I can come back to this request after a week or two.
Currently, I am intensively working on Zemismart M1 - Matter Bridge for Tuya Zigbee devices project, and there is a critical volume of initial efforts that must be put into this, in order to release the first alpha-version for broader testing.

This driver (Tuya Wall Thermostat) will not be extended with new thermostats and TRVs, it came to a state where this is almost not possible.

New Tuya thermostats and TRVs will be added to the new [ALPHA] Tuya / Moes BRT-100 TRV driver, I will follow-up in this thread.

1 Like

Thank @kkossev you're really generous and we all appreciate how busy you are. Thanks for the update, we look forwards to your driver :slight_smile:

1 Like

Hi @kkossev. Thanks for your awesome work!
I would like to buy some thermostats for my floor electric heating. Could you confirm that they all work with your driver:
https://de.aliexpress.com/item/1005004819384249.html (AVATTO 2.0?)
https://de.aliexpress.com/item/1005003252110774.html (Beok TGR85)
https://de.aliexpress.com/item/1005003575320865.html (AVATTO 1 w/o brightness adjustment & buzzer on/off?)

Maybe there are some preferences in terms of known issues/bugs?

Hi @anesterov ,
Unfortunately, it is impossible to confirm 100% whether a Tuya device (no matter where it was purchased from - AliExpress or Amazon) will work paired directly to HE or not. Even if it will look exactly the same as in the seller's site pictures, you may receive a different device (different Manufacturer ID). So, purchasing a Tuya platform device is always a risk.

1 Like

Hi @kkossev ,
Have you been able to work on this driver version yet? I am not sure if you did or not.
Thanks

1 Like

Not yet, the work on the Matter Bridge project takes all my free time.

Hopefully the thermostats will be supported also in a future Tuya Zigbee->Matter Bridges, so there will be no need to write new drivers for the new devices that will appear in the future.

2 Likes