Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HG08673 has stopped reporting new energy data #22720

Closed
Gnarfoz opened this issue May 20, 2024 · 8 comments
Closed

HG08673 has stopped reporting new energy data #22720

Gnarfoz opened this issue May 20, 2024 · 8 comments
Labels
problem Something isn't working

Comments

@Gnarfoz
Copy link

Gnarfoz commented May 20, 2024

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: Koenkk/zigbee-herdsman-converters@4182889
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 Gnarfoz added the problem Something isn't working label May 20, 2024
@Koenkk
Copy link
Owner

Koenkk commented May 21, 2024

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

@Gnarfoz
Copy link
Author

Gnarfoz commented May 21, 2024

@leonidostrovski
Copy link

leonidostrovski commented May 21, 2024

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.

@Koenkk
Copy link
Owner

Koenkk commented May 22, 2024

@Gnarfoz I don't think it's related to Koenkk/zigbee-herdsman-converters@4182889, 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.

@Gnarfoz
Copy link
Author

Gnarfoz commented May 22, 2024

Sure thing, here you go: log.gz

@Gnarfoz
Copy link
Author

Gnarfoz commented May 22, 2024

I had singled out Koenkk/zigbee-herdsman-converters@4182889 because it looked vaguely related and fit into the time frame, given that I auto-update daily to the latest dev version.
However, 09e51e0 also includes the huge ZigBee spec revamp, so I guess anything is possible. 😀

Koenkk added a commit to Koenkk/zigbee-herdsman that referenced this issue May 27, 2024
@Koenkk
Copy link
Owner

Koenkk commented May 27, 2024

Found the issue, fixed!

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

@Gnarfoz
Copy link
Author

Gnarfoz commented May 28, 2024

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

Big thanks, @Koenkk!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants