[Device Support Request] TS011F MS-104BZ (Zigbee + RF) _TZ3000_pmz6mjyu
See original GitHub issueIs your feature request related to a problem? Please describe. Clusters 0xE000 and 0xE001 are logged as warnings and can’t be accessed:
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57344
2022-01-07 18:31:37 WARNING (MainThread) [zigpy.zcl] Unknown cluster 57345
Access to 0xE001 is needed to configure Rocker / Reset switch behavior.
Describe the solution you’d like Force Rocker switch behavior to be able to toggle both physical switches at the same time. Right now, if I press both physical switches at the same time only one light is toggled and the other one is ignored.
Device signature - this can be acquired by removing the device from ZHA and pairing it again from the add devices screen. Be sure to add the entire content of the log panel after pairing the device to a code block below this line.
{
"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=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, 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": "0x010a",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": [
"0x000a",
"0x0019"
]
},
"2": {
"profile_id": 260,
"device_type": "0x010a",
"in_clusters": [
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0xe000",
"0xe001"
],
"out_clusters": []
},
"242": {
"profile_id": 41440,
"device_type": "0x0061",
"in_clusters": [],
"out_clusters": [
"0x0021"
]
}
},
"manufacturer": "_TZ3000_pmz6mjyu",
"model": "TS011F",
"class": "zigpy.device.Device"
}
Additional context My device seems to be an updated version of MS-104BZ with both Rocker and Reset switches support. https://www.moeshouse.com/products/2-gang-tuya-zigbee-3-0-smart-light-switch-module-2mqtt-setup-available
Issue Analytics
- State:
- Created 2 years ago
- Comments:28 (17 by maintainers)
Top GitHub Comments
Great !! And the quirk is more “tuya standard” by naming and also have the original device types so not getting problem later with devices and must redoing then and braking automation for users.
Thanks for good testing and finding the bad copy and past coding i was doing !!
OPS !! I was not seen that your device is one MAIN_POWER_OUTLET i fixing it !!