For anyone that is still having issues with their hub, due to the problematic 1.6.1 update from a couple of weeks ago, Aqara have now told us that they can issue an OTA update to your hub on a customer-by-customer basis. To do this, you will need the following info, and email it to firstname.lastname@example.org;
- Your Aqara Hub serial number, which can be found on the underside of the hub where the electrical pins are.
- If you’re using the Apple Home app, you can find the serial number for the hub, by going into the settings for the hub light, or the hub alarm.
- Your Mi Account ID. This can be found in the Mi Home app under Profiles, then click on the avatar or image for your profile and the Mi Account number can be seen under your name/profile.
- If you’re using the Aqara app, then you just need to provide the email address you use for your Aqara account.
We’ve just been told by Aqara that they are planning to issue a firmware update to fix the issues that many people have been facing with their hubs and child devices after upgrading to 1.6.1 via the Aqara app for iOS, namely reduced ZigBee signal range and offline devices and slow response times.
It seems the 1.6.1 update that has caused these problems was only meant for beta testers but somehow managed to make its way to normal users, resulting in a series of problems, centred around the hub. The update that Aqara will be issuing, presumably via the Aqara app, will drop early next week, and will in actual fact be a downgrade to the previous stable build, which is 1.6.0.
some users online have been erroneously reporting that both 1.6.1 and 1.6.0 firmware updates were causing the aforementioned issues, but in actual fact, depending on the app you’re using or even viewing the firmware number on, this would in some cases appear as 1.6.0, when in actual fact, the problem-prone update has always been 1.6.1. This is backed up by the fact that 1.6.0 has been out for a while with no reported issues, up until the 1.6.1 update dropped.
As soon as we know more or have an exact date for the ‘downgrade’ we will update this page.