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

hi,

I use Aquara door and window sensors, basic version. I switch some homey’s of during the night. trouble is I have to repair the sensors now and then. old version every time, I bouoght new ones, there it is about once a week. still annoying .. any tip to prevent this?

Any chance the Aqara Shutter Switch H2 will be supported?

No long able to Pair T1M ceiling light with my Homey Pro Mini.

Apps are up-to-date

Homey is up-to-date

After putting the ceiling light into pair mode, Homey fails to finalise the handshake. Error message below :backhand_index_pointing_down:t3:

Any ideas what the problem could be?

It was paired in the past.

Have you tried using this app to see the health of your Zigbee network?

It would also help the app developers a great deal if you could try a pairing and then after it failed go to the settings in your Homey mobile app, navigate to the Aqara app, and generate a Diagnostic Report n copy and paste the report ID here for them.

Example output of the app’s widget in a Dashboard:

Thanks for your help.

Here is the report I’d of the diagnosis report I’ve just created.

135b54b2-6fd8-49dc-90c4-8536a2cb5a5d

I’ve installed the app, all devices seem to be connected ok. The T1M ceiling isn’t displayed, I’ve not been able to pair it.

Just a thought, but have you tried moving your Homey to the same room, and as close as possible to the light. Then do a factory reset on the light, turn the light on and off five times consecutively (on for 1 second, off for 1 second for each cycle) and then try to pair the light again. But make sure there isn’t a half-paired residual device (I’ve had a ghost device from a failed pairing block subsequent attempts before). Also, how many Zigbee devices do you have paired to your Homey?

Will the fp400 be added anytime soon?

Hello,

I am also interested in integration on homey, I bought the FP400, I tried to integrate it on the app aqara, all this goes well, but he asks me for an additional hub

Thank you in advance for your feedback

I allow myself to add that integration can be done live, via new device matter, but it is seen as a simple detector with brightness, it lacks the areas and the AI with the app aqara

Thank you in advance for the full integration

Yann

Question about active Zigbee reads for Aqara SP-EUC01

Hello @TedTolboom, @kasteleman, @baskiers, @robinbolscher, and other Homey developers,

I am investigating the Aqara SP-EUC01 EU Smart Plug on Homey Pro Early 2019.

Device details:

  • Model: lumi.plug.maeu01

  • Homey driver: plug.maeu01

  • Homey firmware: 13.5.1

Athom confirmed in my ticket 155132 that the Homey App SDK supports active Zigbee attribute reads from a device driver.

I created a temporary read-only SDK test driver and paired the plug with it. The driver successfully performs live reads from:

Endpoint 21
Cluster: Analog Input
Attribute: presentValue

The results were:

  • heater OFF: approximately 0
  • heater ON: approximately 137 W
  • repeated reads every 60 seconds returned values around 136–139 W
  • all reads completed without errors

The standard Endpoint 1 Electrical Measurement activePower attribute was readable but always returned 0.

My questions are:

  1. Can the official Aqara Homey app actively read EP21 / AnalogInput / presentValue while keeping the existing onoff, measure_power, and meter_power functionality?

  2. Is the Aqara app currently maintained by Lumi Technology, Ted, or another developer?

  3. Would an active-read implementation for this device be technically acceptable for the Aqara app?

  4. Has anyone already implemented or investigated this endpoint for the Aqara SP-EUC01?

The goal is to obtain reliable live power readings while preserving the existing Aqara app integration and device controls.

I can provide the SDK test project, driver manifest, source code, and complete logs if useful.

Thank you
Petr

I think it’s a ghost device, it’s showing up as an unknown node - router aqara in Zigbee insights. but not in the device list in Homey. Whats the process for removing ghost devices?

'

Only thing I can think of off the top of my head is to check in the Homey dev tools for that device

Will W600 valves be supported in this zigbee app or will the matter implementation give sufficient access to basic when, and, then cards? Stable and reliable connection in matter? Considering to get a few of those if Homey support is reliable.

I have a couple of the W600 (will get more at some point) and asked months ago the same question about Zigbee support, but I never got a reply.

I’ve been using them since in Matter o/ Thread, and they seem reliable and stable enough. They report the current temperature and the set temperature, as well as the battery level. And they allow you to set a temperature offset, heat on/off, and change the set temperature. There might be some additional settings via Zigbee, but nothing that affects their purpose. And all the aforementioned settings (bar the offset, which is in Advanced Settings) are controllable via Flow cards in Thread mode.

Thanks a ton @Drako74 Basically I just need access to set temps (then card), reads of current temp (logic/and cards). Also preferably When cards for temp changes. Can you confirm that those cards are available through matter with these? Also, do the w600 just ramp up temp to max when out of battery or do they use some kind of frost protection when that happens? Are they noisy? Sorry for all the questions. Considering to switch from five annoying cloud-based WIFI Netatmo valves which bring tons of reliability issues. It will be an investment and hope to use a new system for 5+ years at least, preferably with local control and much less annoyances than the cloud-based Netamo has delivered the last five.

Here’s all the Flow cards in Thread mode:

I haven’t got anywhere close to using up the first set of batteries yet in the 7 months I’ve had them… but to be fair, it has been the hottest year ever, so they haven’t had much work to do at all so far.

Virtually silent in operation, or they wouldn’t still be on my radiators, but in little pieces :rofl: ha ha ha

They work great for local control, and sleek looking design too. Seems decent build too. So far very pleased with them.

Version 1.17.0 has just been uploaded to the Homey app store, pending Athom’s approval.

Changelog v1.17.0:

  • Add support for the W100 climate sensor (TH-S04D) in both Zigbee and Matter device protocols. Add support for the Vibration sensor T1 (VS-S01D).
  • Improve occupancy sensor accuracy and reliability for both the FP300 and FP1E occupancy sensors.
  • Improve handling of the external sensor input for the Smart Radiator Thermostat E1.

Hi Ted,

Are there any plans to add the Smart Radiator Thermostat W600 device in Zigbee / Matter protocols in the not so distant future please? That would go nicely with the W100 climate sensor.

Thank you :grin:

The Aqara Floor Heating Thermostat W500 and the Aqara Radiator Thermostat W600 are next up (in the works)…

Hi @TedTolboom

I’m experiencing severe intermittent button-event loss with multiple Aqara H2 EU switches connected directly to Homey Pro 2023 via Zigbee.

I have submitted an Aqara diagnostic report after reproducing the issue:

Diagnostic report ID: 8d41a6d1-e9c7-4799-9feb-4802ae28e3c4

I did some controlled testing:

  • The issue affects both H2 switches with neutral (Zigbee routers) and without neutral (end devices).
  • On one mains-powered H2, Developer Tools shows it as a router with a direct route to Homey (0 → 4) and 0% TX errors.
  • With 50 physical single presses on this H2, Homey registered 28/50.
  • Every press that was registered by Homey triggered the corresponding Flow correctly. The missing presses produced no button event at all.
  • Rebooting Homey did not resolve the issue.
  • Completely disabling all 2.4 GHz Wi-Fi radios did not improve it. (To determine interference)

I also did an A/B test using an Aqara G5 Pro:

H2 → Zigbee → G5 Pro → Matter → Homey: 50/50 presses registered.

A few of those had a slight delay, but none were lost.

So the problem seems specific to the direct H2 → Homey Zigbee path rather than the switches themselves or the Flow.

Could this be something to look into?

I can reproduce the issue consistently and perform additional tests if needed.

Cheers and thanks in general for good Aqara/Homey support :blush: !