Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.97k stars 1.67k forks source link

ts011f_plug_3 not providing power values #24218

Open senrabyar opened 1 week ago

senrabyar commented 1 week ago

What happened?

Similar to other similar issues which I think I have exhausted trying.

I have 14 TS011F plugs working OK (4 are plug_1, 10 are plug_3). I purchased a further batch of four and two work fine, but the other two have no power. The working ones have the expected 1.0.5 firmware, but the broken have 0122052017 firmware. The physical units are identical, and labels give model WHDZ03.

The plug is the UK 3 pin version.

I have tried changing the poll interval from blank to both 30 and '30'

OTA says firmware up to date.

The stated Zigbee Manufacturer is _TZ3000_o81odtrp which is not the same as all the working plugs, and in correspondence on the HA Community is not known by other people.

Is this a new device / new firmware / corrupt firmware ?

What did you expect to happen?

Expected same monitoring as the the other TS011F_plug_3

How to reproduce it (minimal and precise)

The behaviour is detected by simply pairing device, and viewing in Z2M Devices or Dashboard

(Also fails on ZHA / Conbee )

Zigbee2MQTT version

1.40.2

Adapter firmware version

20210708

Adapter

Sonoff ZB Dongle P

Setup

HA on Pi5

Debug log

Sorry I cannot find data/log in any HA folder

Here's the stuff Z2M reports

Device type Router Zigbee Model TS011F Zigbee Manufacturer _TZ3000_o81odtrp Description Smart plug (with power monitoring by polling) Support status Supported

IEEE Address 0xa4c138ae715a78fb Network address 0xC542 / 50498 Firmware version 0122052017 Manufacturer [Tuya] Model [TS011F_plug_3] Power
Interview completed True

{ "child_lock": "UNLOCK", "indicator_mode": "off/on", "last_seen": "2024-10-05T10:52:27.304Z", "linkquality": 102, "power_outage_memory": "off", "state": "OFF", "update": { "installed_version": 268449287, "latest_version": 268449287, "state": "idle" }, "update_available": false, "current": null, "energy": null, "power": null, "voltage": null }

senrabyar commented 1 week ago

Further info ..

Discovered that configuration.yaml already had an "advanced:" line, so that prevented the logging debug from working.

Now found a file in \log\datestamp\log.log which contains what you want see - debug errors !

The file is heavily polluted by the excess data rate the air quality devices produce - but that is a different problem. log.log

See attached