[APP][Pro] Tuya Zigbee App

[robertklep]

With TuYa you will never know if a device is supported or not until you have the actual device. Even devices from the same brand/model can have different internal identifiers that will cause Homey to not be able to recognise it.

The only way around that would be for Athom to implement proper generic Zigbee device support (like basically all other Zigbee implementations have), but so far they haven’t done so because they apparently still believe that specific device support (that is, through an app) is the best way.

[Brane_Brodnik]

Anyway, there is higher probability for already implemened brand/model to work then for not yet implemented one.

If Athom believes in specific device support to be the best way, they should much more proactively support all unknown devices to be implemented. I’m using Homey for about half a year and haven’t noticed progress in adding any devices so far. In this case, alternative generic Zigbee device support would at least possibly mean temporary solution for devices which many of us have bought but have no benefit of them.

Thank you and best regards.

[robertklep]

That’s what I’m trying to say: Athom don’t seem to believe in better generic device support.

At some point you should consider cutting your losses and migrate to a (much) better Zigbee implementation, like zigbee2mqtt, that integrates well with Homey.

[Brane_Brodnik]

But in case of addind zigbee2mqtt, I need to buy and establish one more eco-system with
new hardware, new knowledge, which would establish parallel zigbee mesh network in my house if I understand…? I wonder whether it is worth of it, or whether choosing Homey in this case was right decision or not?

[robertklep]

It’s a trade-off: wait for Homey to improve (which may be never) or pay for additional hardware for a good Zigbee network.

[staeff]

Just my two cents, sure homey should improve the generic device support, but tuya devices use many custom (non-standard) clusters which sometimes even between tuya devices aren’t 100% consistent. so I don’t think that such things could ever be part of the generic implementation and still an app (no matter if official or community) is needed and still I wouldn’t expect coverage for all devices that exist.

As for zigbee2mqtt, when I built my NAS I used the opportunity to switch to that, but I don’t think it’s realistic for non-technical people to do that. And even then the zigbee2mqtt app does have some issues which might be a deal breaker for some people (like not supporting duration for transitions or motion alarms not triggering zone activity).

[robertklep]

Sure, if you want to wait for Homey to improve, you can just choose that.

[Brane_Brodnik]

It might be breaking point for Homey, at least for me. After some additional waiting it could happen I would forget about Homey and try with another platform.

I would appreciate an official statement from Athom. Indirect part of it was what Johan Bendz published one week ago. Anyway, generic Zigbee device support from Athom would still be strongly needed supplement to Tuya Zigbee App solution from my point of experience so far with Homey. Trying to be a little patient before my next step.

[robertklep]

@Brane_Brodnik

I would appreciate an official statement from Athom

Athom don’t officially read this forum, and I doubt they will make any statements here about this.

[Brane_Brodnik]

If they are serious and ambitious company, they care about mood and opinions of their customers and they will find a way to get it. If not, I will have no reason to regret if I leave them.

[Peter_Kawa]

Because this forum is a bit all over the place, I’d suggest to first use the SEARCH button before saying things:

@Doekse

To anwser the first question: Tuya Zigbee devices will of course be available through Tuya Zigbee hubs, the same goes for BLE devices. We are also looking into creating an official Tuya Zigbee App but with the vast amount of different devices it’s really hard for us to deliver top notch quality and ensure a good user experience.

And in regards to your second question; Yes, the official Tuya App wil be supported by both Homey Cloud and Homey Pro

This unfortunately does not mean next month everything is up and running.
I’ve teamed up HA/zigbee2mqtt and Homey, and it makes a great system. Z2M is pure bliss!
Athom B.V. is just waaaay too slow with support for (new) devices.
Let me be clear, 3rd party developers are no party in this, it is Athom’s box, they sell it.
They should think of something to keep up with the market imho.

[Jerome_Revillard]

Dear all,

I would like to add a new temperature sensor… This is not my first driver BUT I still don’t understand clearly how to find the proper endpoint configuration from the interview.

The endpoint that I have in the interview is like this:

"endpointDescriptors": [
      {
        "endpointId": 1,
        "applicationProfileId": 260,
        "applicationDeviceId": 1026,
        "applicationDeviceVersion": 0,
        "_reserved1": 1,
        "inputClusters": [
          0,
          1,
          61184,
          1026,
          1029,
        ],
        "outputClusters": [
          25,
          10
        ]
      }
    ],

So, I decided to put in the driver.compose.json file this information:

"endpoints": {
      "1": {
        "clusters": [
          0,
          1,
          61184,
          1026,
          1029
        ],
        "bindings": [
          10,
          25
        ]
      }

but I still see in the logs plenty of line like this:

2024-08-09T07:31:39.512Z zigbee-clusters:endpoint ep: 1, cl: undefined (61184), error while handling frame cluster_unavailable {
  meta: { transId: 0, linkQuality: 78, dstEndpoint: 1, timestamp: 4989591 },
  frame: ZCLStandardHeader {
    frameControl: Bitmap [ clusterSpecific, directionToClient, disableDefaultResponse ],
    trxSequenceNumber: 1,
    cmdId: 2,
    data: <Buffer 00 02 04 02 00 04 00 00 00 14>
  }
}
2024-08-09T07:31:41.642Z zigbee-clusters:endpoint ep: 1, cl: time (10), error while handling frame binding_unavailable {
  meta: { transId: 0, linkQuality: 78, dstEndpoint: 1, timestamp: 4996245 },
  frame: ZCLStandardHeader {
    frameControl: Bitmap [  ],
    trxSequenceNumber: 2,
    cmdId: 0,
    data: <Buffer 07 00>
  }
}

Can someone explain to me what I’m missing here please ?

Best,
Jerome

[robertklep]

Probably better to post this on Github.

[Jerome_Revillard]

Ok I did it : Question about zigbee endpoint · Issue #912 · JohanBendz/com.tuya.zigbee · GitHub

Best
Jérôme

[Rick_znd]

Hello,
first of All THANKS Johan for the time you spend on maintaining this app.

I’m using a 4 gang remote MOES zigbee remote. It’s recognised by the app.
If i switch on a light, it immediatly turns off again.
Using a simple flow like WHEN BUTTON X clicks → than IKEA TRADFRI turn off or ON.
The lights change it’s status correctly but suddenly it changes again.

Manufacter ID: _TZ3000_wkai4ga5
Product ID: TS0044

[robertklep]

@Rick_znd

Using a simple flow like WHEN BUTTON X clicks → than IKEA TRADFRI turn off or ON.
The lights change it’s status correctly but suddenly it changes again.

You’re going to have to do a bit more investigating to see why this happens. For instance, if you make a flow “WHEN BUTTON X clicks → then send yourself a push notification”, do you receive the notification once, or twice?

[Rick_znd]

thanks Robert.
Tried and it gets me 2 notifications with one single click

[robertklep]

Does the card provide some way of finding out the type of click? Like single, double, long, etc. If so, perhaps it triggers twice with a different type, and you can filter out the wrong one with a Logic card.

[Rick_znd]

i can choose single or double click but i can’t understand on how to filter …

[robertklep]

So for “Upper Left Button: 1 Click” you get two notifications?