jason0x43 Posted October 6, 2013 Author Share Posted October 6, 2013 Yes I noticed it doesn't work with the latest Alfred. Jason, have you considered joining forces with these guys, who also have a Python implementation of a NEST library? https://github.com/johnray/Indigo-Nest-Thermostat-Plugin I hadn't seen that one before. It appears to work similarly to mine, although its API is different. Link to comment
Richman777 Posted October 14, 2013 Share Posted October 14, 2013 This still seems to not work. I type in "nest status" and hit enter and the message "communicating with nest" comes up and then it will switch to the default "Search with google". I downloaded the latest from the link on the first page. I don't have alleeyoop installed and can't even find a version to download so not sure if when you said "published" you meant there or on the main page. Link to comment
jason0x43 Posted October 14, 2013 Author Share Posted October 14, 2013 This still seems to not work. I type in "nest status" and hit enter and the message "communicating with nest" comes up and then it will switch to the default "Search with google". I downloaded the latest from the link on the first page. I don't have alleeyoop installed and can't even find a version to download so not sure if when you said "published" you meant there or on the main page. The download link is always for the current version, so you should be good as long as you downloaded after Oct 6. (That was the last update; I forgot to update the messages on the first post.) Try the "log" command ("nest log") to open up the debug log. Then run "nest status" and see if an error/exception message shows up in the log. If so, send me the exception and I can try to see what's wrong. Link to comment
cagnew Posted October 16, 2013 Share Posted October 16, 2013 I installed the new version and it is now working for me. Thank you! Link to comment
intrepidsilence Posted February 4, 2014 Share Posted February 4, 2014 Hello, I just installed this workflow a couple of days ago and it worked fine. Now it does not. I have deleted it and tried to reinstall. Deleted the Keychain entry, and a few other things to try to get it to work again. Is there a way to reset it back to pre-install state to get it working again? Thanks in advance! I really love this workflow and thank you very much for creating it. Link to comment
jason0x43 Posted February 5, 2014 Author Share Posted February 5, 2014 Hello, I just installed this workflow a couple of days ago and it worked fine. Now it does not. I have deleted it and tried to reinstall. Deleted the Keychain entry, and a few other things to try to get it to work again. Is there a way to reset it back to pre-install state to get it working again? Thanks in advance! I really love this workflow and thank you very much for creating it. Are you seeing any sort of error message? Workflow data is stored in two places: configuration is in ~/Library/Application Support/Alfred 2/Workflow Data/jc-nest, and the cache is in ~/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data/jc-nest. Clearing out or removing those directories will completely reset the workflow. Link to comment
jason0x43 Posted February 5, 2014 Author Share Posted February 5, 2014 Hmmm...It's looks like Nest may have changed something about their API again. I'm looking into this... Link to comment
mikejandreau Posted February 6, 2014 Share Posted February 6, 2014 Their API must have definitely changed. I type nest temp and then it suggests I search Google because it can't connect to my Nest. Looking forward to an update so I can not have to reach for my phone anymore! Link to comment
jason0x43 Posted February 7, 2014 Author Share Posted February 7, 2014 False alarm. Clearing your session file (basically like logging out) and having the workflow create a new one seems to fix the problem. I just posted an updated version of the workflow with a "clear" command that will clear your session file. The next time you run a command the workflow will log back in to home.nest.com and create a new session file. This should fix the problem you're seeing. Link to comment
mikejandreau Posted February 10, 2014 Share Posted February 10, 2014 Jason, that didn't work for me. I cleared my session via the new version and still get "Search Google" when I type nest temp. Anything else I can try? Link to comment
jason0x43 Posted February 11, 2014 Author Share Posted February 11, 2014 Odd. Well, let's try a more extensive reset: Delete session.json from ~/Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data/jc-nest (this is what the 'clear' command should be doing) Delete config.json from ~/Library/Application Support/Alfred 2/Workflow Data/jc-nest Delete your stored Nest credentials from your keychain -- open Keychain Access and delete the "jc-nest.nest" entry Once you've deleted everything, try using the workflow again. It should ask you for your Nest login information the first time you try to do anything. After that you should be back to normal. Link to comment
mikejandreau Posted February 11, 2014 Share Posted February 11, 2014 That did the trick for me. I think something about my user account was preventing the clear command from working. I'm back up and running being 100% lazy to change the temperature now. Thanks! FWIW, this is probably my most used workflow. Love it. Link to comment
calebaharrison Posted March 13, 2014 Share Posted March 13, 2014 Has 2.2 broken this for anybody else? Here's the error log that pops up when I debug it: Starting debug for 'Nest' [ERROR: alfred.workflow.input.scriptfilter] Code 1: Traceback (most recent call last): File "<string>", line 2, in <module> File "alfred_nest.py", line 32, in __init__ LOG.debug('nests: %s', self.account.nests) File "nest.py", line 251, in nests for struct in self.structures.values(): File "nest.py", line 240, in structures self.status['user'][self.user_id]['structures']) File "nest.py", line 231, in status r = self.request('GET', 'mobile/user.{}'.format(self.user_id)) File "nest.py", line 334, in request r = self._requestor.get(url) File "requests/sessions.py", line 347, in get return self.request('GET', url, **kwargs) File "requests/sessions.py", line 335, in request resp = self.send(prep, **send_kwargs) File "requests/sessions.py", line 438, in send r = adapter.send(request, **kwargs) File "requests/adapters.py", line 331, in send raise SSLError(e) requests.exceptions.SSLError: [Errno 8] _ssl.c:504: EOF occurred in violation of protocol Any thoughts? Link to comment
jason0x43 Posted March 13, 2014 Author Share Posted March 13, 2014 It's a networking error, which isn't really saying much. Is it happening consistently? You can try clearing your session with the "clear" command, or the more extensive method I described a couple posts back. Link to comment
Fishysan Posted March 19, 2014 Share Posted March 19, 2014 Hi Jason, thanks for this plugin! I'm also having the same problem, and it is because Nest has changed their site to require SSL TLSv1 now. This is breaking other apps that scrape their website. I wish they'd just release their damn 3rd party API. So if you look into using TLSv1 it should start working again. Pulled from another forum for example; # will failopenssl s_client -connect transport03-rts03-iad01.transport.home.nest.com:443# will succeedopenssl s_client -connect transport03-rts03-iad01.transport.home.nest.com:443 -tls1 Link to comment
jason0x43 Posted March 19, 2014 Author Share Posted March 19, 2014 Yeah, I noticed. Annoying. It looks like urllib3, which requests uses, has an API for using TLSv1, so I should be able to get it back up and running. Link to comment
jason0x43 Posted March 20, 2014 Author Share Posted March 20, 2014 I just uploaded a new version that should fix this. Link to comment
Fishysan Posted March 20, 2014 Share Posted March 20, 2014 Excellent, thanks for the quick fix Jason! It works dandy again. One thing I was going to mention but I'm in Celsius, Nest status is, but weather is in F… probably due to the data you pull from the Nest website? Link to comment
jason0x43 Posted March 20, 2014 Author Share Posted March 20, 2014 Give it a try now. I updated it to use the new Nest weather API, which among other things provides C and F temperatures directly (making it slightly easier to provide the right ones). Link to comment
Fishysan Posted March 20, 2014 Share Posted March 20, 2014 That was quick! Done. Perfect, thanks! Link to comment
segphault Posted March 22, 2014 Share Posted March 22, 2014 Works great here, thanks for sharing. :-) Link to comment
jrs1231 Posted March 25, 2014 Share Posted March 25, 2014 Fantastic work, Jason. Thanks so much! Link to comment
calebaharrison Posted March 26, 2014 Share Posted March 26, 2014 Awesome - update works for me, again, as well. Thanks! Link to comment
mikejandreau Posted November 19, 2014 Share Posted November 19, 2014 I just bought a second Nest as I'm in the process of moving to a place with two zones. Will this workflow work with two different Nests on the same account? Or will I have to duplicate the workflow and change the triggers to nest-2 or something to have it talk to the second unit? Link to comment
jason0x43 Posted December 1, 2014 Author Share Posted December 1, 2014 I just bought a second Nest as I'm in the process of moving to a place with two zones. Will this workflow work with two different Nests on the same account? Or will I have to duplicate the workflow and change the triggers to nest-2 or something to have it talk to the second unit? At the moment, you'll need to duplicate the workflow. You can choose between Nests to control, but the workflow can only control one at a time. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now