Hiya, I’ve been bashing my head against this quirk for the last few weeks. It relates to the device handler request here: Github link (Not my original request but it’s for the same device.) I have commented there but trying here too - anywhere I can get either help, or a suggestion of where I should go next for help, would be great!
This is a Moes Tuya 6-gang mains scene switch, with 3 ‘true’ switch buttons and 3 scene-only buttons. It is supported by Zigbee2MQTT, but we have ZHA so I am trying to get it working there. There are several features which do not appear via ZHA by default - for example, ‘switch mode’ which controls whether a button is a switch or scene-only. They apparently do appear with Z2M.
I don’t have a Tuya gateway, so I’m not able to personally scan for the DPs, but I have been relying on this documentation: Tuya Dev site
It has a separate endpoint for each switch, with clusters duplicated across all/some of them. I also keep reading about and seeing in the code, reference to an 0xEF00 cluster which is apparently a Tuya standard for receiving commands? However there is no mention of this at the link above, or in my scans of the device.
I HAVE been able to get it so that the additional attributes (like ‘switch mode’) are readable and writable via the Manage Zigbee Device menu in HA.
Then via the v2 methods, I have been able to expose those attributes as entities, and they seem to read correctly when the device is paired. However, I am unable to change those attributes via those entities, and it’s driving me mad trying to figure out why. I’m guessing maybe it is trying to do that via EF00, which may not exist for this device?
If anyone may be able to help me, or point me in the right direction to get help, I’m happy to share what I’ve got so far!