Tuya TS011F (TZ3000_typdpbpg) powers off

[phoxy84]

What happened?

When I use the device they shut down suddenly. This happens maybe once every one or two days. Don't know if it is a Z2M issue or a problem with the plug.

I have four of them, all have the same problem.

I made an automation to power the device on automatically but that cannot be the solution :)

What did you expect to happen?

The plug just stays on.

How to reproduce it (minimal and precise)

I don't know. Just power on the device and wait.

Zigbee2MQTT version

1.23.0-dev commit

Adapter firmware version

20211217

Adapter

zzh

Debug log

debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:30: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.36,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":79,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":238}' debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:30: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.36,"energy":2.51,"indicator_mode":null,"linkquality":65,"power":79,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":238}' debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":4}' from endpoint 1 with groupID 0 debug 2022-02-28 10:58:30: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":4}' debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":0}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:30: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.36,"energy":2.51,"indicator_mode":null,"linkquality":69,"power":79,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}' debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":0}' from endpoint 1 with groupID 0 debug 2022-02-28 10:58:30: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":0}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:30: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.36,"energy":2.51,"indicator_mode":null,"linkquality":69,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}' info 2022-02-28 10:58:30: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":69,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}' debug 2022-02-28 10:58:35: Received MQTT message on 'zigbee2mqtt/iMac/set' with data 'ON' debug 2022-02-28 10:58:35: Publishing 'set' 'state' to 'iMac' info 2022-02-28 10:58:35: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":0}' debug 2022-02-28 10:58:35: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:35: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":0}' debug 2022-02-28 10:58:36: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:36: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}' debug 2022-02-28 10:58:37: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":0}' from endpoint 1 with groupID 0 debug 2022-02-28 10:58:37: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":0}' debug 2022-02-28 10:58:37: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":241}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:37: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:58:41: Received MQTT message on 'zigbee2mqtt/iMac/set' with data 'ON' debug 2022-02-28 10:58:41: Publishing 'set' 'state' to 'iMac' info 2022-02-28 10:58:41: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:58:42: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:42: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:58:56: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":39}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:56: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0,"energy":2.51,"indicator_mode":null,"linkquality":51,"power":39,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:58:59: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":171}' from endpoint 1 with groupID 0 info 2022-02-28 10:58:59: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.17,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":39,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:59:01: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":95}' from endpoint 1 with groupID 0 info 2022-02-28 10:59:01: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.17,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":95,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:59:03: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":392}' from endpoint 1 with groupID 0 info 2022-02-28 10:59:03: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.39,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":95,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:59:10: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":107}' from endpoint 1 with groupID 0 info 2022-02-28 10:59:10: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.39,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":107,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}' debug 2022-02-28 10:59:12: Received Zigbee message from 'iMac', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":458}' from endpoint 1 with groupID 0 info 2022-02-28 10:59:12: MQTT publish: topic 'zigbee2mqtt/iMac', payload '{"child_lock":null,"current":0.46,"energy":2.51,"indicator_mode":null,"linkquality":47,"power":107,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":241}'

[phoxy84]

@RHAD1969 all sockets were updated to 1.0.5 firmware but i noticed it`s not reporting power consumption at all:(

I think they work with polling, is it a plug_3, or (still) plug_1?

See here

[RHAD1969]

@phoxy84 It reports as a JLT1 on my smart-bridge10 and it is reporting itself as a TS011F_plug_1 on Zigbee2MQTT in Home Assistant

[phoxy84]

@phoxy84 It reports as a JLT1 on my smart-bridge10 and it is reporting itself as a TS011F_plug_1 on Zigbee2MQTT

Sorry, don't know then. Did you open an issue already on that problem?

[jar87]

@phoxy84 in my caase plug_1 is still plug_1;)

[jar87]

Hopefully future update of z2m will solve problem.

[RHAD1969]

@phoxy84

Sorry, don't know then. Did you open an issue already on that problem?

I've opened an issue. The responded with obvious answers. They want the ID of my device to push an update. But my device is not connected to a Tuya bridge and therefore not visible on their platform.

I just connected one plug using my smart-bridge10 and connected my 'always on' laserprinter to the plug. I'm curious if I get power cut offs using this config. I hope to eliminate Home Assistant / Zigbee2Mqt as the cause of this issue.

[durkimat]

Ok, got a couple hooked up to a tuya ZigBee hub. They're on v1.04 and there's no update. They're still turning off. In the logs for one or turned off twice in a row, it wasn't off the second time, it still triggered the log event.

[RHAD1969]

Tuya just got back at me via Whatsapp, so they seems to take the issue seriously. I pointed them also to this discussion.

I'll keep you posted.

[jar87]

Hopefully they will fix it asap :)

[navycrow]

Strange thing. I paired my 4 sockets on tuya bridge 8 days ago. The firmware was 1.0.10. In despite, they continue to cut off once or twice a day. On wednesday, i made a new request to the seller and sent the virtual ids of the sockets (found in Tuya Smart Life app). Since wednesday, no sockets had cut off ???? !!!!! However the firmware is still 1.0.10. Weird !!

[phoxy84]

Tuya just got back at me via Whatsapp, so they seems to take the issue seriously. I'll keep you posted.

That sounds great, hope they fix it.

Strange thing. I paired my 4 sockets on tuya bridge 8 days ago. The firmware was 1.0.10. In despite, they continue to cut off once or twice a day. On wednesday, i made a new request to the seller and sent the virtual ids of the sockets (found in Tuya Smart Life app). Since wednesday, no sockets had cut off ???? !!!!! However the firmware is still 1.0.10. Weird !!

Well, I use four of them and they don't shut down every day, since last week: 1 turned of twice (cordless vacuum cleaner) 1 turned of four times (pc monitor) 1 turned of five times (kettle) 1 tuned of twice (floor heating pump)

The last is I think the most used one. The kettle has the biggest spike in watts.

[navycrow]

Well, less then one hour after my latest post, one socket cut off again. So finally : not solved at all. I believed it :(

[bolidesoft]

It is either hardware or firmware issue of these sockets. Here is the chart of "electrical_measurement rms_voltage" sensor of my TS011F. See those sudden voltage drops? They coincide with the sudden power offs. Something happens inside for a second and it turns off the relay. The next second all the parameters are OK again but it remains powered off. My guess - it is hardware problem and this is a bad news...

[Jhonattan-Souza]

My guess is the same, it is hardware problem

[Scaaro]

I think the problem is in Fw. I have 3 sockets, one reports as plug_3 and the other two as plug_1.

The sockets labeled plug_1 are randomly shutting down and the socket labeled plug_3 was working fine. It was also the only one that had the OTA update available. After the FW update, the socket is now labeled plug_1 and shows the same problem. Unfortunately I don't know the Fw version not shown in zigbee2mqtt.

[durkimat]

I have exactly the same - one of the five I have shows as plug_1 and is completely stable. I haven't tried moving to tuya hub and updating and have no intentions of moving it! All 4 plug_3 have problems.

[navycrow]

scaaro said plug_1 are defective and no plug_3 durkimat said plug_3 are defective and no plug_1 sadrov said 1 plug_3 is defective and not the 3 others me, i said all my 4 plug_1 are defective. So my conclusion : both plug_3 and plug_1 can be defective. Now we need to know the firmware version for the defective ones and the firmwares of good ones to know if it's firmware relative. Mine are plug_1 / firmware 1.0.10

[phoxy84]

I have 8 (4 plug_3, 4 plug_1) but in z2m no firmware version. I ordered a Tuya bridge. If I have any info, I will post.

[sadrov]

same here, I use z2m exclusively. Is there a way to figure out the firmware version through z2m?

[RHAD1969]

Bad news people:

Although this is a widespread problem, Tuya redirect me to my supplier and blaming it on my gateway. But I use two different gateways and you have also a lot of issues.

[RHAD1969]

The reply from Tuya:

to be honest, as we are a B2B platform, we don't have any store on mediamarket or amazon, we don't sell smart devices directly, all the suppliers we cooperate  all  have stores on our website

https://expo.tuya.com/

if there is any problem with our app, then all the users will reflect this question. but now I haven't heard of it , so I think you can go to the supplier you bought from to ask for the help

Received from Vincent +86 173 0091 8147 using WhatsApp

[kamilkobak]

I have the same problem :/

[durkimat]

The 1 of 5 of my plugs that is not turning off randomly appears differently in the tuya ZigBee Gateway. It immediately suggests a v1.05 upgrade, though I can't find the current version anywhere! The others all show v1.04 with no updates available. The model number of this plug is WGH-JLCZ02 and on the plug is labelled WHD09. I will try and get model information from the others later. I've also just realised one of the others had the washing machine plugged in and working so maybe I have 2 that are ok. Washer is running so I can't check!

[meganiekje]

I have 2 of those Tuya TS011F plug_1 devices. They also switch off randomly. So I decided to open one of them, to see if I can find a design flaw. The plugs are glued, so you have to break them open: look here how to: https://www.instructables.com/Hardware-and-Software-Hack-Smart-Devices-Tuya-and-/ Thank you very much Wim3D ;)) WARNING : THE DEVICE HAS 300 VOLT INSIDE. DO NOT DO THIS, IF YOU DO NOT KNOW ABOUT ELECTRONICS !!!!!! Inside I see a very nice circuit, with good quality soldering, and solid components. When I checked the power supply part of the electronics, I see a PB2525 High voltage regulator, that is used on a 'unconventional' way to produce 4.8 Volts DC. This goes into a 10 uF capacitor. This voltage will be needed to power the relay. Then they use a 7110 low voltage regulator in a abnormal way, to make 3.3 Volts. This 3.3 V is used to power a BL0937 (Single Phase Energy Meter IC) The 3.3Volt is not stabilized at all, but the holes for a capacitor are there, only it is not mounted. If I look at the graph from @BolideSoft, it could be the BL0937 that causes the problems, if it has an unstable power supply. I put a 16V 64uF elco on the PCB, to stabilize the 3.3 Volts, lets see what happens...... I also bridged the relay, so the output power is alway on. I use the plug only for monitoring, not for switching. I keep you posted !!!

[meganiekje]

The 64uF capacitor on the 3.3v does not help :(( The plug still powers off.

[Kedryn]

Just to let you know, i have the same random power off problem with my 3 tuya plugs TS011F_plug_1. All of 3 randomly powering off. And it's not a matter of signal, because i moved them near the coordiantor for testing, but it's still happening.

[NicoLouis-be]

i have 2 of them. I did buy them togheter and only one of them has the random power off Type ts011f_plug Connection through zigbee usb dongle, and did nothing to the firmware.

[diegogarciadev]

I had the same problem with 4 power plugs, I have bought a tuya zigbee gateway and connecting plug to it the problem has desappear... After one day no more disconnections. But with the tuya integration in HA you don't see the power momitoring, only voltage, current and power

[meganiekje]

@diegogarciadev : maybe, tuya does re-send the 'ON' command frequently, to keep the plug active. I have made a rule that does just that, every 6 hours. Lets see if that helps...

[diegogarciadev]

@diegogarciadev : maybe, tuya does re-send the 'ON' command frequently, to keep the plug active. I have made a rule that does just that, every 6 hours. Lets see if that helps...

I thought about that, maybe it's better to add an automation to power on when power off, if is quik enough it could work, if not maybe we have to send the power on order every 5 minutes. For me sometimes the plug has powered off in 1 hour.

[phoxy84]

@diegogarciadev : maybe, tuya does re-send the 'ON' command frequently, to keep the plug active. I have made a rule that does just that, every 6 hours. Lets see if that helps...

I thought about that, maybe it's better to add an automation to power on when power off, if is quik enough it could work, if not maybe we have to send the power on order every 5 minutes. For me sometimes the plug has powered off in 1 hour.

I did that but when the power went automatically on it went off again and then on again. Now i have a 15 seconds delay that works.

i bought the tuya bridge and connected two sockets. Waiting to give back results. Firmware is 1.0.10, no updates.

[durkimat]

I have one that turns off within a couple of minutes. Automating turning back on isn't practical for that one. Plus another was intended to measure power of my Comms gear, including home assistant - that didn't work too well 😂 Send like there's a variety of similar but different plugs out there all with the same issue. @phoxy84 plugs have a completely different firmware to mine and I've noticed with the 5 I have, they all appear with different product names when I register them. I'm not really holding out too much hope. But if these are no good, are there other good value ZigBee plugs available that actually work?

[meganiekje]

As I wrote before: it is not very difficult to bridge the relay contact. The relay is switching only one 230volt pin. The other pin is always connected, and has the Ampere measurement resistor in series. Just make sure you use a thick wire, as there might run 16 amps. Ofcourse, the overcurrent and under/overvoltage protections no longer work, but the measurements do work. You can use the plugs as a measuring and zigbee mesh device.

[nickles-lee]

@diegogarciadev : maybe, tuya does re-send the 'ON' command frequently, to keep the plug active. I have made a rule that does just that, every 6 hours. Lets see if that helps...

I thought about that, maybe it's better to add an automation to power on when power off, if is quik enough it could work, if not maybe we have to send the power on order every 5 minutes. For me sometimes the plug has powered off in 1 hour.

I'm doing exactly that, but the trouble is that it'll still reset the clock on my oven...

[MudiStar]

I found an interim solution: aktivate the "child_lock" option (Enables/disables physical input on the device)

I had no problems for at least 48h

[diegogarciadev]

I found an interim solution: aktivate the "child_lock" option (Enables/disables physical input on the device)

I had no problems for at least 48h

It doesn't work for me in a device joined with zigbee2mqtt, the ones in tuya brigde are still up but I had one disconection in 3 days

[durkimat]

Only one of my devices presents a child lock in settings. It's very odd tbh, of the 5 devices they all seem to present slightly differently in tuya. One even had a blue indicator light whereas the others are red. All the same batch from one supplier but clearly all different.

[MudiStar]

In my log file it looked like someone had pressed the button, but no one was home at the time or I was sitting in the same room without touching anything. So I thought to give it a try and deactivate the button itself.

I have only problems with the one with the blue indicator. The red ones are ok They all have the child lock setting

[diegogarciadev]

In my log file it looked like someone had pressed the button, but no one was home at the time or I was sitting in the same room without touching anything. So I thought to give it a try and deactivate the button itself.

I have only problems with the one with the blue indicator. The red ones are ok They all have the child lock setting

This is what I found in tuya developer platform:

2022-04-03 05:11:14 Report ERROR 0 device itself
2022-04-03 05:11:07 Report ERROR 4 device itself
2022-04-03 05:11:07 Report POWER1 OFF device itself

What model are the ones with the red light?

[MudiStar]

Red: Zigbee Model TS011F Zigbee Manufacturer _TZ3000_ew3ldmgx

Blue: Zigbee Model TS011F Zigbee Manufacturer _TZ3000_typdpbpg

[phoxy84]

To test I set one on child lock. I will report back.

red is also: _TZ3000_u5u4cakc (plug_3)

[jar87]

Hey. Since i updated all plugs via zigbee gateway all plugs works great. All, for all time, are in ON mode. But issue is with reporting. I`m not receiving any data from them:(

[phoxy84]

Hey. Since i updated all plugs via zigbee gateway all plugs works great. All, for all time, are in ON mode. But issue is with reporting. I`m not receiving any data from them:(

Then it should be a software/firmware problem or bridge problem, no hardware issue….

[jar87]

@phoxy84 i wrote that here about 2-3 weeks ago ;)

[diegogarciadev]

Hey. Since i updated all plugs via zigbee gateway all plugs works great. All, for all time, are in ON mode. But issue is with reporting. I`m not receiving any data from them:(

All my plugs were updated by Z2M, no new updates from SmartLife App, the version is 1.0.10

[jar87]

@diegogarciadev thats why i connected zigbee gateway with smart Life app and then repaired plugs and updated them also. Then it worked. In z2m till now i dont see and didn`t saw any updates...

[diegogarciadev]

@diegogarciadev thats why i connected zigbee gateway with smart Life app and then repaired plugs and updated them also. Then it worked. In z2m till now i dont see and didn`t saw any updates...

How do you repair the plugs? I've removed them from z2m and added to smart life trough tuya zigbee bridge but no updates received

[jar87]

@diegogarciadev hmm strange. exactly 19 days ago i updated plugs to 1.0.5 version. Check screen below. Same thing i`ve posted here, in that topic, like i wrote 19 days ago.

Maybe try to change location in Smart Life app?

[diegogarciadev]

@diegogarciadev hmm strange. exactly 19 days ago i updated plugs to 1.0.5 version. Check screen below. Same thing i`ve posted here, in that topic, like i wrote 19 days ago.

Maybe try to change location in Smart Life app?

[jar87]

@diegogarciadev very strange..:/