That’s not how software development works. Do you think developers are bugs on purpose?
I have no idea if this is a bug, and if it is, whether it’s a bug or zha integration or the coordinates firmware, but if you won’t try to report it properly, and nobody else will, chances for it to get fixed are small.
As for how to report issues, check this help article:
Integration issues are in the core tracker.
Also check the troubleshooting documentation for ZigBee, it has a section on reporting issues that list mandatory information you must include in the report in the addition to the regular things:
However, in case it’s a problem with your coordinator, you could make a support request with Nabu Casa (it’s commercial company, they are responsible if the product they sell is defective).
I have no clue what’s causing that issue, but there are many helpful people on GitHub that may guide you through debugging. Just keep in mind many of them are volunteers, you need to show you did your homework (which, to be clear, I’m not suggesting you wouldn’t).
Thanks, I’ll post on GitHub if I hadn’t already. This has been going on for at least 5 months now, so I can’t remember where I’ve posted. I remember going to their GitHub and maybe got sidetracked and forgot to post.
Someone told me devs aren’t on the forums, so posting about bugs here is useless. I was recommended to post on the Home Assistant Discord. A link to it is somewhere in this thread. I didn’t get help there though.
At this point, it clearly looks like a bug, so it makes sense to post in their GitHub
I’m gonna be more affected than the vast majority of people because I have 33 of these exact same model of sensor. I’m sure most folks would just assume their one or two sensors are bad, but because I owned them for a year without issue and only have issues with these, it’s clear to me something changed.
I’m tired of spending all this money on new AAA batteries and replacing them in my sensors. Anything I can do to fix it would be great.
Now that my ZBT-2 has finally arrived, I can confirm it’s not my coordinator as the issue still exists on this model.
Well, maybe not useless, because there are still people here who help with debugging, checking if the issue is really a bug or maybe some misconfiguration etc. but yes, devs are more in discord - however the official way to report bus is on GitHub. I think on discord it’s possible to get help with some simple issues, but it doesn’t have proper bug tracking, so GitHub is the way to go.
I wish you luck with this issue, I can only imagine how annoying that must be with that number of devices.
If this doesn’t work, you could consider testing the other ZigBee integration (Z2M) to see if the issue is there too. But I don’t think switching such big system is easy and simple and running 2 at the same time might be problematic, as they would compete for the same airwaves, so yeah…
