Hi all, I’ve been diving into the world of smart home automation with Aqara devices, and I wanted to share my experience with the H2 EU Rollershutter controller. While setting up my system, I encountered a peculiar issue with percentage commands that I thought might be helpful to discuss here.
Initially, everything seemed to be working smoothly. I paired the H2 EU Rollershutter with my Aqara M3 hub and integrated it into my OpenHAB setup. Connectivity wasn’t an issue—up and down commands worked perfectly. However, when I tried to send percentage-based commands, things got a bit strange. Sending a 100% command only moved the shutter a few centimeters, and the Aqara app indicated it had only moved 1%. Any percentage below 100% resulted in the shutter opening fully, which was definitely not the intended behavior.
After some research and troubleshooting, I noticed a pattern: it seemed like the H2 EU was interpreting the percentage commands by dividing them by 100. For example, sending a 100% command was interpreted as 1%, and sending a 50% command resulted in 0.5%, which isn’t a valid state. I even tried sending a 10000% command, thinking it might compensate for the division, but the controller rejected any values above 100%.
I reached out to the community for advice and found that others had encountered similar issues. Through trial and error, I discovered that manually adjusting the percentage values in the OpenHAB configuration to match the expected behavior was a viable workaround. For instance, setting the command to 1% in OpenHAB resulted in the shutter moving to the fully closed position, which aligned with the intended functionality.
While this solution isn’t perfect, it allowed me to continue using my Aqara H2 EU Rollershutter without major disruptions. I’m hopeful that future firmware updates will address this percentage interpretation issue, making the integration smoother for everyone.
This experience taught me the importance of thorough testing and community support when integrating new smart home devices. It also highlighted the need for clear communication between device manufacturers and users to ensure compatibility and ease of use across different platforms.
If anyone else has encountered similar issues or has found a more elegant solution, I’d love to hear about it! Let’s keep the conversation going and help each other navigate the exciting but sometimes challenging world of smart home automation.