Hi, welcome to the forum!
Which zigbee integration are you using?
It’s this one, right? Futurehome TS0601_futurehome_thermostat control via MQTT | Zigbee2MQTT
Hi Nick4, thanks for the reply!
Sounds like the missing link. Can you treat me like an idiot nube (as that’s what I am); where do I find that integration and how do I install it?
I’m not really sure what ZigBee2MQTT is?
I mean, I do have some ZigBee devices connected already, I just don’t know whether it’s MQTT or not.
There are 2 different ways (integrations) in HA to use zigbee
- Zigbee Home Automation - Home Assistant (the official, default component which gets activated whey you add a zigbee coordinator)
- https://www.zigbee2mqtt.io/ (uses MQTT)
In Settings → Devices & services you will probably find the first one, right?
Yup, ZigBee Home Automation.
Have you tried deleting it and pairing again?
You might also have a look at this extensive guide Zigbee network optimization: a how-to guide for avoiding radio frequency interference
Sorry, I can’t figure out any of this. I’ve installed Mosquitto and now Zigbee2MQTT but I can’t get the configuration sorted or get it to run. I’ve now just had an error message and had to reset Zigbee Home Automation.
Part of my problem is that I don’t understand what it’s all supposed to be like.
My TS0601 had connected up easily enough in the first place I just don’t get any functionality. Surely it shouldn’t be this difficult?
I’ve tried removing and reconnecting the device. I still just get this:
No, you don’t need to remove ZHA, that’s the foundation to make zigbee work
I meant to delete the thermostat and pair it again.
zigbee2mqtt is an alternative to ZHA, you can’t have both!
Repairing it won’t help. You have a Tuya device, they don’t follow the Zigbee standard and each one has to have support added. I did a quick search of the zha quirks repo and I don’t see a quirk for the _TZE200_viy9ihs7.
You can submit a device support request at the zha quirks repo asking for someone to support it, but it’s not going to be a fast process since many of the Tuya devices require reverse engineering to support.
If you want to see the process to support a new Tuya device in ZHA, you can see this draft documentation.
I generally recommend not buying Tuya unless there is no other option and if you do want to use Tuya devices and are not comfortable building quirks, then make sure that they are already supported in ZHA.
According Futurehome TS0601_futurehome_thermostat control via MQTT | Zigbee2MQTT it seems to work in z2m.
Is this because they are/were using ZHA?
Yes, both z2m and ZHA require converting from the Tuya data points to function properly. Support is usually faster with z2m, they have more developers, and I assume a larger user base. If you can find the z2m converter, it’s not usually that hard to build out the ZHA quirk, but it’s not something I would suggest a brand new HA user attempt.
1 Like
Hi, thanks for the input. So the device was advertised as being a Zigbee device (good old Ebay!). Am I having problems because I’m using HA or would it not work with anything other than the Tuya app?
Looks like it’s not working with z2m yet either. Tuya zigbee thermostat [New device support]: · Issue #18589 · Koenkk/zigbee2mqtt
Well, zigbee isn’t zigbee.
All the info is in this thread why it’s not working.
That’s the thing with buying devices: always check that they work/are supported before buying them.
Also, diehards steer away from Tuya - me too!
I see there is a custom quirk here, you would need to install it. See official ZHA documentation for enabling custom quirks.
2 Likes
“Zigbee isn’t zigbee” doesn’t help me very much 
. At this stage I’m now trying to figure out if I’ve been mis-sold something or whether I’m just not using it in the way it was intended.
Like I said: All the info is in this thread why it’s not working.
Basically, yes, they are Zigbee, as in they use Zigbee to communicate. All proper Zigbee devices follow a standard outlined here Zigbee Cluster Library. This allows devices to work together and is how ZHA supports most devices, since we implement the ZCL standard, any conforming device just works. Tuya chose to not follow the ZCL, all of their commands are sent to a proprietary cluster using a proprietary format.
Even when we do add support, they will routinely release models with a different manufacturer code or move a data point to another id. Which means we have to add yet another quirk and someone had to capture the data point all over. Some devices even lock functionality and won’t respond unless a specific “spell” is transmitted on initial join.
All to say, don’t buy Tuya unless you have no other choice. There are other manufacturers that don’t follow the standards, but they are by far the worst.
2 Likes
You need to find and use an existing custom quirk to add, alternativly submit a device support request to ZHA Device Handlers and wait, or write your own quirk for ZHA to add, see ->, Zigbee Guide: How-to add/setup local custom ZHA Device Handlers (also known as ”quirks”) in the ZHA integration