Describe the bug
When pairing a Tuya 3-button scene remote TS0043 with manufacturer ID _TZ3000_famkxci2, Homey pairs it as a "Generic Zigbee Device" instead of matching it with the button_wireless_3 driver.
To Reproduce
Steps to reproduce the behavior:
- Go to Homey App > Devices > Add Device.
- Search for 'Tuya Zigbee' and select 'Wireless 3-Button Switch' (or start Zigbee pairing).
- Put the TS0043 remote in pairing mode (hold button for 5 seconds until LED blinks).
- See error: Device is paired as "Generic Zigbee Device" without any capabilities/buttons.
Expected behavior
The TS0043 (_TZ3000_famkxci2) remote should be recognized by the button_wireless_3 driver with battery measurement and button press flow triggers.
App and Homey version
• What Homey version are you running? Homey Pro (Early 2023)
• What version of Homey firmware do you use? 13.5.0
• What version of the Universal Tuya App are you using? v9.0.1086
Screenshots
Additional context
Root cause analysis of driver.compose.json for button_wireless_3:
The driver's endpoints.1.clusters definition includes Security/Alarm clusters (1280 / 1281 IAS Zone). Since the TS0043 hardware lacks these clusters, Homey's Zigbee signature matching algorithm fails and falls back to Generic Zigbee Device.
Removing clusters 1280, 1281, and 61184 from the endpoints configuration in driver.compose.json resolves the matching issue.
Describe the bug
When pairing a Tuya 3-button scene remote TS0043 with manufacturer ID _TZ3000_famkxci2, Homey pairs it as a "Generic Zigbee Device" instead of matching it with the button_wireless_3 driver.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The TS0043 (_TZ3000_famkxci2) remote should be recognized by the button_wireless_3 driver with battery measurement and button press flow triggers.
App and Homey version
• What Homey version are you running? Homey Pro (Early 2023)
• What version of Homey firmware do you use? 13.5.0
• What version of the Universal Tuya App are you using? v9.0.1086
Screenshots
Additional context
Root cause analysis of driver.compose.json for button_wireless_3:
The driver's endpoints.1.clusters definition includes Security/Alarm clusters (1280 / 1281 IAS Zone). Since the TS0043 hardware lacks these clusters, Homey's Zigbee signature matching algorithm fails and falls back to Generic Zigbee Device.
Removing clusters 1280, 1281, and 61184 from the endpoints configuration in driver.compose.json resolves the matching issue.