Zigbee or Zigbee2mqtt or both

I purchased a USB zigbee adaptor: usb-Texas_Instruments_TI_CC2531_USB_CDC and a zigbee radiator valve: zhaquirks.tuya.ts0601_trv

I then installed the Zigbee integration in HA which recognises the controller and the controller recognises the TRV after pairing.

In the Loveday dashboard, I can add the card for the TRV and change the target temperature BUT I can not do that in an automation as I only seem to be able to set on-off, Mode but not the target temperature as that option is not given. What I would like to do is set that target temperature to e.g. 21 and the valve opens / closes based on the temperature in the room.

Reading up on this on this forum people mention zigbee2mqtt so I tried to install that but it fails to start. My questions:

  1. Do I need both the Zigbee integration AND Zigbee2mqtt or do I only need one of them?
  2. Any idea why I can’t set the target temperature in my automation? Do I need to change something in the TRV configuration?

Thank you

You can’t run both at the same time, because only one can talk to the USB stick. Zigbee2MQTT won’t be able to start while ZHA is running.

Thanks, @mobile.andrew.jones. That clears that up but leaves the second question. Is the fact that I can’t set a heat point in the TRV down to the TRV or is it down to my choice of ZHA versus Zigbee2MQTT?

if you can set it via UI then probably it works and you just have a bug in automation.

Thanks, @maxym but, I don’t believe I get as far as being able to create a bug :slight_smile: In the action section, I select the device and the only actions I can select are:

  • Turn On_Off
  • Toggle On_Off
  • Change HVAC Mode
  • Change Preset

That’s it… I can’t set the target temperature.

There’s more than just device actions. Your climate entity supports far more in the way of service calls, such as the climate.set_temperature service call.

1 Like

Thanks, @Tinkerer - I was not aware of that option. That seems to fix it. Thank you!

Device triggers are just wrappers for normal triggers, same for conditions, and the same for actions. Usually in fact the device side of things is a subset of what’s possible.

They’re convenient for those that don’t take the time to dive into the documentation, but so far not even close to complete replacements.

1 Like