Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

If you were buying a new thermostat, which would you get?

  • Ecobee

    Votes: 41 67.2%
  • Nest

    Votes: 14 23.0%
  • iDevices

    Votes: 1 1.6%
  • Other

    Votes: 5 8.2%

  • Total voters
    61
I have a Nest thermostat, Wemo switches, MyQ garage door opener and a dropcam. None of these devices are compatible with Homekit, in fact I've never actually seen it in use. Does anyone know if this will only work with Apple/partnered products or will it eventually be more ubiquitous?
 
I have a Nest thermostat, Wemo switches, MyQ garage door opener and a dropcam. None of these devices are compatible with Homekit, in fact I've never actually seen it in use. Does anyone know if this will only work with Apple/partnered products or will it eventually be more ubiquitous?

Nest is not currently compatible with HomeKit. Being they are owned by Google, it remains unknown if they will ever add that feature. WeMo is pretty content to be stand-alone, but they do integrate nicely with the Amazon Echo for voice control. However, Belkin is on-record as saying they do plan to "add HomeKit" -- but I assume their current hardware doesn't have the enclosed chipset required. So, if you did want HomeKit WeMo hardware down the road, expect to have to buy new devices.

As for the Chamberlain MyQ, you should read this:
https://myqcommunity.chamberlain.com/chamberlainmyq/topics/homekit-setup-and-integration
Bottom line there is that nobody really knows for sure if the current MyQ will be compatible via firmware update or not. Either way it will need the code to scan/type into your iOS device to add it to HomeKit. So will it need new hardware, or not the case if you have latest hardware version? Who knows... as of right now, however, there is no official MyQ product that has been officially unveiled as HomeKit compatible by the company, so I'd tread lightly.

Hope this helps you.... oh and if you want the list of compatible HomeKit devices from Apple's site, go here:
https://support.apple.com/en-us/HT204903
 
Nest is not currently compatible with HomeKit. Being they are owned by Google, it remains unknown if they will ever add that feature. WeMo is pretty content to be stand-alone, but they do integrate nicely with the Amazon Echo for voice control. However, Belkin is on-record as saying they do plan to "add HomeKit" -- but I assume their current hardware doesn't have the enclosed chipset required. So, if you did want HomeKit WeMo hardware down the road, expect to have to buy new devices.

As for the Chamberlain MyQ, you should read this:
https://myqcommunity.chamberlain.com/chamberlainmyq/topics/homekit-setup-and-integration
Bottom line there is that nobody really knows for sure if the current MyQ will be compatible via firmware update or not. Either way it will need the code to scan/type into your iOS device to add it to HomeKit. So will it need new hardware, or not the case if you have latest hardware version? Who knows... as of right now, however, there is no official MyQ product that has been officially unveiled as HomeKit compatible by the company, so I'd tread lightly.

Hope this helps you.... oh and if you want the list of compatible HomeKit devices from Apple's site, go here:
https://support.apple.com/en-us/HT204903
Thanks for the comprehensive reply. It's not really a big deal without SIRI integration but it would be nice, IMO as long as Apple forces people into their ecosystem with it, it will always be limited. It would be nice to see them treat it like the app store where anyone can make their products compatible as long as they fit within Apple's guidelines.
 
Thanks for the comprehensive reply. It's not really a big deal without SIRI integration but it would be nice, IMO as long as Apple forces people into their ecosystem with it, it will always be limited. It would be nice to see them treat it like the app store where anyone can make their products compatible as long as they fit within Apple's guidelines.

Apple allows anyone in, but you have to follow their rules to play in their sandbox. This means not just hardware but software. It is with this in mind that requires the chipset to become MFi certified. Additionally, as HomeKit is still right now in the early stages, it wasn't until iOS 9 released that certain features even "came live" within the HomeKit spectrum. As they improve the core aptitude of the product, so too can the developers make their devices work better.

Just today, for example, Lutron updated their app to allow for more support of the HomeKit platform. Another example is Elgato, who has Bluetooth HomeKit devices, and will be releasing a new firmware update soon to allow those devices to become triggers for events. So again, its not so much the limit of the developers as it may be Apple's slow coming to market with what iOS even supports, sadly.
 
Thanks for the comprehensive reply. It's not really a big deal without SIRI integration but it would be nice, IMO as long as Apple forces people into their ecosystem with it, it will always be limited. It would be nice to see them treat it like the app store where anyone can make their products compatible as long as they fit within Apple's guidelines.

And it's not just the chip to work with HomeKit but also processing power. Apple is requiring a pretty heavy level of security to work with HomeKit, so it means usually complete hardware redesign, hence the reason there aren't too many compatible devices yet. For example, August is just taking preorders for their new HomeKit lock, which is nice cause they fixed a lot of design flaws.

My biggest concern right now is because of the early stages of software development, there are glitches, so I'm only moving forward with non-life concerning devices, lights and thermostats. I'm not ready to jump on the lock or garage openers since for example, this morning I woke up and my lights were on and ecobee set to home. I have the Home app setup to turn on my lights and set my ecobee to home when I arrive home but clearly HomeKit I arrived home even though I was home, sleeping.

I don't want this kind of glitch to happen where my doors suddenly unlock, cause that's messed up. In a year, HomeKit will be robust system, just a bunch of glitches to work out.
 
Last edited:
And it's not just the chip to work with HomeKit but also processing power. Apple is requiring a pretty heavy level of security to work with HomeKit, so it means usually complete hardware redesign, hence the reason there aren't too many compatible devices yet. For example, August is just taking preorders for their new HomeKit lock, which is nice cause they fixed a lot of design flaws.

My biggest concern right now is because of the early stages of software development, there are glitches, so I'm only moving forward with non-life concerning devices, lights and thermostats. I'm not ready to jump on the lock or garage openers since for example, this morning I woke up and my lights were on. I have the Home app setup to turn on my lights and set my ecobee to home when I arrive home.
Fair points. I only recently got the MyQ garage door kit and have to say that I'm pretty impressed with it. It works with my existing door opener and gives us piece of mind on whether or not we've forgot to close it. I'm with you on the lock though especially considering we rarely use the front door, not sure if I want to go there just yet.
 
  • Like
Reactions: knemonic
Nest is not currently compatible with HomeKit. Being they are owned by Google, it remains unknown if they will ever add that feature. WeMo...

Did you notice on Home app's website they are selling something that is supposed to allow you to setup non-HomeKit devices with HomeKit? I didn't have much time to read it, and it's probably more than most are willing to bite off, but interesting none the less.

Curious, have you had this issue: when I arrive home, I have a scene where I say I'm back, turns on the lights and sets ecobee to home. But I noticed before I went to bed, the ecobee hadn't automatically continued with my normal schedule for sleep mode. And I have the setting in my ecobee online account to "hold till the next scheduled event." So it should jump to the next scheduled event even though it's holding from a scene. Any ideas?
 
Last edited:
Curious, have you had this issue: when I arrive home, I have a scene where I say I'm back, turns on the lights and sets ecobee to home. But I noticed before I went to bed, the ecobee hadn't automatically continued with my normal schedule for sleep mode. And I have the setting in my ecobee online account to "hold till the next scheduled event." So it should jump to the next scheduled event even though it's holding from a scene. Any ideas?

This is an "issue" -- I would agree. But apparently, after talking to Ecobee, this is intentional. Which sucks. I had the EXACT same complaint, and they told me the unit is working as-intended. When you use HomeKit to set your thermostat to Home/Away/Asleep using those 4 scenes created by Ecobee, it sets it to that mode INDEFINITELY!!

So I had the same issue. I have my Ecobee3 set precisely the same way ("hold till next scheduled event")-- but that only works if you change the temp, or auto home/away is functioning, etc. When you use HomeKit to say you're home, or "good night" for example, it sets into that mode for ever and ever. So if you want to use it, you have to basically use it 24/7/365.

I guess they figured you'll always tell Siri "good night" followed by "good morning" -- but the problem there is if you forget one morning, your HVAC will be "stuck" in night/sleep mode. Again, I had the same issue, the same complaint, and contacted Ecobee. Their reply was simply they would consider this as a request for the future. For the moment, however, changes to those modes via HomeKit will remain "indefinite" (sadly)
 
This is an "issue" -- I would agree. But apparently, after talking to Ecobee, this is intentional. Which sucks.

Ugh. They're stupid, I don't want to talk to Siri literally every time a change needs to be made when it's something I want to happen on a daily basis, it defeats the purpose of it being convenient then. That's even more work if you didn't have HomeKit, having an old thermostat, since that would be set to a schedule and you'd rarely change it. Buttheads.

So the truth is this, if you want to achieve what we're talking about, we really need mimic all the schedules we have setup in ecobee in the Home app then. That's work but I guess once it's done it's done.

It's cluttered but for every scheduled change, I've found its best to first create the hue scene in the hue app (since it's easier to make light schemes in there than in Home), hue "Siri" it, add one of the four comforts settings to it in ecobee then go back to hue and re-Siri it cause I've noticed ecobee breaks the hue Siri association after you've added the ecobee comfort setting to it.

But what is frustrating after what we've talked about above, when I add a custom setting to a scene in ecobee, I can't choose which sensor to read temp off of. I created two additional comfort settings on their website, but those don't show up in the ecobee scenes, cause they only give you those four options, the custom only giving you temp and fan control, and not sensor control, which is stupid. See, I want a pre-sleep mode, which I have scheduled for an hour before I go to bed, which knocks the home setting down a degree, and then Sleep mode is one more degree down (70>69>68), so I ease into the cold nights (Midwest gets really cold). But because I can't choose my self created comfort modes in the ecobee scene settings, and I can't choose the custom setting, cause I need to use the remote sensor (which is in the master bed upstairs), I don't know what sensor it is using. I assume either the actual ecobee or maybe both.

That's probably a good question then, when you use the custom comfort setting in the ecobee scenes, is it using all sensors, or just the main one?

But my ultimate question is this, I might as well mimick my entire schedule in the Home app, which negates the auto away mode I assume or simply just not use HomeKit with the thermostat at all, so I get auto away and just setup the schedule in ecobee. This warrants two questions, have you found the custom setting in Home to choose which sensor the temp is pulled from and if using the Home app, is there a setting that still would allow the auto away when in a holding pattern set through the schedule of the Home app?

Ha, sorry for the long one. Glad someone knows what the crap is going on.
 
This is an "issue" -- I would agree. But apparently, after talking to Ecobee, this is intentional. Which sucks.

I guess one could get similar results by using triggers to achieve an auto away for the ecobee in Home but I've found those are hit and miss in the few days I've been using them. Sometimes it doesn't throw on the lights when I get home as a trigger. But frankly the auto away ecobee feature isn't that reliable as well, so maybe I'd get similar results. I'll say this, the nest did way better with auto away than the ecobee does.
 
That's probably a good question then, when you use the custom comfort setting in the ecobee scenes, is it using all sensors, or just the main one?

But my ultimate question is this, I might as well mimick my entire schedule in the Home app, which negates the auto away mode I assume or simply just not use HomeKit with the thermostat at all, so I get auto away and just setup the schedule in ecobee. This warrants two questions, have you found the custom setting in Home to choose which sensor the temp is pulled from and if using the Home app, is there a setting that still would allow the auto away when in a holding pattern set through the schedule of the Home app?

Ha, sorry for the long one. Glad someone knows what the crap is going on.

All of these are great questions and concerns, and sadly I don't have answers to these. Obviously the Ecobee3 lets you set Home, Sleep or Away. So in those situations it would use the sensors you've decided in your comfort settings. However, for the "custom" option (which is basically what you're asking about here) I'd have to assume that it is reading ALL sensors. Or perhaps JUST the thermostat (main)?? But again this is truly speculation here. You'd have to reach out to them to verify.

As for the other questions regarding using the Home app (which again is just modifying the HomeKit database and nothing more)-- I don't believe there is any way to make the "auto" home/away sensing of the thermostat work in the way you want. HOWEVER--- if you go into the Home app, triggers, characteristics, and look at your thermostat-- you'll see that you can select the "motion detected" option for each of your sensors. I -did- try (at one point) to make my master bedroom's ecobee3 sensor trigger the lights in there but that didn't work. Again I'd reach out to Ecobee3 to ask them about this, but maybe at some point that will work-- my testing showed it did not.

If it did work, you could make it so when no thermostats saw any motion, it thoughts you were away? I dunno... all in all, reach Ecobee and let us know what you find-- this is good questions!!
 
All of these are great questions and concerns, and sadly I don't have answers to these. Obviously the Ecobee3 lets you set Home, Sleep or Away. So in those situations it would use the sensors you've decided in your comfort settings. However, for the "custom" option (which is basically what you're asking about here) I'd have to assume that it is reading ALL sensors. Or perhaps JUST the thermostat (main)?? But again this is truly speculation here. You'd have to reach out to them to verify.

As for the other questions regarding using the Home app (which again is just modifying the HomeKit database and nothing more)-- I don't believe there is any way to make the "auto" home/away sensing of the thermostat work in the way you want. HOWEVER--- if you go into the Home app, triggers, characteristics, and look at your thermostat-- you'll see that you can select the "motion detected" option for each of your sensors. I -did- try (at one point) to make my master bedroom's ecobee3 sensor trigger the lights in there but that didn't work. Again I'd reach out to Ecobee3 to ask them about this, but maybe at some point that will work-- my testing showed it did not.

If it did work, you could make it so when no thermostats saw any motion, it thoughts you were away? I dunno... all in all, reach Ecobee and let us know what you find-- this is good questions!!

I'm betting the reason the motion detection didn't work with your sensor is the sensors are really slow to informing the main of motion and temp. I think the main will ping it randomly or something like that, but it's not in constant communication with the main so having it turn on your lights is hit and miss I'm sure.

The thought I had to achieve an auto away with Home is setup a trigger for when I leave the geofence, and if all my lights are off (I'd probably need to add one to my upstairs bedroom since I don't have one there yet to avoid auto away if someone is upstairs) and the condition is all lights have to be off. Then it would set an away scene. Honestly this might be more reliable than waiting for ecobee to realize I'm not home, I noticed it took it over 2 hours to kick in auto away after leaving (unless my cat was throwing it off, but she stays in other rooms mostly).

I will say this, I think Apple needs to take a much more active role with partners with regard to their software working better with others, cause all this promotional stuff showing dudes saying I'm home Siri and all their stuff turning on and switching modes is misleading if people have to go through all this work to get at best semi-reliable experiences for hundreds if not thousands of dollars worth of electronics. If not, it could fail before it even becomes decent for the rest of us.
 
I'm betting the reason the motion detection didn't work with your sensor is the sensors are really slow to informing the main of motion and temp. I think the main will ping it randomly or something like that, but it's not in constant communication with the main so having it turn on your lights is hit and miss I'm sure.

The thought I had to achieve an auto away with Home is setup a trigger for when I leave the geofence, and if all my lights are off (I'd probably need to add one to my upstairs bedroom since I don't have one there yet to avoid auto away if someone is upstairs) and the condition is all lights have to be off. Then it would set an away scene. Honestly this might be more reliable than waiting for ecobee to realize I'm not home, I noticed it took it over 2 hours to kick in auto away after leaving (unless my cat was throwing it off, but she stays in other rooms mostly).

My thoughts were the same-- it doesn't read those thermostats constantly, so it might not have triggered from there because of this. I never did really give it "tons" of time to check for motion but i still question if that works. For example right now I reached out to Elgato about their Eve Door/Window sensor. It is Bluetooth, and won't trigger any lights. Even though you can select such within the Home app, it won't work that way. Why? Eve devices aren't set to "push" right now-- but with their next firmware update, they can become push/trigger devices. So that is nice, but right now, isn't the case. Perhaps that, coupled with the "slow/infrequent updates" are the cause of the issue with the Ecobee3.

Your idea of lights being off/etc would be smart. Though at that point, why not just use your geofence? You could set your lights to go off and your thermostat to go away at same time. OR do you have same issues as me, spouse at home? I've just come to decide that with the two of us we can't use certain features with geofencing. I just use "arrive home" and that way it turns on lights even if she is home. And then I have all Lutron Caseta switches, so when I leave the house it "warns" me (Apple Watch and/or iPhone) that stuff was left on, giving me a quick button to turn it all off-- and usually i know if that is okay, or if she is home still, so it works nicely for us.

PS: My cats (x2) kept setting off the auto-home feature during the day. I setup a link between Ecobee3 and IFTTT so that it would notify me when the schedule gets overwritten (this is good but polling there is again not instant, could be 10+ minutes before you know)-- still it gave me visibility to see what was happening. And from there I was able to use my Nest Cam to see-- sure enough cats were tripping the sensor. I emailed Ecobee about that, too-- the problem is ALL sensors (motion) work for auto-home/away features, and the cats only ever tripped just one-- but no way to exclude it sadly. Even if excluded from "away" mode, the motion sensors are ALL always part of "auto home" sensing, boo-hiss!!!
 
My thoughts were the same-- it doesn't read those thermostats constantly, so it might not have triggered from there because of this. I never did really give it "tons" of time to check for motion but i still question if that works. For example right now I reached out to Elgato about their Eve Door/Window sensor. It is Bluetooth, and won't trigger any lights. Even though you can select such within the Home app, it won't work that way. Why? Eve devices aren't set to "push" right now-- but with their next firmware update, they can become push/trigger devices. So that is nice, but right now, isn't the case. Perhaps that, coupled with the "slow/infrequent updates" are the cause of the issue with the Ecobee3.

Your idea of lights being off/etc would be smart. Though at that point, why not just use your geofence? You could set your lights to go off and your thermostat to go away at same time. OR do you have same issues as me, spouse at home? I've just come to decide that with the two of us we can't use certain features with geofencing. I just use "arrive home" and that way it turns on lights even if she is home. And then I have all Lutron Caseta switches, so when I leave the house it "warns" me (Apple Watch and/or iPhone) that stuff was left on, giving me a quick button to turn it all off-- and usually i know if that is okay, or if she is home still, so it works nicely for us.

PS: My cats (x2) kept setting off the auto-home feature during the day. I setup a link between Ecobee3 and IFTTT so that it would notify me when the schedule gets overwritten (this is good but polling there is again not instant, could be 10+ minutes before you know)-- still it gave me visibility to see what was happening. And from there I was able to use my Nest Cam to see-- sure enough cats were tripping the sensor. I emailed Ecobee about that, too-- the problem is ALL sensors (motion) work for auto-home/away features, and the cats only ever tripped just one-- but no way to exclude it sadly. Even if excluded from "away" mode, the motion sensors are ALL always part of "auto home" sensing, boo-hiss!!!

Exactomondo, my girlfriend works from home, so I want to make sure the lights don't turn off when I leave. Your idea with the lutron switches is an interesting idea. All I would need is one to achieve this connected to a light we use frequently. Curious, the button you push, does it set a scene in general or just turn off those switches?

I did a little digging. I've concluded you can't choose which sensor to use for your set temp. I created three test scenes, each using the home, away and sleep modes. Home I have set only to the ecobee sensor, away the ecobee sensor and sleep the remote sensor. I then looked at each of the scenes in the Home app and at all the variables and what did I notice? They all were the same. So I think this means the Home app is not giving us access to sensor information, that is to use a specific sensor to heat/cool a home by.

This is crummy cause I'd like to be able to duplicate my exact schedule in the Home app since the home app, regardless of someone or something changes the scene or temp at the ecobee will still run its schedule, since it's not subject to the rules set forth in the ecobee app, not permanently holding. I could easily mimick what my comfort settings are in the Home app (Create a scene, choose a temp and then create a trigger for a specific time) except I wouldn't be able to choose which sensor to base the temp off of.

I have a feeling though we'll get much faster results by contacting the Home app developers since they may be able to simply change their app to show more HomeKit database info, or maybe they're already working on it.

I wonder if there is a way to use the motion sensors with IF to put the ecobee into away mode automatically. I've noticed it takes the ecobee a long time to put itself into away mode (I'm really curious what their variables are for auto away) but maybe we could get the ecobee to tell IF that if both motion sensors are unoccupied and kick in the away mode. The problem with this is the sensors are in only two spots, for me if someone is watching tv in the living room, the ecobee is in the dining room doesn't detect motion in there. So more sensors are needed. But the ecobee sensors aren't cheap and you'd rather have a lot of them to get much more accurate results, one in the kitchen, offices, etc (and either it's the sensors that are slow or the ecobee itself in updating the occupancy status, hence a true motion sensor would be more ideal). I'm gonna see what is out there in this regard. The motion sensor might not even need to be HomeKit, since it would simply connect to IF when it detects no motion then IF would send ecobee the command to go autoaway.

Another approach could be I utilize cameras for motion sensors (in addition to having them for security). I actually have a Mac mini setup in my living room for all sorts of purposes (FaceTime, entertainment, it's also my desktop if I need to work in the living room and when I need a more desk type setup, I ran Ethernet to another room and have a thunderbolt adapter to hdmi which plugs into a hdmi to Ethernet adapter which mirrors my Mac into a second display, so I can use my Mac at a desk and in my living room, htpc and desktop for the price of one).

But I had a camera laying around so I figured I'd play with that for security purposes and I've only played with two software so far but one, sighthound has IF integration. The problem I have with that software is I can't have it tell IF if there is no motion for 30 min, set ecobee to auto away, since it only will send an event to IF when something happens. But IP cameras aren't super expensive and serve more purpose than simply detecting motion, so a little premium price might be justifiable (and I simply would run Ethernet to the areas I want to use them).

Lots of options to say the least.
 
My thoughts were the same-- it doesn't read those thermostats constantly, so it might not have triggered from there because of this. I never did really give it "tons" of time to check for motion but i still question if that works. For example right now I reached out to Elgato about their Eve Door/Window sensor. It is Bluetooth, and won't trigger any lights. Even though you can select such within the Home app, it won't work that way. Why? Eve devices aren't set to "push" right now-- but with their next firmware update, they can become push/trigger devices. So that is nice, but right now, isn't the case. Perhaps that, coupled with the "slow/infrequent updates" are the cause of the issue with the Ecobee3.

Your idea of lights being off/etc would be smart. Though at that point, why not just use your geofence? You could set your lights to go off and your thermostat to go away at same time. OR do you have same issues as me, spouse at home? I've just come to decide that with the two of us we can't use certain features with geofencing. I just use "arrive home" and that way it turns on lights even if she is home. And then I have all Lutron Caseta switches, so when I leave the house it "warns" me (Apple Watch and/or iPhone) that stuff was left on, giving me a quick button to turn it all off-- and usually i know if that is okay, or if she is home still, so it works nicely for us.

PS: My cats (x2) kept setting off the auto-home feature during the day. I setup a link between Ecobee3 and IFTTT so that it would notify me when the schedule gets overwritten (this is good but polling there is again not instant, could be 10+ minutes before you know)-- still it gave me visibility to see what was happening. And from there I was able to use my Nest Cam to see-- sure enough cats were tripping the sensor. I emailed Ecobee about that, too-- the problem is ALL sensors (motion) work for auto-home/away features, and the cats only ever tripped just one-- but no way to exclude it sadly. Even if excluded from "away" mode, the motion sensors are ALL always part of "auto home" sensing, boo-hiss!!!

I was just searching the net a little and came across this, have you played with it yet? Looks similar to Home

PowerHouz by Zysco
https://appsto.re/us/I6Sg3.i
 
Exactomondo, my girlfriend works from home, so I want to make sure the lights don't turn off when I leave. Your idea with the lutron switches is an interesting idea. All I would need is one to achieve this connected to a light we use frequently. Curious, the button you push, does it set a scene in general or just turn off those switches?

Based on the way that the Home app is setup, Triggers run Scenes. That is what I am using, and how it integrates with HomeKit. When you setup a Lutron in-wall switch, you are controlling that specific light/load. If you use a Lutron Pico remote, you can use it to control multiple lights, but still, not a scene. However, when you want a Lutron device to control a non-lurton device, then we're getting into HomeKit and away from Lutron itself-- and using their scenes and the trigger capabilities there.

So with HomeKit you can make it that turning a light on or off triggers a scene. In my case then I have a scene called "bedroom on" and when the bedroom light is turned on (characteristic/trigger) it runs a scene (bedroom on) which turns on the Philips Hue Light Strip. Technically I could have that scene do other functions, but for me it was just that simple.

In your case, then, you could create a scene where turning off a certain light would also turn off other lights/devices. This works great, however remember it will only work if the "state" of the light is changed. So just pressing the off button alone isn't going to work, if the light is already off. You have to change the state of the bulb from on, to off. In my bedroom for example, there is a rare occasion where the hue light strip doesn't go off correctly. Although I could fix this with a Siri voice command, i've also tested it with my light switch. I have to first turn ON the bedroom light (even just to 5% dim), then turn it back off--- so that it sees the state change to "off" (from on) to run the scene. Hope this makes sense.

I was just searching the net a little and came across this, have you played with it yet? Looks similar to Home

PowerHouz by Zysco
https://appsto.re/us/I6Sg3.i

Ohh that looks like a nice app to compare to the Home app, and for a fair price, too. Does it support triggers/etc? The watch app feature looks very nice too!

Also, regarding your comments about motion sensors-- I have a feeling there will soon be other options there. If you dig into the notifications in iOS you'll see there are home security comments in the OS. Makes me think we'll see a LOT more motion sensor options/triggers in the VERY near future with HomeKit. I for one look forward to using my Elgato Eve Door/Window to be able to cause triggers too... we'll see how long it takes for that to work though!
 
Oh wow-- went back to check that app-- it is $5 to buy it but then even MORE money to make it work with more than 5 devices? Forget that-- way overpriced... though I guess $15 for the HOME app and this would be about the same net cost roughly with all features unlocked... tempting for comparison, but not sure i want to spend the money. Did you!?
 
Oh wow-- went back to check that app-- it is $5 to buy it but then even MORE money to make it work with more than 5 devices? Forget that-- way overpriced... though I guess $15 for the HOME app and this would be about the same net cost roughly with all features unlocked... tempting for comparison, but not sure i want to spend the money. Did you!?

I did end up buying that app to see if i could control the ecobee through specific sensors, but it's not much different than the Home app. With the extra in app purchases, the total came to $10, so it is actually cheaper than the Home app (though its a bit deceiving since it doesn't say in the description i think it is limited to 5 devices unless you buy the unlimited devices for $5 more, but maybe thats good for people who only have a few devices).

I have some good news, the developer of the Home app put me on his beta testing and were working towards getting the Home app to give us access to the ecobee sensors individually. I am not sure if we'll be able to achieve this but at least it is a step forward.The reason I have a feeling we might not is that I setup IFTTT to do all my scheduling last night in hopes IFTTT would forgo the permanent hold aspect of the ecobee we spoke of. It did not. Before my fiancé went to bed last night, she told siri I'm going to bed which puts it in a pre sleep mode (set at 69), but at midnight i have a actual sleep mode that knocks it down to 68. When I woke this morning it was still at 69, so the IFTTT did not take effect. I am using the comfort mode action in IFTTT to set the temp, and since the comfort modes are sensor specific, I was hoping I would achieve what we have. But from what I can see, unless a user actually changes the temp directly, no schedule will take effect, ecobee or IFTTT. Which leads me to believe Home may not. The only hope I have is since we may be able not to rely on the comfort modes, and recreate the modes in the Home app through its' settings, maybe it will override ecobee's inherent permanent hold programming.

Truth is, that aspect of the ecobee needs to go as it is really as it is really messing with my zen thing, man. will keep you posted as things develop with Home.
 
  • Like
Reactions: arijaycomet
The hold issue with the ecobee has prevented me from even using its built-in geofencing feature. When I tried it, making it set itself to Home profile when I arrived, it kept that profile past when my Sleep profile was supposed to activate. IFTTT geofence did work for me though for "resume schedule". So at least if it went into auto-away, it will go back to Home when I arrived.

For the sensors though... On ecobee's support page (https://www.ecobee.com/faq/what-voice-commands-can-i-use-to-control-my-homekit-enabled-ecobee3/), it mentions that as of iOS 9 we can ask the temperature of the senors, “List [sensor name] temperature.”... or we the temperature of the thermostat, “List temperature of [thermostat name].”. I can't get it to ever list or report that there is a sensor in my house. I'm able to say "what's the temperature of my house", but if I ask it "List the [Living Room] temperature" it will always reply back with "sorry, but I couldn't find any sensors in the living room. Has anyone gotten it to list the sensors readings through Siri? Or is that support page just generally referring to a sensor like the elgato eve, and not ecobee's sensors?
 
The hold issue with the ecobee has prevented me from even using its built-in geofencing feature. When I tried it, making it set itself to Home profile when I arrived, it kept that profile past when my Sleep profile was supposed to activate. IFTTT geofence did work for me though for "resume schedule". So at least if it went into auto-away, it will go back to Home when I arrived.

For the sensors though... On ecobee's support page (https://www.ecobee.com/faq/what-voice-commands-can-i-use-to-control-my-homekit-enabled-ecobee3/), it mentions that as of iOS 9 we can ask the temperature of the senors, “List [sensor name] temperature.”... or we the temperature of the thermostat, “List temperature of [thermostat name].”. I can't get it to ever list or report that there is a sensor in my house. I'm able to say "what's the temperature of my house", but if I ask it "List the [Living Room] temperature" it will always reply back with "sorry, but I couldn't find any sensors in the living room. Has anyone gotten it to list the sensors readings through Siri? Or is that support page just generally referring to a sensor like the elgato eve, and not ecobee's sensors?

Yep, as mentioned above the permanent hold aspect of the ecobee is annoying. I can't create scenes in the Home app that include changing my profile when I go to bed for example simply cause it won't resume the schedule in the morning. I hope they will change this soon cause even on old school thermostats, the schedule resumes even if you make a change to the temp, and we don't know why they think this makes sense.

As with Siri telling me temps of the sensors, my guess is either HomeKit isn't updated to allow this yet or the ecobee app isn't making that info available yet through commands. Individual temps show up in the Home app, so the sensor info is there but maybe the commands aren't able to access it yet.
 
I tried enabling HomeKit with the Ecobee3 by using the Home app and setting up my home and adding the ecobee to it all went without issue but it required me to disable the 'auto' heat/cool feature of the thermostat meaning it turned the system off. Why does using HomeKit not allow the auto feature? Seems that is a feature I want it to be on always so i don't have to select heat or cool. Anyway so I tried removing the device from homekit and the house and now the Ecobee3 will not let me go back to auto mode. Anyone know what I am doing wrong?

Using homekit siri was able to answer the simple temperature and humidity questions and even set the temperature to 76f but it was not able to answer the temperature for each of my named sensors, saying 'could not find sensor' in that room. Setting up homekit is terribly confusing at the moment, is there a better app for it? Seems Apple really needs to write this app, not have it rely on 3rd party.
 
I'm relieved to hear about the sensors because I worried mine might not be working correctly. It's a shame though. Same with the "auto" feature. That one is the biggest annoyance for me because where I live, in the spring and fall, it's common to have the AC come on during the day and the furnace overnight. I'd prefer to just leave it in auto year round to be honest, but for now, I disable HomeKit to have the auto function during those seasons.
 
As an update to the Ecobee app just a day or two ago, you can now enjoy AUTO mode (instead of just HEAT, AC or OFF). There must have been some change to how HomeKit works, as the limitation was in HK, not Ecobee. Now that HK supports Auto mode capabilities, you can get the benefits of AUTO mode once more. See my posts prior in this thread-- Ecobee3 remains my top thermostat choice for Apple users who desire HomeKit compatibility!
 
As an update to the Ecobee app just a day or two ago, you can now enjoy AUTO mode (instead of just HEAT, AC or OFF). There must have been some change to how HomeKit works, as the limitation was in HK, not Ecobee. Now that HK supports Auto mode capabilities, you can get the benefits of AUTO mode once more. See my posts prior in this thread-- Ecobee3 remains my top thermostat choice for Apple users who desire HomeKit compatibility!

App Store is showing last update for ecobee app was 12/1, you in the beta test side? Also, with the update have you noticed if they fixed the issue we were taking about, with schedule resuming automatically after using HK commands? :)
 
App Store is showing last update for ecobee app was 12/1, you in the beta test side? Also, with the update have you noticed if they fixed the issue we were taking about, with schedule resuming automatically after using HK commands? :)

You're right-- it wasn't a software update. It was just a push update. I received an email from my Ecobee stating this update occurred, and the display on my unit also said the same facts. You can read more about it here:
https://www.ecobee.com/faq/how-do-i...my-homekit-enabled-ecobee3-when-in-auto-mode/

As for the issue you were talking about (must have missed that in this thread)-- i've never had such an issue. my Ecobee3 is set that any changes to temperature would hold until the next scheduled event. So if I used Siri to change the temp, it properly holds until the next scheduled change. Equally so, telling Ecobee to go home/away works the same, too. I've never experienced any other issues though perhaps I'm not understanding precisely the issue you speak of, sorry.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.