Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apps Thermo Watch - control your Nest Thermostat
- Thread starter Marconelly
- Start date
- Sort by reaction score
Here's what's going on: When you set Away on your watch, your whole home goes into Away state. So for example if you have Nest cameras, they change their behavior accordingly. As soon as you set your home to Away state, your thermostat goes into "Eco" mode. Then when you change the thermostat back to Heat or Cool, it does so, but your home remains in the Away state.
This is all completely repeatable using Nest's own app btw, and it's their way of decoupling away state from the functioning of thermostat. Essentially, what they're thinking is that some people might want thermostat working while the house is in the away state.
Sadly, this behavior does appear somewhat confusing... now they have Eco mode and Away state, and one invokes the other but not vice versa. Essentially, I think Nest want to discourage people who own just the thermostat from switching to away mode manually, and instead they want you choosing Eco mode from the mode menu. Try doing that with my app as well, and see if you prefer how it works then.
In the meantime I plan to change my app to only show thermostat being Away when it's in the Eco mode, just like their app is doing. This way it will behave the way you'd expect it, if you choose away mode manually.
Glad you said confusing because that is what I have been since the Eco introduction, never sure what mode to use, there are times when I select Eco and tstat says Eco but the Nest app says Away. I always set the Eco/Away manually using the watch but sometimes use the stat for heal/cool, If I use the watch both ways there does not seem to be an issue.
I've just submitted a new version of the app for a review. It will do what I described above - mimic the exact behavior of an actual thermostat - so you won't be seeing any discrepancies if you set the away state on the watch app, then switch to heating on the thermostat etc. The app has bunch of other enhancement and new features too. It'll be a nice update
Really having issues with the opening speed of the app now on my Watch (Series 0). Even as a complication, it can take 15-20 seconds for the app to open to one of the 2 thermostats I have set up. It was much faster under WatchOS 2 than it is now. I don't think this is expected behavior, even for an older model watch. Wil the new version that you referred to, @Marconelly, in #129 above fix this issue?
That version is already out (3.0). It features several OS3 specific enhancements, such as letting you swipe up and down, or tap upper/lower portion of the screen to change the temperature. It also features improved handling of the dock preview.
As for your problem, you should try two things:
- Keep the app in the dock, and for the time being, remove the complication from the watch face. The performance problem with the complication still exists as of watchOS3.1 (I haven't tested 3.1.1 yet). Until Apple fixes this OS-level issue (which they acknowledged to me, but I'm not sure when they're going to do anything about it) the app will keep losing performance while the complication is running, and will eventually need to restart. This is what's causing the restarts you're seeing - with the complication removed, the app shouldn't really ever restart, for as long as you keep it in the dock.
- If this doesn't help, try reinstalling the app. I'm not sure why anything would go wrong with the installation over time, but I've seen stranger things happen with the watch, so I can't ever be sure.
As for your problem, you should try two things:
- Keep the app in the dock, and for the time being, remove the complication from the watch face. The performance problem with the complication still exists as of watchOS3.1 (I haven't tested 3.1.1 yet). Until Apple fixes this OS-level issue (which they acknowledged to me, but I'm not sure when they're going to do anything about it) the app will keep losing performance while the complication is running, and will eventually need to restart. This is what's causing the restarts you're seeing - with the complication removed, the app shouldn't really ever restart, for as long as you keep it in the dock.
- If this doesn't help, try reinstalling the app. I'm not sure why anything would go wrong with the installation over time, but I've seen stranger things happen with the watch, so I can't ever be sure.
I finally have some really good news on this front. It looks like Apple has fixed this gradual performance degradation bug that happened due to repeated complications update, and that has been there since watchOS3.0.
With watchOS3.2 beta, at least when tested on simulator, I can no longer reproduce this problem. Maybe all my complaining and bug reporting finally worked
*edit* Now also been testing it on a real watch with 3.2 beta, and the problem is definitely gone.As for the next version of the app, it should be a really good one - I've added a true Siri support to the app, so you will be able to to control your thermostats completely hands free, through Siri, without ever needing to start the actual app, or the widget. Next version will only support Siri from the iPhone or iPad, but as soon as wachOS3.2 is officially out, I'll bring the same Siri support to Watch app as well.
That is if Apple approves it first... I've not done things entirely by the book here. You may know that the Siri support for 3rd party apps is very limited in scope, and home devices control is not one of the things they have meant to be officially supported. This, I assume, is the reason that Nest's official app has not made any updates to support this yet (and I'm not aware if any 3rd party apps have attempted to do it either). The way I've made this work is that you're technically speaking 'messages' to your thermostat, but it's very streamlined and easy to perform. I really hope they don't reject it, because I think people will like the way it works.
Last edited:
I finally have some really good news on this front. It looks like Apple has fixed this gradual performance degradation bug that happened due to repeated complications update, and that has been there since watchOS3.0.
With watchOS3.2 beta, at least when tested on simulator, I can no longer reproduce this problem. Maybe all my complaining and bug reporting finally worked
As for the next version of the app, it should be a really good one - I've added a true Siri support to the app, so you will be able to to control your thermostats completely hands free, through Siri, without ever needing to start the actual app, or the widget. Next version will only support Siri from the iPhone or iPad, but as soon as wachOS3.2 is officially out, I'll bring the same Siri support to Watch app as well.
That is if Apple approves it first... I've not done things entirely by the book here. You may know that the Siri support for 3rd party apps is very limited in scope, and home devices control is not one of the things they have meant to be officially supported. This, I assume, is the reason that Nest's official app has not made any updates to support this yet (and I'm not aware if any 3rd party apps have attempted to do it either). They way I've made this work is that you're technically speaking 'messages' to your thermostat, but it's very streamlined and easy to perform. I really hope they don't reject it, because I think people will like the way it works.
I was reading your post and thinking "Whaaaattt?!? Did I miss a big announcement?"
Then I read your last paragraph.
I hope they let it through, too, but since this is a hot button area with them right now, what with Alexa and Google Home, I could see them not allowing it pending a large planned expansion of Sirikit to allow much greater access. But fingers crossed! This would be a wonderful addition.
I took away the messaging aspect as much as possible. It does not look like a message at all, as it's all custom UI that looks like an app itself. This is how it looks like and at the top you can see the kind of phrase you can say (there are many other possible variations and functions, of course)
Last edited:
Well, they rejected it
I've submitted an appeal to the review board, arguing for my case the best I could - but it's a long shot. However, the beta version is still available, and I'll proceed with sending it to whomever is interested. I will keep the 'Siri branch' of the app continuously updated with whatever official updates I publish, so that I can keep this beta alive and up to date, as well as to allow me to easily adapt the code once the day comes that Apple allows more elaborate SiriKit usage.
gwhizkids and ericg301 can you PM me your emails so that I can send you beta invites? Others are free to join in.
I've submitted an appeal to the review board, arguing for my case the best I could - but it's a long shot. However, the beta version is still available, and I'll proceed with sending it to whomever is interested. I will keep the 'Siri branch' of the app continuously updated with whatever official updates I publish, so that I can keep this beta alive and up to date, as well as to allow me to easily adapt the code once the day comes that Apple allows more elaborate SiriKit usage.
gwhizkids and ericg301 can you PM me your emails so that I can send you beta invites? Others are free to join in.
Got it and installed the beta. Thanks!
Works great with this syntax: "Thermowatch, message to Nest: increase temperature". However, it does not work with either: "Thermowatch, message to Nest: decrease temperature" or "Thermowatch, message to Nest: reduce temperature". In those cases, I get the following:
Also, what is the syntax if you have multiple Nests (in my case, Upstairs and Downstairs)?
Finally: assume I need WatchOS 3.2 beta to use from Watch, correct?
Works great with this syntax: "Thermowatch, message to Nest: increase temperature". However, it does not work with either: "Thermowatch, message to Nest: decrease temperature" or "Thermowatch, message to Nest: reduce temperature". In those cases, I get the following:
Also, what is the syntax if you have multiple Nests (in my case, Upstairs and Downstairs)?
Finally: assume I need WatchOS 3.2 beta to use from Watch, correct?
Last edited:
I am not sure why decrease temperature doesn't work. Try changing the sentence structure and see if it works then, something like:
"Message to Nest using Thermo Watch: Decrease Temperature"
or
"Thermo Watch send message to Nest saying: Decrease Temperature"
here are the phrases that should work:
Thermowatch, message to Nest: heat up
Thermowatch, message to Nest: start heating
warm up
warm-up
warmer
temperature up
raise the temperature
increase the temperature
increase temperature
cool down
colder
cooling
cooler
temperature down
lower the temperature
decrease the temperature
decrease temperature
All the above phrases can be used in a sentence, something like "Thermowatch, message to Nest: Make the room warmer"
You can also specify degrees number like this:
"Thermo Watch message to Nest, set 75 degrees" etc.
Below phrases have to be an exact match,
Thermowatch, message to Nest: Away
Thermowatch, message to Nest: Set away
set home
end away
and away (I've added this because Siri can never interpret "End Away" right, no matter what I try.
fan on
set the fan on
turn the fan on
fan off
set the fan off
turn the fan off
If you have multiple Nests you can do two things:
Thermowatch, message to Nest Number Two: increase temperature
or (in your case)
Thermo Watch, message to Upstairs: increase temperature
Thermo Watch, message to Downstairs: increase temperature
Essentially, you can use whatever name you've given to your thermostats when you address them. You will know that it worked when the correct thermostat name is printed under the circle with the action in the Siri UI.
"Message to Nest using Thermo Watch: Decrease Temperature"
or
"Thermo Watch send message to Nest saying: Decrease Temperature"
here are the phrases that should work:
Thermowatch, message to Nest: heat up
Thermowatch, message to Nest: start heating
warm up
warm-up
warmer
temperature up
raise the temperature
increase the temperature
increase temperature
cool down
colder
cooling
cooler
temperature down
lower the temperature
decrease the temperature
decrease temperature
All the above phrases can be used in a sentence, something like "Thermowatch, message to Nest: Make the room warmer"
You can also specify degrees number like this:
"Thermo Watch message to Nest, set 75 degrees" etc.
Below phrases have to be an exact match,
Thermowatch, message to Nest: Away
Thermowatch, message to Nest: Set away
set home
end away
and away (I've added this because Siri can never interpret "End Away" right, no matter what I try.
fan on
set the fan on
turn the fan on
fan off
set the fan off
turn the fan off
If you have multiple Nests you can do two things:
Thermowatch, message to Nest Number Two: increase temperature
or (in your case)
Thermo Watch, message to Upstairs: increase temperature
Thermo Watch, message to Downstairs: increase temperature
Essentially, you can use whatever name you've given to your thermostats when you address them. You will know that it worked when the correct thermostat name is printed under the circle with the action in the Siri UI.
Last edited:
Sorry, I forgot to reply to this - I didn't get around to implementing Siri support on the watch yet. I have to use beta Xcode to accomplish that, and I figured that would further complicate things about publishing a release.
Also, I've just tried this phrase and it worked:
"Message to Nest using Thermo Watch: Decrease Temperature"
And this also worked:
"Thermo Watch message to Family Room: Decrease Temperature". (My thermostat's name is Family Room)
Don't forget, you can also say numbers to set the desired temperature:
"Thermo Watch message to Nest, set 75 degrees" etc.
Last edited:
I've released an official version that features the complete fix for the performance degradation / app restarting issue, due to repeated complications update. This fix is only possible when using watchOS 3.2, so I encourage everyone using the app to upgrade. Thanks to this, and some other small optimizations, the app has never worked better and faster.
Even though I had to remove Siri support from this official release, I will be keeping that code branch continuously updated, so that once SiriKit start supporting this kind of intent (hopefully with iOS11) the app will be ready to use it right away. Also, I should be releasing another beta soon, that will have Siri working on the watch app as well.
Even though I had to remove Siri support from this official release, I will be keeping that code branch continuously updated, so that once SiriKit start supporting this kind of intent (hopefully with iOS11) the app will be ready to use it right away. Also, I should be releasing another beta soon, that will have Siri working on the watch app as well.
Yes, it's the update 4.0. Keep in mind though that in your case, the beta that you're using already has these updates, but it also has the Siri support that I had to remove from the App Store release.
Last edited:
I've released the 5.0 update today. This version brings support for Apple TV. Those of you who already have the app on iOS/Watch, can just download it to your Apple TV for free, as the app is universal purchase (purchase on one device, and it becomes free on all the other supported devices).
This is what the app looks like. As you can imagine, you switch between the thermostats by swiping left/right, and you change the temperature on the focused one by swiping up/down. I wanted to make this as quickly accessible as possible, so no other buttons are visible, or anything else selectable on the main interface. You can however press the Play/Pause button on the remote, to open the menu where you can set the HVAC mode or turn the fan on/off.
This is what the app looks like. As you can imagine, you switch between the thermostats by swiping left/right, and you change the temperature on the focused one by swiping up/down. I wanted to make this as quickly accessible as possible, so no other buttons are visible, or anything else selectable on the main interface. You can however press the Play/Pause button on the remote, to open the menu where you can set the HVAC mode or turn the fan on/off.
I've released the 5.0 update today. This version brings support for Apple TV. Those of you who already have the app on iOS/Watch, can just download it to your Apple TV for free, as the app is universal purchase (purchase on one device, and it becomes free on all the other supported devices).
This is what the app looks like. As you can imagine, you switch between the thermostats by swiping left/right, and you change the temperature on the focused one by swiping up/down. I wanted to make this as quickly accessible as possible, so no other buttons are visible, or anything else selectable on the main interface. You can however press the Play/Pause button on the remote, to open the menu where you can set the HVAC mode or turn the fan on/off.
Looks fantastic. This app has been a fixture on my watch, holding a permanent space as a complication. It started out good and only got better as time went on. A must have for anyone with a nest and an apple watch.
Unfortunately I'm moving home this weekend and decided on an ecobee this time around, for the sensors and homekit support. I wish you the best of luck with this.
Thanks for the good wishes! While it's a shame that Nest doesn't support Homekit, I can see how they must be blocked from doing it for political reasons, rather than laziness or stubbornness. Hopefully at least Apple will expand SiriKit at the upcoming WWDC, to enable 3rd party apps support for home automation.
I'm actually curious to hear how good Ecobee watch app or iOS widget are. If they are not as good as you think they should be, I think I could expand this app to support Ecobee. They have the API that I have only briefly looked into, but it doesn't seem too different from what Nest has.
I'm actually curious to hear how good Ecobee watch app or iOS widget are. If they are not as good as you think they should be, I think I could expand this app to support Ecobee. They have the API that I have only briefly looked into, but it doesn't seem too different from what Nest has.
Now that I've lived with it for a few days I can tell you that the widget is pretty crappy - it's informational only and just bounces you into the app. The watch app and complication are a joke. The app almost never launches and the complication almost never updates. At least, that's my experience with them. If you had an app or extended Thermo Watch you would have zero competition too. There's next to no commercial 3rd party development around it.
As far as how you would interface with it though... Ecobee is definitely a little different. Unlike Nest, where it's basically Home or Away and Home sticks to a schedule with explicit temperatures, Ecobee is centered around what they call Comfort Settings.
Comfort Settings are themselves a Heat/Cool temperature setting and it's Comfort Profiles that you schedule on a timeline. There are three built in, Away, Home and Sleep and you can add your own.
The other thing you'd have to watch out for are sensors, which I think are the real value add of Ecobee. For instance I added my own Comfort Profile, Bedtime. Since at bedtime I'm really only concerned what temperature it is in the bedroom, and not at the thermostat, I've set that profile from 10:30pm to 11:30pm to only use the bedroom sensor (it averages all sensors under normal circumstances).
There's definitely things you'd need to be aware of to do the app. A user would want manual control over temps, but also to be able to switch profiles and probably to monitor sensors, or perhaps even change which are taken into account for a temp change.
With all that said, I don't want to put you off doing this. I'd happily pay an IAP or for a separate app if you do, as I know they'd be awesome compared to stock.
Thank you so much for all that research and suggestions. It does seem like the differences are substantial enough, that I'd have to do a separate app. However, what will really hamper this effort is the fact that it seems like you have to own an Ecobee thermostat, to be able to create a developer account with them. I somehow missed this before, but they are pretty clear about it here: https://www.ecobee.com/developers/
All this would mean that I'd pretty much have to ditch Nest, and switch to Ecobee long term, to really get that project going.
With Nest, this is not the case. They even provide a virtual device console to developers, so you can develop for their devices that you don't own. If Ecobee would do something like that in the future, I'd gladly jump on the opportunity to make the app, but right now it's too risky of a prospect for me.
Last edited:
That would certainly go some way to explaining why the 3rd part development scene around ecobee seems much less vibrant than Nest. I think they rely their homekit and IFTTT support for 3rd parties, more than their own API.
It's been a great little device so far and I'm quite happy with it, all told. If you do get around to doing something for it it'd certainly be an instant purchase for me.