submitted 9 months ago by corroded@lemmy.world to c/homeassistant@lemmy.world

9 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[-] paf@jlai.lu 3 points 9 months ago

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.

[-] corroded@lemmy.world 1 points 9 months ago

I've swapped out at few of my Zigbee devices in the past, and even though I've deleted the original device, HA will add an "_2" to the entity ID, which breaks any automation that uses it, even if the friendly name remains the same. The only time I've seen this not happen is when a device drops off the network and I re-pair it. Is there a trick to making this work? Even if I don't switch to Z2MQTT, this would be really useful to know. I have a few unreliable cheap door sensors that I'd like to replace, but they're tied to so many automations that I've been dragging my feet on it.

[-] paf@jlai.lu 1 points 9 months ago

No particular tricks, maybe it's a one of the limitation of zha. As an exemple, I recently replace a bulb by a new one and old one was repurpose somewhere else in the house, the only thing I did was to rename old bulb and added the new one with old bulb name.

load more comments (6 replies)

this post was submitted on 09 Jan 2024

8 points (100.0% liked)

homeassistant

11921 readers

1 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago

MODERATORS

GreatAlbatross@feddit.uk