zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

HG08673 has stopped reporting new energy data

Open Gnarfoz opened this issue 1 year ago • 6 comments

What happened?

On May 13, after updating to dev branch version 09e51e0, all of my HG08673 have stopped reporting new energy data. They're stuck on whatever their latest value was.

09e51e0 pulls in zigbee-herdsman-converters 19.38.0, which is the first version to contain this commit: https://github.com/Koenkk/zigbee-herdsman-converters/commit/4182889448e29e1bcf8e4aae961fe5dea0fa0543 I think it might be related, since these HG08673 are shown as

Zigbee Model TS011F
Zigbee Manufacturer _TZ3000_j1v25l17

in the frontend.

I'm not sure where the firmware version of the devices is exposed, if at all.

What did you expect to happen?

Values to keep updating.

How to reproduce it (minimal and precise)

Just start Z2M and watch the numbers stay the same even though there's energy being consumed.

Zigbee2MQTT version

1.37.1-dev (commit #09e51e0)

Adapter firmware version

0x26720700

Adapter

ConBee2

Setup

Docker / Podman

Debug log

No response

Gnarfoz avatar May 20 '24 23:05 Gnarfoz

Could you provide the data/database.db entry of your device?

Koenkk avatar May 21 '24 18:05 Koenkk

Sure: https://gist.github.com/Gnarfoz/712596eb1958d0225bccb98119284e1f

Gnarfoz avatar May 21 '24 18:05 Gnarfoz

Exactly same issue on different devices and networks (TS011F_plug_1+BSD29_1) Power: no issue Current: no issue Voltage: no issue Energy: NullkWh or 0kWh

network #1 (1.37.1-dev commit: [d484405]) device: TS011F_plug_1

network #2 (1.37.1-dev commit: [d484405]) device: TS011F_plug_1

network #3 (1.37.1-dev commit: [d484405]) device: TS011F_plug_1 BSD29_1

I can send database.db in private message (not for public use)

Update: On network #3, I removed "-dev" from the Z2MQTT image name on Docker. Now I see version 1.37.1 commit: ea39d86 The issue looks resolved!

On other networks I keep the "latest-dev" (version 1.37.1-dev commit: 9b3a394) and problem continue.

leonidostrovski avatar May 21 '24 18:05 leonidostrovski

@Gnarfoz I don't think it's related to https://github.com/Koenkk/zigbee-herdsman-converters/commit/4182889448e29e1bcf8e4aae961fe5dea0fa0543, this only affects devices detected as TS011F_plug_3, yours is detected as HG08673. Could you provide a 10 minute debug log? I want to check wether the polling happens.

See this on how to enable debug logging.

Koenkk avatar May 22 '24 18:05 Koenkk

Sure thing, here you go: log.gz

Gnarfoz avatar May 22 '24 19:05 Gnarfoz

I had singled out https://github.com/Koenkk/zigbee-herdsman-converters/commit/4182889448e29e1bcf8e4aae961fe5dea0fa0543 because it looked vaguely related and fit into the time frame, given that I auto-update daily to the latest dev version. However, https://github.com/Koenkk/zigbee2mqtt/commit/09e51e064bd4a6759939fbc565f818e6df6d7049 also includes the huge ZigBee spec revamp, so I guess anything is possible. 😀

Gnarfoz avatar May 22 '24 19:05 Gnarfoz

Found the issue, fixed!

Changes will be available in the dev branch in a few hours from now.

Koenkk avatar May 27 '24 19:05 Koenkk

Can confirm, it's alive again. :-) image

Big thanks, @Koenkk!

Gnarfoz avatar May 28 '24 08:05 Gnarfoz