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

Powertag "zh:controller:buffalozcl: Unknown attribute" repeatedly in log #22396

Closed
rbswift opened this issue May 2, 2024 · 5 comments
Closed
Labels
problem Something isn't working

Comments

@rbswift
Copy link
Contributor

rbswift commented May 2, 2024

What happened?

Since upgrading to the latest version I have the following events repeatedly logged.

Seems to relate to this device: https://www.zigbee2mqtt.io/devices/A9MEM1570.html#schneider%2520electric-a9mem1570

May 02 17:20:28 alarm npm[5128]: [2024-05-02 17:20:28] info:         zh:controller:buffalozcl: Unknown attribute 16652 in cluster seMetering
May 02 17:20:34 alarm npm[5128]: [2024-05-02 17:20:34] info:         zh:controller:buffalozcl: Unknown attribute 16654 in cluster seMetering
May 02 17:20:44 alarm npm[5128]: [2024-05-02 17:20:44] info:         zh:controller:buffalozcl: Unknown attribute 16403 in cluster seMetering
May 02 17:20:44 alarm npm[5128]: [2024-05-02 17:20:44] info:         zh:controller:buffalozcl: Unknown attribute 16655 in cluster seMetering
May 02 17:21:00 alarm npm[5128]: [2024-05-02 17:21:00] info:         zh:controller:buffalozcl: Unknown attribute 16652 in cluster seMetering
May 02 17:21:05 alarm npm[5128]: [2024-05-02 17:21:05] info:         zh:controller:buffalozcl: Unknown attribute 16654 in cluster seMetering
May 02 17:21:10 alarm npm[5128]: [2024-05-02 17:21:10] info:         zh:controller:buffalozcl: Unknown attribute 16384 in cluster seMetering
May 02 17:21:10 alarm npm[5128]: [2024-05-02 17:21:10] info:         zh:controller:buffalozcl: Unknown attribute 16653 in cluster seMetering
May 02 17:21:15 alarm npm[5128]: [2024-05-02 17:21:15] info:         zh:controller:buffalozcl: Unknown attribute 16403 in cluster seMetering
May 02 17:21:15 alarm npm[5128]: [2024-05-02 17:21:15] info:         zh:controller:buffalozcl: Unknown attribute 16655 in cluster seMetering
May 02 17:21:36 alarm npm[5128]: [2024-05-02 17:21:36] info:         zh:controller:buffalozcl: Unknown attribute 16654 in cluster seMetering
May 02 17:21:41 alarm npm[5128]: [2024-05-02 17:21:41] info:         zh:controller:buffalozcl: Unknown attribute 16384 in cluster seMetering
May 02 17:21:41 alarm npm[5128]: [2024-05-02 17:21:41] info:         zh:controller:buffalozcl: Unknown attribute 16653 in cluster seMetering

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

just updated to 1.37

Zigbee2MQTT version

1.37

Adapter firmware version

20210708

Adapter

zStack3x0

Setup

plain - Raspberry Pi

Debug log

No response

@rbswift rbswift added the problem Something isn't working label May 2, 2024
@jbouv55151
Copy link

I do have the same problem and the same product.

@Nerivec
Copy link
Collaborator

Nerivec commented May 2, 2024

This is a logging issue only. It will be lowered back to debug level, where it should have stayed 😉

@rbswift
Copy link
Contributor Author

rbswift commented May 2, 2024

This is a logging issue only. It will be lowered back to debug level, where it should have stayed 😉

Thanks for that. I wonder what the additional data might be? Anything interesting?

@Nerivec
Copy link
Collaborator

Nerivec commented May 2, 2024

Lots of stuff that manufacturers intend for their hubs. Sometimes it proves useful to Z2M (after lengthy investigations into what they mean 😅), sometimes not.

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

Koenkk commented May 4, 2024

Moved to debug!

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

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

4 participants