Issues with Tuya TS0012 2 Gang

Hi!

I have several TS0012 Tuna 2 gang, TS001 1 gang and also TS0013 3 gang devices. All of them are "No Neutral"

On the TS0011 I have no issues, they load and also load the quirk as seen here:

{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZ3000_ji4araar",
"model": "TS0011",
"class": "zhaquirks.tuya.ts001x.Tuya_Single_No_N"
}

On the 2-gang I do not get them to lad and they are found by the coordinator (TubeZB) but it is not working, they either go back to the same status when turning the switch in Home Automation (but the light does not turn on or off) or they flick both switches as if it was a 1gang switch.

I have been searching and reading and also followed the post Issue #1301 #1301 but can't get this working.

Home Assistant:

Home Assistant 2022.11.1
Supervisor 2022.10.2
Operating System 9.3
Frontend 20221102.1 - latest

This is the diagnostic file for one of them:

zha-09251d82decb68e2a0992ae516deadf1-_TZ3000_jl7qyupf TS0012-6d0aa46e4ab6ecf655105a4e3af71b8f.json.txt

This part is something I don't get, it is not loading quirks

"data": {
"ieee": "REDACTED",
"nwk": 49942,
"manufacturer": "_TZ3000_jl7qyupf",
"model": "TS0012",
"name": "_TZ3000_jl7qyupf TS0012",
"quirk_applied": false,
"quirk_class": "zigpy.device.Device",

[javicalle]

If they are battery powered devices, the pairing process can be tricky. You must keep short pushing buttons until the pairing process ends to keep the device awake.

If not working, add the signature from the devices to see if they need a new quirk.

Hi!

The device adds and becomes nice and free in ZHA when adding them. Once they are added they do not work. They are switches in the light socket behind the light wall switch. No Neutral devices but powered devices.

[javicalle]

It seems to be another f****ng tuya variant.

The proposed quirk for the TS0012 would be:

class Tuya_Double_Var05(EnchantedDevice, TuyaSwitch):
    """Tuya 2 gang no neutral light switch (variant 05)."""

    signature = {
        # NodeDescriptor(
        #     logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, 
        #     frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, 
        #     maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, 
        #     descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, 
        #     *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False
        MODEL: "TS0012",
        ENDPOINTS: {
            1: {
                # "profile_id": 260,
                # "device_type": "0x0100",
                # "in_clusters": ["0x0000","0x0003","0x0004","0x0005","0x0006","0xe000","0xe001"],
                # "out_clusters": ["0x000a","0x0019"]
                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,
                    TuyaZBE000Cluster.cluster_id,
                    TuyaZBExternalSwitchTypeCluster.cluster_id,
                ],
                OUTPUT_CLUSTERS: [Ota.cluster_id, Time.cluster_id],
            },
            2: {
                # "profile_id": 260,
                # "device_type": "0x0100",
                # "in_clusters": ["0x0004","0x0005","0x0006"],
                # "out_clusters": []
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    OnOff.cluster_id,
                ],
                OUTPUT_CLUSTERS: [],
            },
        },
    }
    replacement = {
        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,
                    TuyaZBOnOffAttributeCluster,
                    TuyaZBE000Cluster,
                    TuyaZBExternalSwitchTypeCluster,
                ],
                OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
            },
            2: {
                PROFILE_ID: zha.PROFILE_ID,
                DEVICE_TYPE: zha.DeviceType.ON_OFF_LIGHT,
                INPUT_CLUSTERS: [
                    Groups.cluster_id,
                    Scenes.cluster_id,
                    TuyaZBOnOffAttributeCluster,
                ],
                OUTPUT_CLUSTERS: [],
            },
        },
    }

You will need to enable the local quirk in your instalation. There is a guide about enabling custom quirks:

• Editing (ZHA) quirks in a (HA) container or local. #693 (comment)

Copy in your local quirk folder the current ts001x.py file and put the suggested quirk in the bottom of file:

• https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts001x.py

Restart HA, remove and pair you device again.
Check that the device is loading the quirk and that the device signature has changed.

Hi!
I have enabled it and other devices pick it up but not the TS0012. It refuses to pick it up. I have tried the custom file in issue #1301 as well as the ts001x.py file you refer to but none of them works and the devices refuse to pick them up.

With the file you shared it picks up the quirk :-). Removed the device, restarted HA and then re-added the device.

Still not working, when flicking the switch in HA to on it goes off after a few seconds. Try both switches but the same. The lights do not turn on.

The other switch I have installed works different even though it is the same switch from the same vendor. When I flick one of the switches it flicks both of them. It sees it as if it would be a 1-gang switch even though it shows the two switches.

[javicalle]

Can we go one by one, please.

Share one device signature and behavior and we will try to fix it, but one by one.

And yes, I agree on the comment, another *****ng Tuna device. Useless but now I have more than 25 of them for the entire house and I have no neutral wire in the switch boxes. If not I would have thrown them out. I also have several of the switches in 2-way wiring so it limits my choices.

This one puts the switch back to what it was after a couple of seconds, any of the switches but treats them as two switches

Signature file:
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
}
},
"manufacturer": "_TZ3000_jl7qyupf",
"model": "TS0012",
"class": "ts0012.Tuya_Double_Var05"
}

[javicalle]

Not sure if I understand which is the device's behavior. But can be related to the Tuya EnchantedDevice.

I have updated the quirk signature. Just the class Tuya_Double_Var05(EnchantedDevice, TuyaSwitch): part.

Update the file, remove any __pycache__ folder and restart HA.

You will need to remove the device and pair it again.

Tried the steps you provided but no change.
And to explain the two different switches:
They are both 2 gang and TS0012 from the same vendor.
The one we are looking at first is the signature file I uploaded last. The behavior of that device is that whenever I flick any of the two gangs it just goes back to the previous state after a couple of seconds. The lights will not turn on.

The second device (TS0012) behaves different, it treats the two gangs as the same so which ever I flick it will flick both of them. The light do turn on but both do regardless which one I switch.

Hope this explains :-)

These are the signatures of the two devices I mentioned:

First device (that puts back the switch to the previous state after a few seconds):

{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
}
},
"manufacturer": "_TZ3000_jl7qyupf",
"model": "TS0012",
"class": "ts001x.Tuya_Double_Var05"
}

Second device (that treats the gangs as the same):

{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
}
},
"manufacturer": "_TZ3000_jl7qyupf",
"model": "TS0012",
"class": "ts001x.Tuya_Double_Var05"
}

[javicalle]

For its behavior, the second device will need the "Tuya spell".
This means that the device needs the updated version of the quirk. And once updated the code, you need to pair the device again (to apply the new code version).
Be sure that there is no __pycache__ folder before restart HA.