This sounds like the update we’ve all been waiting for… nicely done good sir 
Muchly appreciated
Hi @TedTolboom,
I’m having problems with the Aqara Temperature and Humidity Sensor T1 (lumi.sensor_ht.agl02) on my Homey Pro 2019.
Homey firmware: 13.5.1
Aqara app: 1.18.1
I’ve tested two brand-new T1 sensors from the same 3-pack. Both pair successfully and appear correctly in the Zigbee network, but neither reports temperature, humidity or pressure values.
I’ve tried re-pairing close to Homey (1 metre), keeping the sensors awake during pairing, and restarting the Aqara app.
My older Aqara temperature sensors (lumi.weather) have worked reliably for years.
Diagnostic report ID:
cdbf16d6-fb7d-4c73-abf9-252cddf88ff1
Is this a known compatibility issue with Homey Pro 2019? Is there a solution without replacing the hub or sensors?
Thanks for your help!
Hello, I am having issues pairing my Aqara Wireless Mini Switch to Homey. I have connected this button in the past but did a reset on the Homey last year and am just now getting around to re adding.
Diagnostic Code: 8ef550d8-0907-42b7-bece-36947068ca2d
I have gone through all known troubleshooting steps and can not get this to connect.
Here are the steps I took: restarted homey, removed and re installed aqara app on homey, tried to pair under 2018 and standard model, tried to pair via sole zigbee pairing. None of these have worked.
Is there a trick to getting these to pair?
Hello.
Thank you for adding W100 support.
I’m trying to create a flow for one of my W100 devices (Zigbee) using the buttons, but it gives an error message simply adding the card. It also says “Chose button”, but the list is empty.
If I try creating the flow from the iOS app using the same trigger card, both dropdown lists are empty.
Diagnostic ID: f49c37db-a7ff-45cc-9322-7ab7c34b4ce2
I just released v1.19.1 to the app store test environment.
@Alex7 @Hass this should address your issues.
Changelog:
## Aqara v1.19.1
Requires **Homey v13.1.0** or newer.
Battery alarm replaced by battery level
To align with app store guidelines battery powered devices now only show the battery level (%), no longer a battery alarm.
- Flows using the battery alarm of these devices stop working and need to be updated (e.g. to The battery level dropped below …).
- *Smoke detectors* keep their battery alarm.
Fixes and improvements
- Temperature and humidity sensor T1: improving robustness of reporting after pairing. Existing sensors recover by themselves, no re-pairing needed (pressing the button will accelerate).
- TVOC air quality monitor: more reliable reporting, a stable battery level and a new display unit setting (press the sensor’s button after saving).
- Climate sensor W100: the *button pressed* flow card works again.
- Vibration sensor T1: added the vibration alarm turned on / off flow cards.
- Various fixes for the Dimmer switch H2, smoke detector, wall switches, relay controller and Smart plug EU.
Hi @TedTolboom, any chance of adding the E1 double remote? I have both the single and double remotes and the single remote is recognised (lumi.remote.acn003) but the double (lumi.remote.acn004) is not. Thanks!
lumi.remote.acn004 should be recognized properly.
Can you check / confirm if the manufacturerName is reported as Aqara instead of LUMI (hence it is not recognized properly)?
It reports as LUMI, not Aqara.
Did you try to include based on the v1.19.1 version in test environment (see link above)?
Version v1.19.1 is released to the app store:
I have installed the test version now. The single rocker WXKG16LM is recognised correctly, very happy with that! The double rocker WXKG17LM however can’t be added, it errors halfway through the setup. It won’t even be added as a generic Zigbee device. Before I installed the test version, it was added as a generic device.
Restart Homey and wait until fully loaded, pull out the battery of the double rocker and drink a coffee (wait for a few minutes) and then install the battery and retry to add the switch.
@TedTolboom how is the W600 testing going on your side? I got 5 of them the other day and unfortunately have serious issues. Not sure if it is related to the Homey app or if I have hw issues at the radiators.
The radiators/valves frequently indicate that they are not heating in Homey, while they are heating at the physical radiator (often they are at or above the setpoint value when this happens read directly on the valve, making me suspect a hw issue). Have tried recalibrations, reseating etc and I am running out of ideas (no adapters involved as they fit directly on the radiators). Sometimes they also indicate heating in homey while no heating happens at the radiator. I am running them at zigbee at the moment, but seems like an Aqara hub is required to change them back to Matter/thread so can not check if that improves things (I could change them over to zigbee from matter/thread without a hub so really strange). These will go back to the vendor and I will return to the semi-semi-reliable Netatmo valves if the sitation does not improve.
Did you test based on v1.19.x, as just released today? It does include quite some updates to the W600 thermostat driver.
It is still possible to switch back from Zigbee to Matter. You need to remove the device from Homey, open the Aqara (iOS or Android) app and with Bluetooth enabled it should detect the device automatically. It will then show an option to switch between Thread or Zigbee.
No Aqara Hub required.
Thank you. I use 1.19.1 as released today.
I did remove the device from Homey and even restarted Homey thereafter to make sure it was gone from the zigbee stack. When trying to add the device in the Aqara Android app it did not detect it automatically and tried to add the device both through matter code and QR. Never reached the mode switch that appared when the device came from the factory. Guess anyway that zigbee vs matter just deals with communication and should not have any effect on temp regulation and operation as such (?)
Edit: I may start to see some system in the madness. It seems like these valves systematically close heating when the temp reaches 2 degrees above the actual set point(!), heating sets in when below same thereshold. I have set them to +2 offset and will observe them for a few days more and come back to you, but that is the closest I am to seeing a pattern so far. Valve position tends to move to 0% when around 2 degrees above setpoint. As a sidenote, they also immidently behave like they should after calibration and also turn down heat when set to 5 degrees (off) so that actually reduces the likelihood of the hw hypothesis (valve is clearly able to open and close by radiator pin). Thanks for your patience on this issue.
Did some more testing. I think I am able to reproduce the issue quite consistently now. The w600 heats up 2 degrees celcius more than the set point temp in zigbee mode (have not tested with Matter). E.g. in order to get 23 degrees in the room you need to set the temp to 21 in Homey (or directly at the valve). Offset is not at all relevant for this. You can hopefully reproduce or falsify by setting the valve to 22 and it will likely close at uncomfortable 24 degrees. This affects reliability in Homey as it shows that heating is turned off when it is not, and will give less comfort. If this is reproducable the app could compensate or we need to set temps 2 degrees below desired with the W600 in all flows (a somewhat dirty workaround). I for one would prefer the added reliability above what I suspect is a “battery-preserving feature” from Aqara. Hope someone else with W600 can reproduce this and I am in a good location to test app editions myself as we are in the heating season in Northern Scandinavia.
Steps to Switch the Protocol
- Initial Pairing (Thread mode):
- Pull the battery tab on the W600 to turn on the display.
- Open the Aqara Home app (with Wi-Fi and Bluetooth enabled) and add the device, or pair it initially in its default Thread/Matter state.
- Factory Reset (if required): <<**************
- If you need to re-configure the device, press the device button 2 times and then hold it for more than 10 seconds to restore factory settings.
- Switch Protocol in App:
- Go to the accessory settings inside the Aqara Home app.
- Locate the Switch Protocol option (or select the desired protocol—Zigbee or Thread—during the device setup/re-add flow).
- Confirm the selection and wait for the configuration to apply
When you have completed the indicated Factory Reset button press combination, you should then open the Aqara mobile application and if Bluetooth is enabled on your mobile device the app should automatically detect the W600 and switching protocol between Zigbee and Thread is just a couple of taps in the app and wait. The app guides you through the process.
The most likely reason you are seeing the thermostat heating 2°C above the set temperature is because you have set the offset to +2°C. Please can you confirm what you are using to measure the room temperature, and where the measuring device is located? And that you are seeing this temperature discrepancy when the Homey device Advanced Settings Temperature Offset is set to 0 (zero).
I only ask these questions because I have a couple of these W600 TRV’s and they have been rock solid reliable.
Thank you. I am not that concerned about changing over to Matter anymore as I do not think the issue lies there. The 2 degrees issue is there both with and without onset +2 (it was just something I intially tested). They are at 0 now and everything works (valves open and closes at the temps I want) @TedTolboom when I have set temps 2 degrees below intended. Did you try to set the valve to a temp and check that it closes at the set temp with zigbee (literally listen to the radiator and check valve status % in Homey in all its pure madness)? My hypothesis is that it will close at a temp which is about two degrees above the set temp, which is absolutely not fine as the room will be overheated and that Homey/the current Homey Aqara app will report that heating stopped way before it did. I am very happy to be proved wrong on this.
What conditions were in place before the “new release” (of what? Aqara app or Homey firmware?), that were provided by the Homey Aqara app for a contact sensor?
