Yeah I bought three of these recently, I’ve only paired one for testing but it seems to randomly switch off anywhere between 6 - 36 hours. Not great for most applications, especially equipment that may be damaged by unexpected power loss.
Hey,
Just got one of these and i got a random turn off. Started digging around and i got here.
I did notice that the reading on HA had drops to 0 every ~5min.
Went into Z2MQTT and on the Settings enabled Retention. No more 0s for now, let’s hope this stops the shutdowns.
Is this retention option also available in zha?
I tried to enable the Retention but I still have the same issue.
In my case, I can never get it on at all, any clue about what could be the issue?
This is what I see in the Z2M logs after I try to switch it on:
Debug 2022-05-10 13:06:54Received MQTT message on 'zigbee2mqtt/Plug/set' with data '{"state":"ON"}'
Debug 2022-05-10 13:06:54Publishing 'set' 'state' to 'Plug'
Info 2022-05-10 13:06:54MQTT publish: topic 'zigbee2mqtt/Plug', payload '{"child_lock":"UNLOCK","current":0,"energy":0,"indicator_mode":"on","linkquality":182,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":null},"update_available":null,"voltage":283}'
Debug 2022-05-10 13:06:54Received Zigbee message from 'Plug', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID 0
Info 2022-05-10 13:06:54MQTT publish: topic 'zigbee2mqtt/Plug', payload '{"child_lock":"UNLOCK","current":0,"energy":0,"indicator_mode":"on","linkquality":182,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":null},"update_available":null,"voltage":283}'
Debug 2022-05-10 13:06:56Received Zigbee message from 'Plug', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2022-05-10 13:06:56MQTT publish: topic 'zigbee2mqtt/Plug', payload '{"child_lock":"UNLOCK","current":0,"energy":0,"indicator_mode":"on","linkquality":185,"power":0,"power_outage_memory":"restore","state":"OFF","update":{"state":null},"update_available":null,"voltage":283}'
The same messages appear if I press the button manually in the plug itself.
on another thread on github, we made all sort of tests. The shutdown happens even with plugs not connected to zigbee. Even with plugs on UPS. Even with plugs with a Faraday cage and almost zero signal. Even with plugs without any load or anything connected at all.
It happens ALWAYS.
I have some tuya zigbee smart plugs. I bought them because one of my aquara plugs burned down. I found out why that happen by using tuya smart plug. It was because my washing machine and oven are connected to the same plug and when they are working simultaneously energy current is lager than 220v. I dont know why fuse doesnt turn off the electricity. That was the reason why my aquara smart plug burned out.
Maybe the problem is in current running those plugs, so I will try to check that first.
Another issue can be coordinator.
P.S. This is the one I got
TS011F_plug_3
I dont have problems with disconnecting after I found out what was the issue with kitchen plug.
Ok I’ve been having major issues since Jan with my power plugs switching off, tried many things and I read recently about over current. Turns out my plugs were going off between 10am and 3pm some days more than other( more sunnier days the more often they would go off). I have 2 solar systems and yesterday 26th June 2022 I decided turn off the solar and hey presto the plugs work fine. Just working out which system is causing the issue now. Waiting from a response from my supplier and Tuya on resolving the issue. I understand from my supply many people are having this issue. So maybe if you got solar panels, that could be many problem problems.
That is just too bad. I have the same plug and also experiencing random power off. Well, I might as well just throw this one away and order a different one, unfortunately. This time at least a BlitzWolf SHP15, which people report as reliable in the GitHub issue linked above - https://github.com/Koenkk/zigbee2mqtt/issues/11648
Since a firmware update found in the zigbee2mqtt addon, all my plugs are now working just fine without any drops aftter 3 weeks. Before the update I had drops within an hour and tthey had all dropped within a few days, so the firmware update resolved my issue
I am having this issue with some rather expensive Mercator double PowerPoints. I learner they are also tuya based TS011F by _TZ3210_<random>
They are turning off randomly. I see 0v drops throughout the day but never at the time of the switch turning off. When the switch does turn off my HA loses connection with the ZigBee coordinator so I might be missing data. Need to fix this for testing.
I habe solar but it is occuring both day and night. Worked fine for weeks then lately 3 times within a week.
Found this thread searching for 250V and experiencing exact same problem as @m133255
I’m using a Sonoff ZBBridge with Tasmota
Will have to dig more, but I have little hope this’ll be fixed as it seems to be “by design” :-/
Here’s an excerpt from a Belgian energy operator:
- Tension minimale instantanée : 184,0 V → Absolute minimum
- Tension maximale moyenne sur 10 min : 253,0 V → Average over 10 minutes
- Tension maximale instantanée : 264,5 V → Absolute maximum
Product link : Tuya Smart Zigbee 3.0 Power Plug 16A EU Outlet 3680W Meter Remote Control Work With Tuya Hub Zigbee2mqtt and Home Assistant
Shop : haozee Official Store
https://haozee.aliexpress.com/store/203725
Device info : TS011F by _TZ3000_zloso4jk
Coordinator Device info : EZSP = Silicon Labs EmberZNet protocol: Elelabs, HUSBZB-1, Telegesis by ZHA
More info : Definitely not related to HA, more a design issue of the devices.
Just buy the correct ones.
Mine never auto power off…
https://trade.aliexpress.com/order_detail.htm?orderId=8153763973618261
I buyed all versions of the power sockets, and these i have work perfect. the rest is poop.
see my discussion on here.
I have them in my house in italy, whole house, and in the Netherlands, never had this issue after the update…
That’s a shitty answer imo. The GPOs i have are over $100 each and suffering from this issue.
I have the same plugs. I use external converter for. it.
This is my external converter file
const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const e = exposes.presets;
const ea = exposes.access;
const definition = {
zigbeeModel: ['TS011F'], // The model ID from: Device with modelID 'lumi.sens' is not supported.
model: '_TZ3000_gjnozsaz', // Vendor model number, look on the device for a model number
vendor: 'Blitzwolf', // Vendor of the device (only used for documentation and startup logging)
description: 'Tuya Power Plug', // Description of the device, copy from vendor site. (only used for documentation and startup logging)
fromZigbee: [fz.on_off, fz.electrical_measurement, fz.metering, fz.ignore_basic_report, fz.tuya_switch_power_outage_memory],
toZigbee: [tz.on_off, tz.tuya_switch_power_outage_memory],
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
await reporting.bind(endpoint, coordinatorEndpoint, ['genOnOff', 'haElectricalMeasurement', 'seMetering']);
endpoint.saveClusterAttributeKeyValue('seMetering', {divisor: 100, multiplier: 1});
endpoint.saveClusterAttributeKeyValue('haElectricalMeasurement', {
acVoltageMultiplier: 1, acVoltageDivisor: 1, acCurrentMultiplier: 1, acCurrentDivisor: 1000, acPowerMultiplier: 1,
acPowerDivisor: 1,
});
try {
await reporting.currentSummDelivered(endpoint);
} catch (error) {/* fails for some #11179 */}
},
options: [exposes.options.measurement_poll_interval()],
// This device doesn't support reporting correctly.
// Koenkk/zigbee-herdsman-converters#1270
exposes: [e.switch(), e.power(), e.current(), e.voltage().withAccess(ea.STATE),
e.energy(), exposes.enum('power_outage_memory', ea.STATE_SET, ['on', 'off', 'restore'])
.withDescription('Recover state after power outage')],
onEvent: tuya.onEventMeasurementPoll,
};
module.exports = definition;
And I use in configuration.yaml inside zigbee2mqtt dir
external_converters:
- name_of_external_converter_file.js
I have no problem, thats what i’m saying…
keep it nice and clean bro, and don’t say i post sh*tty answers…
If you don’t like my answer just say it in a normal way.
My point was simply that we would ideally find a solution to fix the problem, not have to spend more money buying again.
My issue wasn’t with you recommending a plug, it was the implication, intended or not, that it is our fault for buying the wrong ones.
But I think he’s actually right and I appreciate sharing this here because after this bad experience with the plugs I didn’t dare to buy another cheap one from aliexpress.
So thanks @malosaa for the advice, I’ll buy one and give it a try!
I didn’t mean anything by it, and i’m sorry if you did read it that way. I didn’t say it’s your fault that the plugs don’t work.
if you read carefully, I say that you should buy the correct one instead.
I have also explained it several times on github to help people out, so a number of people also have plugs (apparently others) that also work.
But this auto off problem is solved (atleast for me) i have now a lot of them in my home.
but then there is a software problem left, which is that it sometimes indicates 0 watts per update. I have temporarily found something on that but is not perfect.
So for graphing these plugs i would not recommend it.
Tuya needs to fix the error on showing 0 usage together with the normal usage every change.
This result in a bad graph…
So for me i’m cool with it and atleast they don’t shut off again
So the plugs i use are EU plugs and 20A from Aubess.
I really don’t know if the US or the UK plugs will act the same.
I hope they work for you, if you need the store link i can post it here.
They ship fast and are friendly people.
regards and i’m glad i could help.