javicalle

New version not released yet. It will be included in HA 2024.2

Hi @vinzent, thanks for the contribution. Nice implementation of a v2 quirk. Without a Tuya cluster (`0xEF00`) you can't read the datapoints from the device. This seems like a straight...

Maybe we can sort the `MODELS_INFO` array: ```python MODELS_INFO: [ ("_TZE200_9yapgbuv", "TS0601"), ("_TZE204_9yapgbuv", "TS0601"), ("_TZE200_cirvgep4", "TS0601"), ("_TZE200_upagmta9", "TS0601"), ("_TZE204_upagmta9", "TS0601"), ("_TZE200_utkemkbs", "TS0601"), ("_TZE204_utkemkbs", "TS0601"), ("_TZE200_yjjdcqsq", "TS0601"), ("_TZE204_yjjdcqsq", "TS0601"), ], ```

It seems that device triggers 3 events for every button press: * https://github.com/zigpy/zha-device-handlers/pull/1400#issue-1153382712 I'm not sure why it behaves that way, but I'll suggest this change to the quirk: ts0211.py...

Not until there is confirmation that the quirk works as it should. Were you able to validate the quirk on your device?

Please attach the debug logs for button and tamper indicating the sequence of events. You can do it by enabling the debug logs from the device view.

Sorry for the late reply. I can't test myself but maybe you can just configure it as a `binary_sensor` like this: ``` binary_sensor: - platform: rflink devices: oregontemp_0d93_bat: name: Weather...

Ummm, I see the reason now: `binary_sensor` only responds to "command" events and not to "sensor" events like these: ``` 2024-11-08 21:45:48.149 DEBUG (MainThread) [homeassistant.components.rflink] event of type sensor: {'id':...