javicalle

😓 This is turning out to be more difficult than expected. Next proposal: ts0601_switch.py ```python class OnOffEventsCluster(EventableCluster, TuyaOnOff): """OnOffEventsCluster: fire events corresponding to press type.""" class AtlanticSwitchManufCluster(TuyaOnOffManufCluster): """On/Off Tuya cluster...

The device still complains about the DP1 and DP2... Can you double check that `__pycache__` folder has been deleted and the quirk is the one from https://github.com/zigpy/zha-device-handlers/issues/1785#issuecomment-1335450597? If checks are...

No the imports would not be a problem. And now we have new neighbours in the block... ``` 2022-12-06 22:57:14.295 DEBUG (MainThread) [zigpy.zcl] [0x52CD:1:0xef00] No datapoint handler for TuyaDatapointData(dp=25, data=TuyaData(dp_type=,...

Reported as fixed. Please, reopen if the problem persists.

Someone able to test this fix?: * https://github.com/zigpy/zha-device-handlers/issues/1554#issuecomment-1345426616

Thanks for the offer but the code would have errors, so better if can test it someone able to progress through the errors.

You need to match the signature from your device with the one in the quirk. Your's device signature for endpoint 1 is: ```python "1": { "profile_id": 260, "device_type": "0x0100", "in_clusters":...

Quick & dirty proposal: Add the `EventableOnOffCluster` class: ```python class EventableOnOffCluster(EventableCluster, OnOff): """Eventable OnOff cluster: fire events corresponding to press type.""" ``` Use it in the replacement part in sustitution...

Z2M implementation is here: * https://github.com/Koenkk/zigbee-herdsman-converters/blob/b06b48efee3df32a87bfa1b7f6fb2f00bda7aa15/devices/xiaomi.js#L2736-L2767 Seems being using `4447` as manufacturer code (for using it in the decouple command). Also seems that device is using a custom cluster or...

> I still can't get the device decoupled, that's a work in progress. Not sure which one is the `aqaraOpple` cluster in Z2M, but seems that the decouple attribute is...