javicalle

You have said that the scheduled was setted in the Tuya application, right? But as the quirk can not manage the scheduled for the device you need to disable it...

It seems to be the `TuyaPowerMeter` with the GPP cluster. Can you try with that quirk?: TuyaPowerMeter_GPP ```python class TuyaPowerMeter_GPP(TuyaSwitch): """Tuya power meter device.""" def __init__(self, *args, **kwargs): """Init device."""...

I think you need to remove the device from HA and re-pair again. If there are no improvements, the debug logs would be necessary to know what could be happening:...

You can try to grep the device UID `0x73d2`. Any warning of "no handler for..." o similar will be usefull.

I was expecting some of this: ``` 2022-06-25 15:19:25 DEBUG (MainThread) [zigpy.zcl] [0xC958:1:0xef00] Received ZCL frame: b'\t\x97\x02\x00\xdf\x06\x01\x00\x01\x00' 2022-06-25 15:19:25 DEBUG (MainThread) [zigpy.zcl] [0xC958:1:0xef00] Decoded ZCL frame header: ZCLHeader(frame_control=FrameControl(frame_type=, is_manufacturer_specific=0, is_reply=1,...

Can you pair the device again and attach the logs from the pairing process?

> > > > I tried the quirk but I got an error: > > ``` > File "/config/custom_zha_quirks/ts0601_din_power.py", line 3, in > class TuyaPowerMeter_GPP(TuyaSwitch): > NameError: name 'TuyaSwitch' is...

The `TuyaPowerMeter_GPP` quirk definitely doesn't work for your device. The quirk handles DPs: ``` TUYA_TOTAL_ENERGY_ATTR = 0x0211 TUYA_CURRENT_ATTR = 0x0212 TUYA_POWER_ATTR = 0x0213 TUYA_VOLTAGE_ATTR = 0x0214 TUYA_DIN_SWITCH_ATTR = 0x0101 ```...

If you want to try there is my proposal: ts0601_din_power_mcu.py ```python """Tuya Din Power Meter.""" from typing import Dict from zigpy.profiles import zha from zigpy.quirks import CustomDevice import zigpy.types as...

Device is reporting only DPs 1 and 16. 🤔 DP16 is some incremental value. Consumed power, uptime, ... DP1 is a boolean. Usually it is a sensor or a switch....