Hey there,
I’m using the Aqara Temperature Sensor for a long time now and I’m absolutely happy with it.
On Amazon Prime Day i’ve now bought several Aqara E1 Thermostats and added them to homey without any problem.
I know, that it would be possible to combine the Sensors and the Thermostats to get extern Temperatur values, but found no way to do this in homey.
Do you have any ideas for a work around without using an Aqara HUB?
Would be thankful for any ideas…
Best regard,
Marco
Following this one. I have been trying to find a solution to same problem for a while. No luck.
Any news on this? I bought homey pro because I saw aqara as an official integration… Would be a shame if this isn’t possible, might be forced to return it.
Why do you think anyone here would care if you return it?
Besides that, which issues did you have when trying to add the thermostat knob? (Did you even try?)
According to the app store it’s supported:
I don’t have an issue with pairing the thermostat… I just am not able to use the external aqara temperature sensor as temperature source for the thermostat
I have the same problem.
I even bought an Aqara Hub M2, and using the Hub, I was able to set up a heating schedule (high temp day/low temp night). I was also able to command the thermostat to use one spesific Aqara Temperature and Humidity Sensor. The downside was that as I paired the Aqara Smart Radiator Thermostat E1 to the Aqara Hub, Homey Pro lost contact with them.
It’s a shame that the Aqara app is not able to do the same as the Hub - setting up heating schedules, checking logs and more…
Since I’m unwilling to have to use extra apps to control my smart home, I decided to remove the thermostats from the app and re-pair them to Homey, and to control the thermostats using flows.
One flow sets low temperatures at 2230 at night, another flow sets high temperatures at 0700 in the morning. However - quite a few of the thermostats reverts to high temperatures for an unknown reason, one just half an hour after being commanded to low temp, another one hour after being commanded to low temp (see picture).
Checking the log for on of the thermostats gives nothing on commanded temperatures and what commanded it,
My Ikea app controlling one of my light bulbs, tells me what commanded the light on and off in the log:
Why can’t the Aqara app do the same? I would like to know if the temperature reverted to old setting by way of an error, or if it’s a flow doing it…
It seems to me that the Aqara app in Homey needs quite a bit of work to make the Aqara Smart Radiator Thermostat E1 and the Aqara Temperature and Humidity Sensor T1 “smart”.
Seeing the slow progress on this thread, I don’t have much hope of anything happening soon.
It’s not up to the apps to create these timeline notifications, that’s handled by Homey itself.
When the notification uses the app name as the source of the action, it means that the app received a message from the device that it performed the action. So there’s some external reason why your thermostat is doing this.
I’m sure you’re right. Nevertheless, this is information that would be nice to have in order to find out why it’s not working the way I would like.
The interesting thing is, I’ve googled to see if anyone out there on the big interwebs has encountered (and found a solution to) this problem, and there is very little to be found. Nothing that wold help me, at least…
The OP’s question still stands unanswered.
The app has no idea why the device told it it did something 
At the moment Homey FW version 12.3.x (having THE essential information needed for this feature) hits stable, I will release the update to be able to provide a temperature reading from an external sensor as flow card input.
Forget the app - all I need is a log entry in Homey telling me if or when Homey commanded a temperature change. I don’t care if it’s the app reporting to Homey or if Homey keeps a record. I just want to see if a command has been issued by Homey (a schedule, flow or whatever).
I guess you’re not familiar to zigbee basics yet:
This is completely normal zigbee behaviour.
When you pair an already paired (to Homey) zigbee device to an other zigbee controller (Aqara hub), it resets (leaving the (Homey) zigbee network) and connects to the new (Aqara) zigbee controller.
A device can join only one zigbee network at a time.
Multiple zigbee controllers and their mesh networks at one location, are unaware of eachother. You can’t combine them.
Just discuss your requests with the developer I’d like to suggest, Roy 
Contact info is present at the homey.app store app page.
I’m sure you’re right, @Peter_Kawa, in that only one controller can control an zigbee unit at a time, but when I wanted to use a Phillips Hue Motion Detector, I first had to set up a Phillips Hue hub and connect through that. I thought it would work the same with the thermostats. Clearly not.
I’ve informed the developer, thanks for the tip 
YW.
I don’t get it yet.
Only when that particular Hue sensor wasn’t supported by the Homey “Phillips Hue without-the-bridge app”, indeed you’ll have to use a Hue hub as in-between, when the Homey “Phillips Hue app” does support that sensor.
The thermostat knob was supported by the Homey Aqara app apparently, and now you have paired it to the Aqara hub.
Why shouldn’t the knob connect to Homey now…
Did you try adding it as Matter device?
Certain Aqara hubs publish their connected zigbee devices as Matter devices.
@Peter_Kawa
The thermostat knob was supported by the Homey Aqara app apparently, and now you have paired it to the Aqara hub.
As I wrote in my first post, I tried the hub and then dropped it. It’s no longer connected, all my thermostats are back in Homey.
I’m stepping out of this conversation.
Hii! Little question, i see the “external temp sensor” setting in the advanced settings tab.
But when set to external, i don’t see the flow card where you can input the sensors value.
Is this under development or do i need to activate that somewhere? (app already restarted)
Has the stable Homey firmware 12.3.x already been released?
Stable is out:pray:
See v1.12.1, currently in the test environment of the app store:
