Hi everyone, I’m relatively new to the world of openHAB and ZigBee, so I’m hoping you can help me figure out this issue I’m encountering. I’ve been using openHAB on my Raspberry Pi setup for a few months now, and I’ve integrated several SNZB-02 temperature and humidity sensors. They’ve been working perfectly, providing accurate readings and keeping my environment comfortable. However, there’s one thing that’s been bugging me, and I’m hoping to get some insight or advice on how to resolve it.
The issue I’m facing is with the battery level reporting on my SNZB-02 sensors. Despite the fact that these sensors are supposed to be incredibly power-efficient and last for months on a single battery, the battery level channel is still showing 100% after more than six months of use. While I appreciate the efficiency of ZigBee, this inconsistency is a bit concerning. I’m wondering if there might be an underlying issue with how the battery level is being reported or if there’s something I can do to ensure accurate battery monitoring.
I’ve done some digging into the logs, and I noticed some recurring errors related to server binding. Here’s a snippet of what I found:
[ERROR] [verter.ZigBeeConverterBatteryPercent] - 00124B00251E3049: Error 0xffff setting server binding
I’ve followed the recommended steps to activate logging and monitor the issue, but I’m not entirely sure how to interpret the logs or what specific actions I should take to resolve the problem. I’m also curious if others have experienced similar issues with their ZigBee devices and how they’ve managed to address them.
In the meantime, I’ve taken some steps to mitigate the situation. I’ve kept a close eye on the sensor functionality to ensure that the temperature and humidity readings remain accurate. I’ve also started monitoring the battery levels manually, just to be safe. However, I’d love to find a more permanent solution that allows me to rely on the built-in battery monitoring without worrying about potential discrepancies.
I’m also wondering if there might be a firmware update or a configuration change that could help resolve this issue. I’ve checked the manufacturer’s website and the openHAB forums, but I haven’t found any specific guidance related to this particular error code. If anyone has encountered something similar or has any suggestions, I’d be incredibly grateful for your input.
Overall, while this issue hasn’t caused any significant problems with my setup, it’s something I’d like to address to ensure the long-term reliability of my sensors. I’m hoping that by sharing my experiences and asking for advice, I can gain some clarity and find a resolution that works for my setup.
Thank you all in advance for your time and assistance. I truly appreciate the supportive and knowledgeable community here at openHAB!
Best regards,
[Your Name]