TuYa BW-SHP13 "TS011F_plug_1" - False zero Watt power data #16709
Comments
|
@SaturnusDJ Having the same problem It seems to be hardware related issue #12421 |
|
@SaturnusDJ Having these kind of graphs at the moment 😆 |
|
That is truly nuts... Therefore I hope it is possible to add a setting to only accept zero values after three zero values have been reported. |
|
I reported the issue to BlitzWolf now. |
|
@SaturnusDJ Yeah; they probably aren't going to do anything with it... Unfortunately... |
|
First they asked where I bought them, then they told me to contact that platform for a restock date. Completely irrelevant replies. What an idiots. Guess BlitzWolf does nothing more than put a label on boxes. Will try TuYa. |
|
TuYa also can't help because by buying from them, BlitzWolf takes all responsibility/accountability I guess. |
|
@Koenkk |
|
My expectation is that the firmware is bugged and incorrectly reports 0, to confirm, please provide the debug log when zero is reported. See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging. |
|
The device does seem to report 0. |
|
I see, I cannot fix it from the z2m side, it's an issue of the device itself. |
|
That's unfortunate, but understandable. I assume contacting some tuya whitelabel company will have little effect. |
|
@vincentscode how do you want to filter it? You don't know whether the |
|
@Koenkk Sure, but it seems like it's a very short singular measurement (<=2s until next message) and is surrounded by wildly different values. This seems like something that would never occur in real-world use. |
|
The |
|
Unfortunately using a debounce value just causes it to send no data at all to Home Assistant. (the flat sections are with using different debounce values, between is without) |
|
@vincentscode can you provide the debug log when load is removed from the plug (so 0 is the real value)? What we can can is e.g. always ignore the first 0 value |
|
@Koenkk Sure. I've not removed the other attributeReports this time: It seems from the log that removing the first 0 (or having the option to) should work fine as long as the reporting frequency is set high enough. |
|
Could you check if the issue is fixed with the following external converter: https://gist.github.com/Koenkk/9a00f014c9b4c4588a49db6f49cfe0be
external_converters:
- ext_converter.js
|
|
Thanks, this seems to be working! I do get the log messages about as frequently as I was getting the 0 data so it appears to be filtering correctly. While we're at it: The same issue seems to also affect current measurement (which makes sense i suppose): Voltage also drops to zero sometimes for 1 dataframe but it's a lot less frequent: Additionally I've noticed that when testing with a very low intermittent load (such as a laptop loading with a full battery) "TEMPORARY LOG: SKIPPING 0 VALUE" get's spammed quite a lot and no data is reported, I am unsure as to why that's the case but it seems like it likely won't be an issue for most people. |
|
Updated https://gist.github.com/Koenkk/9a00f014c9b4c4588a49db6f49cfe0be to also apply the fix to current and voltage, can you check it? Note that the |
|
It seems to be working just fine with the new version. |
|
@vincentscode @SaturnusDJ can you both provide the data/database.db entry of your device? Then I will make sure this fix only gets applied to your device version. |
|
I've got these two: |
|
Hey guys, sorry I was away. Thanks for the progress. 👍🏼👌🏼 Currently also two in the network here: |
Koenkk
added a commit
to Koenkk/zigbee-herdsman-converters
that referenced
this issue
Apr 16, 2023
…plug_1 (`_TZ3000_gvn91tmx`/`_TZ3000_amdymr7l`). Koenkk/zigbee2mqtt#16709
|
Integrated the fix! Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html) |
|
It does not work correctly. If you remove the load, power and current do not show 0, they continue to show the last load value. Is it possible to add a forced poll at a zero value? |
|
With 1.34.0, I have the same bug, I've a little light that consumes ~7W, and the current show the good value (0.02A) but power stays on 0 W. |
|
Hello @Koenkk ,
|
|
@Malaysk did this work fine in 1.33.2? |
|
Hello @Koenkk , Same issue, Zigbee Model: TS011F Could you please add these to the patch? |
|
@DdenBraver its enabled for all TS011F_plug_1 in z2m 1.34.0 |
|
@Koenkk several times a day I see the same type of errors in the log and they are only for devices like _TZ3000_dksbtrzs https://www.zigbee2mqtt.io/devices/TS011F_plug_1.html DB Data |
|
After 1.35.0 update all my _TZ3000_hdopuwv6 devices began get zero power drops. |
Koenkk
added a commit
to Koenkk/zigbee-herdsman-converters
that referenced
this issue
Jan 2, 2024
|
@mrmaximas pushed a fix Changes will be available in the dev branch in a few hours from now. |
mikeodr
pushed a commit
to mikeodr/zigbee-herdsman-converters
that referenced
this issue
Jan 2, 2024
|
I'm having the same issue with my plugs. It reports the state as always 'On' even when power is off from the physical switch/source. Could you have a look into this please @Koenkk? Thanks |
Same issue here, please add fix for this device thanks. |
|
Zigbee2MQTT |
|
Please provide the debug log when it starts reporting power 0 when it shouldn't. See this on how to enable debug logging. |
|
@Koenkk here the debug log: in the frontend I have this: Consider that this device was running ok in another zigbee2mqtt installation: |
|
I tried to re-pair and it is back working, I will have a look tomorrow: |
|
Can you provide more logging? Log needs to start at the point where it is OK (non zero power is reported) until a false 0 power report. |
|
I catched the error,See time 21:16:43 |
|
Thanks, but I will need the debug log. See this on how to enable debug logging. |
|
Ok, I hope now is correct, here the log where it is reporting correctly: Look here:
|
|
I am not able to catch the error on the log because in ha the debug log is limited to last n rows, is there a way to see the extended log? |
|
You can grab it from the log files, in the |
|
I found something, here the code where I selected only the device that have the problem, attached the full log. Look at the log, there are strange data also for some other device:
|
|
It seems the device reports the 0 value itself: Meaning that we cannot fix this from z2m, the plug is just bad. |
|
It is really strange, just because this start to happen when I switch to zigbee2mqtt in home assistant os, on the previous one (zigbee2mqtt in docker with zb dongle p) eeverything was running ok... |
|
@Koenkk for your reference: |
Is that RCP (Multi-pan) you are referring to? If that's the case, I may also have to reflash to zbdongle-e without Thread. |
yes it was the multipan with silicon labs multiprotocol in the middle! |
Off-topic: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
What happened?
(Opening this as problem because incorrect information is at play.)
Got two TuYa BW-SHP13 "TS011F_plug_1" today. I actually was not surprised to see that this looks the same as the ten I got almost three years ago, yet have different internals... Basic TuYa politics...
And this different version thus comes with a problem:
The power and current attributes drop to 0 (W, A) every 4.5 minutes. Those are false readings.
(Cut out some column for readability)
Can we filter this? Maybe a device_specific option to only accept zero if it is zero for x seconds. Where x should be 6 for the log above.
Oh and where
measurement_poll_intervalwas available for the 'older' version I got of this plug, it is not available for this one, and also does not do anything when added to the configuration file.What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.28.4
Adapter firmware version
20220219
Adapter
zzh! CC2652R
Debug log
No response
The text was updated successfully, but these errors were encountered: