javicalle

> but does it still matter if quirk you shared fixes that? Well, the proposed quirk will only dim your device between 1-1000 (aprox). If your device values can go...

Replace this: ```python lambda x: None if (value == 0xaaac or value == 0xaaab) else x ``` With: ```python lambda x: None if (x == 0xaaac or x == 0xaaab)...

Then you can try with; ```python lambda x: None if (x == 0xaaac or x == 0xaaab) else x/10 ```

Is the quirk from https://github.com/zigpy/zha-device-handlers/issues/1764#issuecomment-1272390644 the right version? Is there something else to fix? The quirk must be merged to the mainstream to be included in next versions of HA....

Which value returns the cluster if you try to read the attribute again? It returns the same you set?

Copy in your local quirk folder the current file: * https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts000x.py Add the imports statements at the beginning of the file. And add the new quirk at the bottom of...

All the info is in my previous comment: * https://github.com/zigpy/zha-device-handlers/issues/1780#issuecomment-1254814541

Your quirk signature doesn't match with yours device's one. It lacks the GPP endpoint. Maybe the `MmwRadarMotionGPP` would match yours device signature: https://github.com/zigpy/zha-device-handlers/blob/e9099ed26eb129e960934965cf5f0b1273b38e4f/zhaquirks/tuya/ts0601_motion.py#L391C7-L391C24 Or maybe you just could add the...

Replace your `ts0601_motion.py` with the current version from: https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts0601_motion.py (Make a backup if you have any other local quirk from this file!!!!) Search for the `MmwRadarMotionGPP` class and add there...

There are already 2 implementations for Tuya DIN metering devices. I would suggest you to try with the `HikingPowerMeter` one. There is a good guide to create your local quirk:...