Richman777

Soooo is this dead? There's def. some weird issues with the API now (every first request fails, which I'm assuming has to do with getting a new session).

Figured you're busy but I figured out the API change - the call to the device put endpoint wasn't actually updating the temperature mode. I made the change to actually call the shared endpoint but not touch the internal structure. You should see a pull request in github.

I've noticed that switching the mode of the nest no longer works - I get a confirmation that it switches between heat/cool but it doesn't actually do it. Edit: Everything else seems to actually work, just changing from cool to heat or vice versa doesn't. It does work if I do it from the actual nest web interface.

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.

FYI - looks like Developer Preview 6 fixed this issue. Edit: I will say, that if you cancel a VPN connect that asks for a token auth, you'll still get that vpn connection popup after. Check IP before and after to see if it connects maybe?

Thanks for the quick response - works like a charm.

Not sure if this is an issue but seems like I can't set the temperature. I type "nest temp" and the current temp comes up and then I add "74" (so the command looks like "nest temp 74") and hit enter. I'll get an empty notification in notification center that just says "Nest" and the nest doesn't respond.

No problem - I'll keep an eye out on it and update if its fixed in one of the next developer previews.

It always says "Connected" despite not actually connecting.... It's definitely attempting to connect to the correct VPN as if I name it something that isn't the correct VPN it throws an error on the variable. Actually viewed the events and saw this, "missing value" (I changed the VPN name to hide it as it does contain company name) tell application "System Events" get service "<VPN NAME>" of current location of network preferences --> service id "2F9448AF-DFE9-4F77-9828-33905B42D4E4" of network preferences get connected of current configuration of service id "2F9448AF-DFE9-4F77-9828-33905B42D4E4" of network preferences --> false connect service id "2F9448AF-DFE9-4F77-9828-33905B42D4E4" of network preferences --> missing value end tell Found this on open radar which seems to be the same thing: http://openradar.appspot.com/14697626

Not really sure if this is a mavericks problem or what but doesn't seem to be working. It will correctly list my VPN and then say connect. I'll get a notification saying it is connected, but it definitely isn't. I have a keyfob for my work VPN and when I hit connect, nothing happens (I'd expect the login prompt to open) and then get the notification via Alfred.