tuya unused cluster then using tuya MCU command (DP) and cluster mess on Zigbee devices.

[MattWestb]

All implanted devices that is using tuya MCU commands (=DPs) is (for the moment) using 2 different Zigbee modules that is TYST11:

    signature = {
        #  endpoint=1 profile=260 device_type=0 device_version=0 input_clusters=[0, 3]
        #  output_clusters=[3, 25]>
        MODELS_INFO: [
            ("_TYST11_jeaxp72v", "eaxp72v"),
            ("_TYST11_kfvq6avy", "fvq6avy"),
            ("_TYST11_zivfvd7h", "ivfvd7h"),
        ],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [Basic.cluster_id, Identify.cluster_id],
                OUTPUT_CLUSTERS: [Identify.cluster_id, Ota.cluster_id],
            }
        },
    }

(its have the input TuyaManufClusterAttributes.cluster hidden) and

    signature = {
        #  endpoint=1 profile=260 device_type=81 device_version=0 input_clusters=[0, 4, 5, 61184]
        #  output_clusters=[10, 25]>
        MODELS_INFO: [
            ("_TZE200_kfvq6avy", "TS0601"),
            ("_TZE200_zivfvd7h", "TS0601"),
        ],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaManufClusterAttributes.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            }
        },
    }

(example from valve.py)

I think easiest is saying its the "TS0601 family" and is one ON_OFF_SWITCH or SMART_PLUG with some basic cluster and the tuya cluster for tuya commands and can having more used or unused cluster on the endpoint.

Then "decoding" the tuya DPs and adding the new virtual tuya function clusters all ts0601 quirks still having the not used Groups.cluster_id and Scenes.cluster_id,

Basic and Identify cluster (then its implanted) shall being left as both is moderate in ZCL.
Time cluster i dont knowing but i think most ts0601 MCU devices is getting the time from the DP commands and is not needed but the OTA can being used for firmware upgrading of the Zigbee module in the future so i think it shall being left.

I think in the long run we shall deleting the time, group and scene cluster in the replace then its not making any good and can making problems for the user in the future then ZHA is (hopefully) starting using scenes and advance us of groups with scenes.

I have only tuya TRVs with TYST11 module so i cant testing if its good or bad but i think its one "policy question" how to implanting tuya ts0061 device quirks and not letting "junk" in the system that can making problems in the future.

Guidelines pleas !!

Mvh MW

[MattWestb]

Also one interesting tuya device:

       MODEL: "TS004F",
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.DIMMER_SWITCH,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    PowerConfiguration.cluster_id,
                    Identify.cluster_id,
                    Groups.cluster_id,
                    OnOff.cluster_id,
                    LightLink.cluster_id,
                ],
                OUTPUT_CLUSTERS: [
                    Ota.cluster_id,
                    Time.cluster_id,
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                    LevelControl.cluster_id,
                    LightLink.cluster_id,
                ],
            }
        },
    }

Its one dimmer switch and can not using group and OnOff cluster as input.
If not deleting the OnOff clsuter the user is getting one not working switch in the GUI that is making problem and no sin.

Some tuya switches (and remotes) have one OnOff in cluster for the back light of the switch and can dim it in the night but its coming later for tuya "normal" zigbee device (i dont knowing but as its one tzya its very likely is using command 0-2 (on/off/toggle) for dimming the panel lights as they is using on there "scene switches" for "scene commands (short double and long pressing)).

[MattWestb]

The TS004F is not working then doing bindings that shall working then its one Zigbee controlling device.
But by adding Group in cluster ZHA is exposing is on group manager and its possible adding as one light in groups and its working OK.

[MattWestb]

All tuya TS004X device is "remotes" (in Zigbee controllers) and all looks the same and is having very strange cluster layout like this (TS0044):

        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    PowerConfiguration.cluster_id,
                    OnOff.cluster_id,
                    Time.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Ota.cluster_id],
            },
            2: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [
                    PowerConfiguration.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [],
            },
            3: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [
                    PowerConfiguration.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [],
            },
            4: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [
                    PowerConfiguration.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [],
            },
        },
    }

And all cluster is putted as in cluster in replace (not time then its deleted for getting the device working OK).

The problem is that ZHA GUI is getting not working switches on the device card and they is only making problem.

I finding its better putting the OnOff cluster as the out clusters and only adding the PowerConfiguration cluster on the EP 1.

Then the "switch" is being exposed ad one "normal" switch that is sending events and hopefully is having one battery sensor and no extra devices that is only making problems.

Back side is that its not possible adding the "switches" in ZHA groups (that is not working then its not lights) and can being possible they is being available for binding (depends of the device type i think) but they is very likely not supporting group bindings then its no light switches.

[MattWestb]

Zigbee modules used for DP (ts0601) devices

Found but it can being more types out there:

# TYST11 Zigbee module with hidden tuya cluster type OnOff Light.

        MODELS_INFO: [("_TYST11_wmcdj3aq", "mcdj3aq")], 
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Identify.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Ota.cluster_id],
            }
        },
    }


# TYST11 Zigbee module with hidden tuya cluster type OnOff switch.

        MODELS_INFO: [("_TYST11_i5j6ifxj", "5j6ifxj"), ("_TYST11_7hfcudw5", "hfcudw5")],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_SWITCH,
                INPUT_CLUSTERS: [Basic.cluster_id, Identify.cluster_id],
                OUTPUT_CLUSTERS: [Identify.cluster_id, Ota.cluster_id],
            }
        },
    }


# TZE200 Time as in cluster.

        MODELS_INFO: [("_TZE200_7tdtqgwv", "TS0601")],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    Time.cluster_id,
                    TuyaManufCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Ota.cluster_id],
            }
        },
    }


# TZE200 Time as out cluster.

        MODELS_INFO: [("_TZE200_oisqyl4o", "TS0601")],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaManufCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            }
        },
    }

# TZE200 Time as out cluster plus ZGPP.

        MODELS_INFO: [
            ("_TZE200_ryfmq5rl", "TS0601"),
        ],
        ENDPOINTS: {
            1: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
                INPUT_CLUSTERS: [
                    Basic.cluster_id,
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaCO2ManufCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            242: {
                # <SimpleDescriptor endpoint=242 profile=41440 device_type=97
                # input_clusters=[]
                # output_clusters=[33]
                PROFILE_ID: 41440,
                DEVICE_TYPE: 97,
                INPUT_CLUSTERS: [],
                OUTPUT_CLUSTERS: [GreenPowerProxy.cluster_id],
            },
        },
    }

By Zigbee standard shall all End points having basic is in and Identify as in and can having Identify aso out.
Then tuya DP devices only using the tuya cluster i think is better and safe not putting Group, Scene and Time cluster in the replacment then they dont have any fuction in the Zigbee module and is making ZHA trying using them.
OTA can being good if finding the right firmware feel for the Zigbee mudule but its dangerus as Z2M have bricking many device with flace firmware.

[MattWestb]

@jacekk015 if you need the endpoint configs of ts0601 devices i have potting all i have finding in quirks here so you can doing one test quirk easier if you like.