I’m not a fan of deleting anything until I know what need the existing code.
Zigbee buttons are like being in a jungle, each manufacturer uses the clusters, values and attributes as they want to make their device work.
In Zwave it is much easier, manufacturers use the established command classes for the buttons, in fact the firmware libraries have default handlers that work in most cases or with small variations.
I have searched for the documentation for this device and it is totally different from all the existing ones in the stock driver.
I think only the battery information will help you.
This device is mainly designed to perform its functions by pairing directly with the zigbee devices to control, up to 30 bulbs, without the need to use a Hub using groups and TouchLink. Use 4 groups to send on, off and level commands
If you pair with the Hub it looks like it will send messages from endpoint 1 to 4 and I hope you can see in the CLI Log what cluster, attributes and values it uses.
So, don’t delete anything else for now and with the CLI:
-
Create a channel to assign the created driver
-
Package and assign the driver to the channel you created.
-
Install the driver on your Hub from the channel
-
Pair the device
-
Open a window to run the LogCat driver. This is a tutorial to capture CLI logs
Edge Driver or Device Handeler for a TUYA (Zemismart) Zigbee plug with energy mesurment capabilities - #18 by Mariano_Colmenarejo -
Press one by one on the 8 buttons and look for what messages the driver receives from the device
-
When you have that information, copy and paste the logs in an orderly manner and publish them and we will try to see what can be done.
This is a tutorial to modifiy and use custom drivers