Hi everyone, I wanted to share my experience with a Z-Wave door sensor issue I recently encountered. After upgrading to Z-Wave 2.0, my door sensor started behaving oddly—it would report as ‘ON’ even when the door was closed. This was quite puzzling, especially since it worked flawlessly with the older Z-Wave 1.x binding.
After some digging, I realized the problem stemmed from how the Z-Wave 2.0 binding interprets the sensor’s signals. The sensor was sending a ‘BASIC report’ with a value of 0xFF when the door opened, which correctly set the state to ‘ON’. However, when the door closed, it sent a ‘BASIC report’ with 0x00, but the binding wasn’t updating the state as expected.
I found that in the Z-Wave 1.x setup, there was a parameter called ‘respond_to_basic=true’ that ensured the sensor’s state was accurately reflected. Unfortunately, this parameter isn’t directly available in Z-Wave 2.x. After some research and testing, I discovered that adjusting the sensor’s configuration in the Z-Wave settings and ensuring the binding was up-to-date resolved the issue.
It was a bit of a learning curve, but it taught me a lot about how Z-Wave bindings handle different sensors. I hope sharing this helps someone else avoid the same frustration! If anyone has similar issues or tips, I’d love to hear them. Happy troubleshooting! 