How to debug zigbee quirk failure to identify my 2023 HY368 smart TRV?

Configuration Zigbee
1

Folks,

I have successfully built my HA Core setup using a SkyConnect gateway and around 30 Zigbee sensors/ switches/ smartplugs (along with some Bluetooth hygrometers).

I bought a set of Tuya Smart TRVs (they have this number under the cover: 202302210100019), which I believed (based on zigbee.blackadder.com) would connect to ZHA without issue.

However, it looks like they won’t connect to via the SkyConnect and need a Tuya gateway - very frustrating!

So my questions are:

  1. Can I add a Tuya gateway to my HA Core setup alongside the SkyConnect or will HA complain?
  2. Can I build a single Zigbee mesh or will I have two meshes?
  3. Will I need additional smartplugs on the Tuya mesh to reach all the TRVs around the house?!?

Your thoughts will be greatly appreciated.

David

2

Yes, you can

Yes, 2 meshes

Nobody knows, you will have to find out

3

Before you spend money, check that a custom quirk won’t enable them to connect to ZHA.

4

Thanks for your responses @francisp and @Stiltjack.

I hadn’t realised that ‘quirks’ even existed, so thanks for that tip, @Stiltjack.

I believe my TRVs are Hysen HY368 models (identical in appearance to this one on blackadder with Zigbee ID of TS0601/ _TZE200* ), and having enabled debug on ZHA, I can see that zhaquirks loads a long list tuya modules (inluding ts0601_trv/ ts0601_trv_sas/ ts0601_valve).

But then zigpy.quirks.registry checks quirks for ‘None None’ against a number of classes, including ts0201 (see below), but there’s no reference to checking any ts0601 classes, and fails with ‘Fail because endpoint list mismatch: {11, 13} {1}’

Oct 17 20:58:08 ubuntu2 hass[2500]: 2023-10-17 20:58:08.863 DEBUG (MainThread) [zigpy.quirks.registry] Considering <class 'zhaquirks.tuya.ts0201.MoesTemperatureHumidtySensorWithScreen'>
Oct 17 20:58:08 ubuntu2 hass[2500]: 2023-10-17 20:58:08.863 DEBUG (MainThread) [zigpy.quirks.registry] Fail because device_type mismatch on at least one endpoint

Any advice for how I can debug why the existing quirks are not identifying my device, so I can get appropriate changes made to the quirk library? Thanks!

UPDATE: Paired successfully once I had worked out how to put the TRV into pairing mode (the instructions are rubbish!). I thought that the slowly (1s) flash of the wifi icon represented pairing mode, but it needed to flash fast to be pairing. What a fiasco!

1 Like
5

Sorry to bring up this old thread, but how did you get this TRV in pairing mode? UPDATE, found it: https://www.youtube.com/watch?v=jAxy7shdYR0