javicalle

> maybe the missing entity is old and can be removed? Yes, probably it is. Please, look at the logs for any device related errors.

You should be able to set the `sensitivity_level` and `keep_time` attributes from the `PirMotionManufCluster` cluster. Accepted values would be: ```python class SensitivityLevel(t.enum8): """Sensitivity level enum.""" LOW = 0x00 MEDIUM =...

The device is reporting just a boolean value at DP_1. We can implement it like an IasZone Motion_Sensor or like an OccupancySensing, but not both. According to the manufacturer, it...

The IasZone alternative woud be like: 1. add a new `MotionSensorCluster` class: ```python class MotionSensorCluster(IasZone, TuyaLocalCluster): """Tuya Motion_Sensor Sensor.""" _CONSTANT_ATTRIBUTES = {ZONE_TYPE: IasZone.ZoneType.Motion_Sensor} ``` 2. replace the `dp_to_attribute` mapping in...

It has been working before? It is the device loading the quirk? Any relevant info in your logs? I would try to pair the device again.

Without having looked in depth, I think the main handicap will be managing the `Direction: Client to Server` part. If I'm not mistaken, the implementation is prepared to handle easily...

Another round to check the repeated responses. If I have understood correctly the device expects the response to the commands to have the direction reversed. I think it would be...

I know you are doing a lots of tests and changes and I don't want to generate any additional noise to them. There is no hurry, but when you test...

Ummm, so the problem is not in the command part. (I'm having a really hard time understanding all the messaging part) Let's attack the reporting part. We can try to...

No rush at all. (Too many open fronts...) No easy way to invert the DR direction, so my hope is that inverting the direction in the device report will also...