Zigbee Cluster 0xEF00

I’ve been going through my system logs and working on resolving the miscellaneous errors; mostly it’s just due to poorly-written automations where the automation would be called while it was still running. Easy fix.

What I can’t seem to fix is a constant stream of “Unknown cluster command” errors on cluster 0xef00 coming from ZHA. I’ve discovered that the 0xef00 cluster is a manufacturer-specific cluster. All of my errors come from Tuya mmWave sensors; apparently Tuya uses this cluster for inter-device communication.

All of my devices work, but this error is polluting the logs to a large degree; right now it’s showing over 100k instances of this error. Is there a way to have HA just ignore this cluster completely? It’s not causing any issues with functionality, but I would rather the logs just show actual errors so I can more easily identify problems and fix them.

I’ve read that Z2MQTT doesn’t have this issue, but swapping from ZHA to Z2MQTT is not an option for me, especially for what amounts to a logging issue. It would require re-pairing almost 100 Zigbee devices and modifying nearly every single automation.

paf,

Cannot really answer your questions but if you ever swap to z2m and you keep the exact same friendly name you are using in zha, automations won’t need to be updated. I know it would be still a pain to re-pair but z2m is better than zha, so you will gain in the long term.

spitfire,

Couldn’t agree more. ZHA is supposed to be more simple to use, but if one is already using HA it’s not going to be long before they reach its limits. Zigbee2MQTT has better device support and more features. While the basic setup may be a little bit more complicated than ZHA you get the benefits mentioned earlier, and you don’t really need to understand all of its functionality from the start - you can learn as you go.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • homeassistant@lemmy.world
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #