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.
It is decoupled from home automation system.
It does just one thing, and it should do it well. No duplication of efforts by writting support for same devices in multiple softwares.
In future if I wanted to redo HA from scratch or swap it with some else software, I can continue using Zigbee2MQTT without repairing all devices.
Even, I can test different software in parallel, by connecting it to already running MQTT, to access sensor readings of my existing running Zigbee network.
Sounds good. I think I’ll look into also switching from my Conbee II to a CC2652 based adapter, which might allow me to slowly transition from one system to the other with both adapters running in parallel.