zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

TuYa plug doesn't connect properly, then fails all communication attempts.

Open ThatDeltaGuy opened this issue 1 year ago • 1 comments

What happened?

I have 5 Zignito tuya plugs(TS011F, _TZ3000_okaz9tjs, Smart plug (with power monitoring)) from ajax online, they've all worked with zha for years. Recently, I've decided to move to z2m, but these plugs don't want to work. After pairing, and configuring the blue light continues to flash and any attempt to turn on/off etc is met with failed (no response received) errors.

The zha config can be found here: https://github.com/zigpy/zha-device-handlers/blob/dev/zhaquirks/tuya/ts011f_plug.py on line 1050, and what I believe is the z2m config here: https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/src/devices/tuya.ts on line 3345, but I don't know enough about how the system works to work out if there are any differences.

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.35.0

Adapter firmware version

0x264d0900

Adapter

ConBee3

Debug log

Publish 'set' 'state' to '0x70b3d52b60011a74' failed: 'Error: Command 0x70b3d52b60011a74/1 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (46))' Publish 'set' 'power_outage_memory' to '0x70b3d52b60011a74' failed: 'Error: Write 0x70b3d52b60011a74/1 genOnOff({"moesStartUpOnOff":2}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (no response received (49))' log.txt

ThatDeltaGuy avatar Jan 02 '24 16:01 ThatDeltaGuy

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days

github-actions[bot] avatar Jul 01 '24 00:07 github-actions[bot]