javicalle

> I think you saw it inverted.... the incremental is DP1 and the boolean DP16. Aren't they? Yes, they are 🤦🏻‍♂️ It can't be 2 DP mapped to the same...

This is a curious device. I think the normal switches (4 left) should be controlled by the `TuyaQuadrupleSwitchTO` quirk. You can enable the local quirks and copy the current `ts0601_switch.py`...

Look at the logs for any info from your device (check the Nwk value for your device in the "Zigbee info" option).

Keep the breaklines: ```` LOG ``` 2022-09-27 21:16:29.316 DEBUG (MainThread) [zigpy.appdb] [0x1496:1:0x0000] Attribute id: 4 value: _TZE200_fm5yck8a 2022-09-27 21:16:29.316 DEBUG (MainThread) [zigpy.appdb] [0x1496:1:0x0000] Attribute id: 5 value: TS0601 2022-09-27 21:16:29.929...

Quick and dirty alternative: 1. restore the file version (or remove the `_TZE200_fm5yck8a` line) 2. add at the end of the [`ts0601_switch.py`](https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts0601_switch.py) file this classes: AtlanticSwitchManufCluster ```python class AtlanticSwitchManufCluster(MoesSwitchManufCluster): """On/Off...

> As they are designed for scenes would it be possible to set them for events instead of entities? Yes, that is the intention. I'll come back with some update....

From your logs I can see that HA tries to write the attribute and the device respond with a success: ``` 2022-09-29 20:31:09.653 DEBUG (MainThread) [zigpy.zcl] [0xB4E7:1:0xef00] write_attributes --> record:...

I do not see any reports from the device apart from those already known (1, 2, 19, 20, 21, 22). Assuming that it is not possible to control the state...

> there is new switch, which does not react and if I try to turn it on, it automatically turns off. My fault. Fixed in the code. Just remove the...

Without any information it is difficult to try to help you. Under the `MmwRadarMotion` quirk, attempts have been made to adjust multiple sensors that I don't think are compatible with...