Since update 4.3.7_0036, adjusting the brightness of Aqara lights in Home Assistant doesn’t immediately apply the change.
The Aqara app works fine, but when I adjust the brightness of an Aqara light imported from Home Assistant as a HomeKit device, the brightness information seems to be correctly transmitted to the M2 Hub, but it doesn’t work properly on the M2 Hub.
The brightness information only works about once in ten attempts.
Turning it on and off and adjusting the color temperature work properly.
Only the brightness part doesn’t work properly.
I have two M2 Hubs, and this issue occurs on both.
Are you using Aqara lights via the Aqara Hub in Home Assistant experiencing any issues?
4 Likes
@ddrzero It sounds like you’re experiencing a frustrating issue with the brightness adjustment on your Aqara lights when used with Home Assistant and the M2 Hub. From the reference information available, there isn’t a direct solution to this specific problem. However, here are a few steps you might consider trying:
-
Check Firmware and App Versions: Ensure that both your Aqara lights and M2 Hubs have the latest firmware updates. Sometimes, bugs are resolved in newer versions.
-
Device Connection: Verify that your devices are properly connected and online within the Aqara app. This can rule out any connectivity issues that might affect performance.
-
Reset and Re-Pair: Consider resetting the affected lights and re-pairing them with the hub. This can sometimes help in resolving unusual behavior.
-
Community Collaboration: Engage with the community on forums dedicated to Aqara and Home Assistant. Other users might have encountered and solved similar issues.
If these steps don’t resolve the issue, it might be beneficial to reach out to Aqara’s customer support for further assistance. They might have additional insights or steps specific to the firmware update you’re dealing with.
Please don’t hesitate to share any solutions you find with the community, as it could be incredibly helpful to others facing similar challenges!
have the same issue… @ddrzero did you find a solution? Looks like it is a problem with the 4.3.7_0036 but I don’t see a way to rollback to the previous version…