TuYa BW-SHP13 "TS011F_plug_1" - False zero Watt power data

[SaturnusDJ]

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.

22:01:20: '{"child_lock":"UNLOCK","current":0.03,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:01:25: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:04:20: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:04:20: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":13,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:05:18: '{"child_lock":"UNLOCK","current":0,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":13,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:05:18: '{"child_lock":"UNLOCK","current":0,"energy":0.3,"indicator_mode":"off/on","linkquality":138,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:05:23: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:05:23: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:41: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:42: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":13,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:46: '{"child_lock":"UNLOCK","current":0,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":13,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:46: '{"child_lock":"UNLOCK","current":0,"energy":0.3,"indicator_mode":"off/on","linkquality":138,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:51: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'
22:09:54: '{"child_lock":"UNLOCK","current":0.09,"energy":0.3,"indicator_mode":"off/on","linkquality":134,"power":12,"power_outage_memory":"restore","state":"ON","update":{"state":"idle"},"voltage":234}'

(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_interval was 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

[ceesvanegmond]

@SaturnusDJ Having the same problem It seems to be hardware related issue #12421

[ceesvanegmond]

@SaturnusDJ Having these kind of graphs at the moment 😆

[SaturnusDJ]

That is truly nuts...
I get the feeling these are not hardware defects but bad design. Unless there are users with no dips? Please post.

Therefore I hope it is possible to add a setting to only accept zero values after three zero values have been reported.

[SaturnusDJ]

I reported the issue to BlitzWolf now.

[ceesvanegmond]

@SaturnusDJ Yeah; they probably aren't going to do anything with it... Unfortunately...

[SaturnusDJ]

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.

[SaturnusDJ]

TuYa also can't help because by buying from them, BlitzWolf takes all responsibility/accountability I guess.
I wrote again to BlitzWolf. After that I will mention Koen here, hopefully he is open to a workaround. Otherwise it's game-over.

[SaturnusDJ]

@Koenkk
Can you share your idea of what this is and what to do with it?
BlitzWolf is unwilling to look at their firmware.

[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.

[vincentscode]

The device does seem to report 0.

Debug 2023-04-13 22:12:04	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":69}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:06	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":65}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:11	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":0}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:13	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":66}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:22	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":69}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:27	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":65}' from endpoint 1 with groupID null
Debug 2023-04-13 22:12:30	Received Zigbee message from 'Server Socket', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":63}' from endpoint 1 with groupID null

[Koenkk]

I see, I cannot fix it from the z2m side, it's an issue of the device itself.

[vincentscode]

That's unfortunate, but understandable. I assume contacting some tuya whitelabel company will have little effect.
Is there any way to filter this in z2m?

[Koenkk]

@vincentscode how do you want to filter it? You don't know whether the 0 report is a false report or a real measurement.

[vincentscode]

@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.