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
Really happy to hear that. I'm wondering if I should pull the glance view out of the app until 2.2.1 comes out and hopefully fixes that bug. Then again, it seems to only be affecting some people - I've been using the glance a few times a day these last few days and it seemed to work fine for me - and I've checked and made sure - I've not updated the glance code ever since the original release. Then again, I am running a newer version of the app which maybe does make a difference. 1.4 should be out very soon now - I've submitted an expedited review request for it, and the request was approved yesterday (usually takes them a day or two after that to review it.
... and that's precisely where the problem with the glance was (or at least part of the problem I could fix). I forgot to add the handling for the error that the watchOS2.2 spams over and over by mistake, when it clearly shouldn't. A problem that didn't exist pre-2.2. I added fix for this to the main app and the complication, but didn't add it to the glance. Apple has fixed this in the latest 2.2.1 beta, but in the meantime my error handling should get the job done on regular 2.2. I've fixed this in the glance code and re-submitted v1.4 for an expedited review early today.
*edit* OK, the 1.4 release is now out, and should fix the glance problem, and be even more reliable in general. I've also added settings for a few things:
- Ticking while spinning the digital crown can be disabled.
- Crown sensitivity can be changed to three different presets
- Humidity display can be enabled/disabled for the main app (it's enabled by default)
Eric, just to let you know that you can now disable the crown spinning ticking, but the final double tap is still there regardless.
Last edited:
Now that 1.4 is out, can you please try, at least temporarily, to go back to your routine of using the glance, and check if you're seeing the erroneous behaviour that you've been seeing before? I want to try and confirm that I've fixed the Glance problem.
It's working for me also, what I did experience the 1st and 2nd day after the update I had to reset my phone in order for the watch and phone to connect kept getting the connection message/retry screen, this morning they connected instantly, hope the first 2 days were a fluke
I see... There are still bugs in watch connectivity protocol that should hopefully go away with os 2.2.1. I suggest if this happens again, rather than resetting the phone, either just wait about a minute, and try again - it should re-connect then. If it doesn't, kill the app (by pressing the side contacts buttons twice procedure) and restart it after 10 seconds or so. I'm curious if that will help resolve the issue. I also have a suspicion that some users might be seeing some disconnections due to peculiarities of their wi-fi networks. If you keep seeing the errors, and have a good mobile data reception, try going for a while on mobile data only, and see if that helps. If all else fails, maybe go back to using complication instead of the glance for the time being - I wonder if there may still be something about glances breaking the connectivity that I can't do anything about - I know some developers on Apple forums have complained about it, but I haven't personally experienced it.
Last edited:
I've just released the 1.5 update - please try it and see if it resolves the connectivity problems completely for you. I believe I've finally got the full understanding of why those connectivity problems were happening, and I think I've resolved it. I've been running the app for days now without ever seeing them anymore. Make sure to update your watch to 2.2.1 as well! It resolves at least one nasty bug that Apple introduced in 2.2 in their watch connectivity protocol.
Aside from this fix, 1.5 introduces a novel setting which if you enable, the app will go directly into the voice input mode if you tap on the complication. You can still tap on the glance to open the app in the "normal" mode (and of course you can always just cancel the voice input pane if you open into it when you don't want to). I kept this option Off by default, but it's there in the settings, if anyone wants to try it out.
Still having connectivity issues, the last 3 days since the update when I put my watch on it will not connect with the app regardless how long I wait, the only working method for me is to reset my phone, upon reset it connects immediately and is fine for the rest of the day, even if I take my watch off and put it back on, it is just the initial connectivity I am having issues with.
Another thing which is me, voice input doesn't understand my "End Away", no matter how many time I try it types "And Away"
Another thing which is me, voice input doesn't understand my "End Away", no matter how many time I try it types "And Away"
Definitely not what I was expecting to hear :\ I've been using the 1.5 version of the app for almost a week now, and it has worked perfectly. Can you tell me, when you say "will not connect" does that mean you see the infinitely looping loader animation, or you see the connection error alerts that won't go away even if you press "Retry"?
Either way, I can suggest a few things to try:
- Don't kill the phone app at the end of the day. I know this shouldn't matter, but now I'm curious if it does.
- If you can, try not using wifi on your phone, and just stay on mobile internet for a day or two. See if that makes any difference.
- if you still get the connection problem, try killing and restarting the watch app (by holding the wide side button twice method). I that doesn't help, try killing and restarting the phone app after that.
All that said, I know they are developers begging Apple to fix the watch connectivity problem, that they have introduced at some point, and the problem those people are seeing are apparently still not fixed. I'm wondering if this affects some users, but not everyone, and what are the differentiating factors between the two (that's why I'm asking you to try all these things).
As for the "And Away" problem - don't worry about that, just press Done button when you see the words "And Away" on the screen, it will work. The fact that Apple's dictation system always interprets "End Away" as "And Away" is the reason I've made the "And Away" one of the supported commands - which will end your away status.
Either way, I can suggest a few things to try:
- Don't kill the phone app at the end of the day. I know this shouldn't matter, but now I'm curious if it does.
- If you can, try not using wifi on your phone, and just stay on mobile internet for a day or two. See if that makes any difference.
- if you still get the connection problem, try killing and restarting the watch app (by holding the wide side button twice method). I that doesn't help, try killing and restarting the phone app after that.
All that said, I know they are developers begging Apple to fix the watch connectivity problem, that they have introduced at some point, and the problem those people are seeing are apparently still not fixed. I'm wondering if this affects some users, but not everyone, and what are the differentiating factors between the two (that's why I'm asking you to try all these things).
As for the "And Away" problem - don't worry about that, just press Done button when you see the words "And Away" on the screen, it will work. The fact that Apple's dictation system always interprets "End Away" as "And Away" is the reason I've made the "And Away" one of the supported commands - which will end your away status.
Last edited:
Help, I've keep getting a "nest write error". I have deleted the app from my phone, twice and even changed my nest password.
So this was my process, download the app on my iPhone 6. Wait 5 minutes then check the watch and make sure it was loaded. Open the app on the phone and logged in. Successfully logged in. Went to watch and it opens with the correct info & temp ect. Whenever I change temp or to away I get nest write error?
The phone and watch are both with most current iOS. Not sure what to do next???
So this was my process, download the app on my iPhone 6. Wait 5 minutes then check the watch and make sure it was loaded. Open the app on the phone and logged in. Successfully logged in. Went to watch and it opens with the correct info & temp ect. Whenever I change temp or to away I get nest write error?
The phone and watch are both with most current iOS. Not sure what to do next???
Follow Up:
Left the app open last night, Put my watch on at 5:30 am, by 8:30 (I wanted to wait to see how long it would take to connect, which it never did) still not connected, keep getting the infinite loop and occasional alert but does go away when I hit retry, finally rest the watch per your recommendation, still no connectivity, killed the app and restarted on the phone, still no connectivity, finally rebooted the phone and had almost instantaneous connectivity.
Whatever my issue is rebooting the phone seems to be the only thing that works for me
Left the app open last night, Put my watch on at 5:30 am, by 8:30 (I wanted to wait to see how long it would take to connect, which it never did) still not connected, keep getting the infinite loop and occasional alert but does go away when I hit retry, finally rest the watch per your recommendation, still no connectivity, killed the app and restarted on the phone, still no connectivity, finally rebooted the phone and had almost instantaneous connectivity.
Whatever my issue is rebooting the phone seems to be the only thing that works for me
aloha50, I will look into what that could be. I've never heard of that problem yet. Does it just say "nest write error" or is the message more elaborate? Is your thermostat locked for changes in some way? Can you successfully control the thermostat using Nest's iphone app? What about going to their website and controlling it from there? Is your thermostat assigned to a company, or is it in your personal home? Also, make sure you log in with your main, "owner" account, and not the secondary, "family" account (and sorry for the barrage of questions)
YatBob, can you try just one more thing - disable the wifi on your phone, and leave it to use mobile data for a day before you go to the bed, and see if the same problem still happens. Just to let you know, I'm planning to implement an option for a secondary approach for data handling and thermostat control, that after initial setup will not be reliant on the phone app in any way. This will use up more battery on the watch, but should hopefully avoid connectivity problems that I can no longer reproduce, like what you're seeing.
YatBob, can you try just one more thing - disable the wifi on your phone, and leave it to use mobile data for a day before you go to the bed, and see if the same problem still happens. Just to let you know, I'm planning to implement an option for a secondary approach for data handling and thermostat control, that after initial setup will not be reliant on the phone app in any way. This will use up more battery on the watch, but should hopefully avoid connectivity problems that I can no longer reproduce, like what you're seeing.
---
Well I got it working. again deleted the app from the phone, went to nest and again changed the password and logged in to control it thru the website. reset the nest app and logged in. reloaded the app and opened it on the watch poof it works. it was one thermostat, one user (personal). Not sure what was different but reloaded worked. yes the error message was "nest write error" nothing else. I like the app and it works well thanks.
Glad you got it working. I think the most likely culprit in your case was some temporary Nest service outage for a group of accounts that included yours, so it would possibly have resolved itself if you just waited.
I will try what you suggest and report back, it is just the initial connectivity I am having issues with, once I connect I can remove my watch for several hours, put it back on an connect instantly
I see. Although it's puzzling that there's anything different between the initial connectivity after you leave the watch unworn for a few hours during the day, vs. when you leave it over the night.
What you're seeing with the infinitely spinning loader is the failure in the connection between the watch and phone. Watch tells the app that the connection exists, so the app begins to communicate, but the connection is in fact broken, and the response never comes back - not even the error response (which would give you an error message after 12 seconds or so). I think you're seeing the same problem that's affecting some people, that some other developers are complaining about, as they too reported that the only solution when that happens is to restart the phone. As for the app like Heartwatch, I think that kind of app doesn't have to rely on on-demand connectivity between the watch and the phone - while the phone's screen is turned off. Therefore it can use a backup sync method that synchronizes the state once the phone's screen is turned on. For my app there's no point in attempting to implement that kind of backup, but I think what I have planned (a network communication system that does not rely on the phone at all) should resolve everything for the problem cases like yours.
Disabling the wifi did work for 2 days, then yesterday evening without ever taking the watch off all day, I lost connection, sort of just ignored it because it was close to bed time, this morning I had to restart phone to get connectivity
In all instances whatever method I use, I have 2 good days of connectivity then on the third day a restart of phone or watch is required, this has happened several times with the 2/3 day cycle.
I think you have a great app and a lot better than the previous 2 I purchased which barely worked, hopefully my issue is minor, and doing a device restart is better than not working at all
I see. I think the only solution for your problem is making the watch communicate with Nest servers directly. I've already started work on this, but I have to do it carefully.
The worst thing is, I can't even replicate the problem you're seeing, I think it's something to do with the WatchConnectivity protocol, and it doesn't happen to everyone. But, by doing what I'm doing now, I can circumvent that protocol entirely (and as a bonus make it so that the watch app becomes completely independent from phone - being able to function even if you shut the phone down entirely).
The worst thing is, I can't even replicate the problem you're seeing, I think it's something to do with the WatchConnectivity protocol, and it doesn't happen to everyone. But, by doing what I'm doing now, I can circumvent that protocol entirely (and as a bonus make it so that the watch app becomes completely independent from phone - being able to function even if you shut the phone down entirely).