As a long-time user of Homematic devices integrated with openHAB, I’ve always appreciated the seamless integration and reliability of the system. However, one issue that has consistently puzzled me is the state reversal of rollershutters between the Homematic CCU and openHAB. For instance, the HmIP-BROLL and similar devices use 100% to indicate fully open and 0% for closed, while openHAB inverts this logic.
This discrepancy might seem minor at first glance, but it creates unnecessary complexity, especially when integrating with other systems like HomeKit or when using widgets that rely on UP, DOWN, and STOP commands. After experimenting with various workarounds, including proxy items and rules, I realized that while these solutions function, they add an extra layer of complexity that shouldn’t be necessary.
I was pleasantly surprised to discover that the Z-Wave binding offers an inversion option, which made me wonder why a similar feature isn’t available for the Homematic binding. This led me to explore the possibility of submitting a feature request to the openHAB community, hoping that future updates could align the logic more closely with the manufacturer’s standards.
In the meantime, I’ve found that using proxy items with inverted values provides a reliable workaround. It’s a bit of a detour, but it ensures consistency across my setup. I’d love to hear from others who have faced similar challenges—how have you tackled this issue, and what improvements would you like to see in the binding? Let’s keep the discussion going and help each other navigate these technical nuances!
Happy automating, everyone! 