[APP] Aqara & Xiaomi Smart Home - Simplify your life with a smarter home

Hi @TedTolboom, Athom recently introduced ‘Quick Actions’ on the device tiles in both the Homey mobile and web apps. These replace (among other options) the on/off action that used to be assigned to the device tile itself, at least in the mobile app.

I noticed that my Aqara Curtain Driver E1s do not have the Quick Action option available in their device settings in Homey. Such a quick action would allow a user to fully open/close a curtain with just one tap on the quick action icon (instead of opening the tile and using the slider). I assume the quick action is not available as there is no button to open/close curtains in the device tile.

Are you perhaps planning to add this quick action and button control for the Aqara curtain driver to your app?

As an example the image below shows my current curtain tiles: the first 4 are the Aqara ones, the last 2 are curtain drivers from SwitchBot. The latter have the Quick Action option and also a button control for fully opening/closing the curtain.

@SunBeech & @TedTolboom
Just FYI

Thanks. That specific item is not currently part of the driver’s capability set:

The Aqara FP300 sensor reporting issues should be solved with the v1.16.3 update of the app

Is the smoke detector model Aqara JY-GZ-01AQ support or not?

And if support, does it work stable (does it not loose network connections etc)?

I have several of the Aqara Zigbee smoke detectors, connected to my Homey Pro 2026 via the official Aqara app. They have been working perfectly fine, and regular tests have always triggered the Advanced Flow automations I have setup, that trigger the alarm on the other smoke detectors, and sound the two Aeotect Z-Wave sirens I have, and turn on all main lights as well as send a Critical Push notification to my mobile.

They are also the first smoke detectors I have had that don’t constantly trigger with false alarms due to steam/vapour or cooking fumes. (And a fraction of the cost of the Nest detectors that I previously had that were an absolute nightmare for false positives, or dropping connection repeatedly. Also better than the Meross detectors they replaced.)

@TedTolboom Have you been able to confirm the issue? Could it be fixed? Tnx.

Hi,

I’m experiencing an issue with the Aqara Water Leak Sensor T1 on my Homey Pro. The sensor pairs successfully through the Aqara app using the “Water Sensor T1” device, but afterwards it does not report any data. Triggering the sensor by shorting/wetting the two probes does not update the water alarm.

So far, I have:

  • Replaced the original sensor through the retailer, but the replacement has exactly the same issue.

  • Removed and paired the sensor again several times.

  • Kept the sensor awake during pairing by pressing its button every 2–3 seconds.

  • Confirmed that I selected the Aqara Water Sensor T1 driver, rather than Generic Zigbee.

  • Tested the sensor immediately after pairing by shorting the probes.

  • Submitted an Aqara app diagnostics report to Athom: 2924356E.

Athom Support believes this may be a driver issue, because the sensor pairs correctly but the Aqara app does not pass its values to Homey. They also confirmed that the Water Sensor T1 is listed as officially supported in the Homey App Store.

Aqara Support, however, says that the T1 does not officially support Homey and requires an Aqara Hub for reliable data reporting.

Could you please confirm whether the Aqara Water Leak Sensor T1 should work directly with Homey Pro? If so, could you investigate why it pairs but does not report its water-alarm status?

Thanks in advance for your help.

Hello @TedTolboom, I have several Aqara Curtain Driver E1s. The sensors tab in the device tile shows the power source of the driver. I am fairly sure that in the past it would indicate whether it is powered by the internal battery or an external power source, e.g. when charging.

The current app version only seems to show the ‘battery’ state, also when the driver is connected to an external power source and changing.

Would it be possible to restore the prior distinction between the different power sources again in a future version of the Aqara app? Thanks in advance.

Dear Ted,

I am experiencing issues with several Aqara Water Leak Sensor T1 (lumi.flood.agl02) sensors when used with a Homey Pro (2026 / latest generation).

The sensors pair without any problems and are correctly identified by Homey as lumi.flood.agl02. In the Zigbee information screen, the manufacturer, device ID, and other details are displayed correctly. However, after pairing, the sensors do not function as expected:

  1. No battery status is shown.
  2. No water alarm is registered.
  3. Briefly pressing the button on the sensor does not trigger any response or communication update.
  4. Bridging the sensor contacts or exposing them to water does not result in a water detection event.

To rule out defective sensors, I paired the exact same sensors with an older-generation Homey Pro (2023). On that Homey, the sensors work correctly immediately:

  1. Battery status is displayed.
  2. The sensor responds when the button is pressed briefly.
  3. Water detection works as expected.

Both Homey devices are running the same software versions:

  • Homey Firmware: 13.3.0
  • Aqara & Xiaomi Zigbee App: 1.16.3

I have also tested the sensors at very close range to both the Homey and a Zigbee router. This made no difference.

On various Homey and Aqara forums, I have found reports from other users experiencing similar issues where the sensor pairs successfully but subsequently fails to report status updates or water alarms. This leads me to suspect a compatibility or Zigbee communication issue between the Aqara Water Leak Sensor T1 (lumi.flood.agl02) and the newer Homey Pro generation.

Is this a known issue, and if so, is there a solution or workaround available?

Kind regards,

Bert Heemskerk

Hi,

I’m experiencing a strange issue with my Aqara FP300 (lumi.sensor_occupy.agl8) connected directly to Homey Pro using the official Aqara app (v1.16.3).

Environment

  • Homey Pro
  • Aqara App v1.16.3
  • Device: Aqara FP300
  • Model: lumi.sensor_occupy.agl8
  • Zigbee route: 0 → 7 → 8(7 is an aqara smart plug installed in the same room)
  • Firmware: Up-to-date (confirmed through Aqara Hub E1)

What I tested

To rule out a firmware or hardware problem, I:

  1. Removed the FP300 from Homey.
  2. Factory reset the device.
  3. Added it to an Aqara Hub E1.
  4. Updated the firmware (already on the latest version).
  5. Tested the sensor in Aqara Home.

Results in Aqara Home

The FP300 behaves exactly as expected:

  • Presence becomes active when entering the room.
  • Presence turns off shortly after leaving the room.
  • Motion and presence detection are working correctly.

Results in Homey

After removing the sensor from Aqara and pairing it again directly to Homey:

  • alarm_motion remains true
  • alarm_presence remains true
  • Lux, temperature and humidity continue to update normally
  • The device remains online
  • RX counters continue increasing
  • Last Seen updates continuously

Example

I left the room for approximately 25 minutes.

During that period:

  • alarm_motion stayed true
  • alarm_presence stayed true

Even though the same sensor reports absence correctly in Aqara Home.

Developer Tools

Current capabilities:

  • alarm_motion true
  • alarm_presence true
  • measure_temperature 26.9
  • measure_humidity 57.8
  • measure_luminance 134.99
  • measure_battery 75

Additional observations:

  • Last Seen: ~1 minute
  • RX: 182+
  • TX Error: 12

RX continues increasing, which suggests Homey is still receiving messages from the device.

Why I think this is a Homey integration issue

  • Firmware is up-to-date.
  • The FP300 behaves correctly in Aqara Home.
  • Homey continues receiving updates (lux, temperature, humidity, RX counter).
  • Only motion and presence appear to get stuck.

Additional test results:

I re-paired the device after updating firmware via an Aqara E1 hub.

The Zigbee route improved from: 0 → 7 → 5 → 8

to: 0 → 7 → 8

The device continues to communicate with Homey:

  • RX counter increases continuously
  • Last Seen remains below 1 minute
  • Illuminance updates normally

However:

  • alarm_motion remains true
  • alarm_presence remains true

Even after leaving the room for 25 minutes. In Aqara Home the same device reports absence correctly.

Hi,

I’m still facing this issue.

I’m experiencing a strange issue with my Aqara FP300 (lumi.sensor_occupy.agl8) connected directly to Homey Pro using the official Aqara app (v1.16.3).

Environment

  • Homey Pro
  • Aqara App v1.16.3
  • Device: Aqara FP300
  • Model: lumi.sensor_occupy.agl8
  • Zigbee route: 0 → 7 → 8(7 is an aqara smart plug installed in the same room)
  • Firmware: Up-to-date (confirmed through Aqara Hub E1)

What I tested

To rule out a firmware or hardware problem, I:

  1. Removed the FP300 from Homey.
  2. Factory reset the device.
  3. Added it to an Aqara Hub E1.
  4. Updated the firmware (already on the latest version).
  5. Tested the sensor in Aqara Home.

Results in Aqara Home

The FP300 behaves exactly as expected:

  • Presence becomes active when entering the room.
  • Presence turns off shortly after leaving the room.
  • Motion and presence detection are working correctly.

Results in Homey

After removing the sensor from Aqara and pairing it again directly to Homey:

  • alarm_motion remains true
  • alarm_presence remains true
  • Lux, temperature and humidity continue to update normally
  • The device remains online
  • RX counters continue increasing
  • Last Seen updates continuously

Example

I left the room for approximately 25 minutes.

During that period:

  • alarm_motion stayed true
  • alarm_presence stayed true

Even though the same sensor reports absence correctly in Aqara Home.

Developer Tools

Current capabilities:

  • alarm_motion true
  • alarm_presence true
  • measure_temperature 26.9
  • measure_humidity 57.8
  • measure_luminance 134.99
  • measure_battery 75

Additional observations:

  • Last Seen: ~1 minute
  • RX: 182+
  • TX Error: 12

RX continues increasing, which suggests Homey is still receiving messages from the device.

Why I think this is a Homey integration issue

  • Firmware is up-to-date.

  • The FP300 behaves correctly in Aqara Home.

  • Homey continues receiving updates (lux, temperature, humidity, RX counter).

  • Only motion and presence appear to get stuck.

    Additional test results:

I re-paired the device after updating firmware via an Aqara E1 hub.

The Zigbee route improved from: 0 → 7 → 5 → 8

to: 0 → 7 → 8

The device continues to communicate with Homey:

  • RX counter increases continuously
  • Last Seen remains below 1 minute
  • Illuminance updates normally

However:

  • alarm_motion remains true
  • alarm_presence remains true

Even after leaving the room for 25 minutes. In Aqara Home the same device reports absence correctly.

Hi Rens, Just a tip: if you have posted your question already somewhere else on this forum, you can also link to that post by grabbing the link of your original post (via the link icon) and pasting that in your new post:

Get Post Link

Regarding Zigbee routes: please keep in mind that these change constantly. The route that you see in the Homey Developer Tools that a devices uses, is the last known route.

Hi,

Yesterday all my aqara devices sensors on Matter decided to leave the network. I’ve tried to reboot the app, reboot my homey pro (2026), gave no change.

The two FP300 sensors are showing up normaly in the app. I tried to repair the connection to one of them. Homey can’t connect to it.

Any thougts?

Do you have FP300 connected via Zigbee or Matter? If you have connected them via Matter, it’s an issue in Homey since apps don’t control the Matter connections, a Matter device inside an app is just an icon and name.

Thanks,

They are connected with matter.

Hi,

I’m having an issue with a new Aqara Temperature & Humidity Sensor T1 (lumi.sensor_ht.agl02) on Homey Pro 2019 (latest firmware) using Aqara app v1.16.3.

The sensor pairs successfully and shows as Ready and Available, but temperature, humidity, pressure and battery all remain null. I already have another identical T1 sensor that works perfectly on the same Homey.

I’ve tried re-pairing, different Zigbee routes/parents, restarting Homey, and even replaced the sensor under warranty, but the replacement behaves exactly the same.

Diagnostic code: 301fb606-9b17-4591-bc06-299a8f01cd5d

It’s resolved. One of my AP switched the 2.4 ghz network to channel 11. Switched in back to channel 6.

All aquara sensors are connected again.

When i try to add Aqara vibration sensor it shows you dont have this app installed but i do and it shows as unknown zigbee device, can you fix this bug?

Which version of the Vibration sensor do you have, the T1 or non-T1? (The T1 version is not compatible, so doesn’t work/add)