zha-device-handlers: [BUG] TS0003 lights effect each other
Describe the bug I have a Tuya 3 gang with neutral light switch (TS0003 _TZ3000_odzoiovu) connect to zha. When I turn on/off 1 light, it effect all other lights too.
Expected behavior Every light should be independant
Device signature
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, 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=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0702",
"0x0b04",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
},
"3": {
"profile_id": 260,
"device_type": "0x0100",
"in_clusters": [
"0x0004",
"0x0005",
"0x0006"
],
"out_clusters": []
},
"242": {
"profile_id": 41440,
"device_type": "0x0061",
"in_clusters": [],
"out_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZ3000_odzoiovu",
"model": "TS0003",
"class": "zigpy.device.Device"
}
Diagnostic information
Paste the diagnostic information here.
Don't remove the extra line breaks outside the ``` marks.
Additional logs
Paste any additional debug logs here.
Don't remove the extra line breaks outside the ``` marks.
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (4 by maintainers)
Commits related to this issue
- Add the TS0003 and TS0004 metering devices And here comes the TS0003 and TS0004 devices with the metering cluster. Fixes: #1981 Fixes: #1982 — committed to javicalle/zha-device-handlers by javicalle 2 years ago
- Add the TS0003 and TS0004 metering devices (#1983) And here comes the TS0003 and TS0004 devices with the metering cluster. Fixes: #1981 Fixes: #1982 — committed to zigpy/zha-device-handlers by javicalle 2 years ago
I just did, and it fixed my problem. Looks like a recent HA update dealt with the bug. I only installed the switch 3 weeks ago.
I can guarantee 110% then i was not looking on every line but its looks its one of the added in zhaquirk ver 0.0.91 and you is running 0.0.90.
And you must doing the repairing or is the device not being feed and switching all gang then getting commands from ZHA.
Here’s the signature…
And I’ve attached the diagnostics.
This is all very new to me so if I haven’t given you it in the right format then let me know!
Appreciate your help!
zha-9f1ac0f5c53d56ed8a2efc4f23c6efee-_TZ3000_qewo8dlz TS0013-0eb4fb98cc0455a845e82517cca05885.json (1).txt
As I had 1MB of logs after few seconds from when I restarted HA, I’m attaching only the diff between before I turned on the switch and after
The device is loading the quirk. Verified it