Nest Learning Thermostat on sale at Lowe's

@guessed discovered that the Nest plugin was no longer succeeding in sending the home/away commands, and it appeared that a minor change at nest.com was the reason. So I’ve submitted v1.1 of the Nest plugin to apps.mios.com for review. I imagine it will be available in the next few days for installation.

If you want the fix immediately, you can edit your I_Nest.xml file as described here:

[url=http://forum.micasaverde.com/index.php/topic,12700.msg108521.html#msg108521]http://forum.micasaverde.com/index.php/topic,12700.msg108521.html#msg108521[/url]

watou

Well, I should have tested better this morning, but all commands that change thermostat state can reply with an HTTP 302 (redirect), such as changing target temperature, fan mode, and HVAC mode, not just setting home/away. So code to handle 302 replies needs to be in place for all of these. Please apply the attached I_Nest.xml to your Vera if you want the update now, or wait for the 1.1 plugin release to be available from the app store.

Thanks,
watou

The Nest thermostat plugin 1.1 is now available in the app store. It fixes the problem with not handling the recent change at nest.com where some commands to change the thermostat state could be redirected to a different URL. Thanks to user @guessed for catching this.

After this release, a different problem was discovered where Vera2 units may not succeed in sending the “home” or “away” commands. If you have seen this problem (you see “failed to send away command” in the task bar), please apply the attached I_Nest1.xml to your Vera by going to Apps → Develop Apps → Luup files, upload the attached I_Nest1.xml file, check “Restart Luup after upload” and press GO. This interim fix (identified as 1.15) will be in the 1.2 plugin release, along with other code improvements. If you have not seen this problem, then you don’t need 1.15. Many thanks to user @knewmania for all his help in tracking this down.

watou

@watou

I’ve been experiencing some hinky behaviors in UI5 lately and one of the error messages was that Vera couldn’t log into Nest. It was because Nest was performing system maintenance–fine, no problem! But today Nest.com was back up and I still wasn’t able to log in. I re-entered my username and password, and all was well.

Probably nothing, but I thought you’d want to know.
Dave

[quote=“DaveL17, post:184, topic:171456”]@watou

I’ve been experiencing some hinky behaviors in UI5 lately and one of the error messages was that Vera couldn’t log into Nest. It was because Nest was performing system maintenance–fine, no problem! But today Nest.com was back up and I still wasn’t able to log in. I re-entered my username and password, and all was well.

Probably nothing, but I thought you’d want to know.
Dave[/quote]

Thanks for that report. I did see once several weeks ago that my plugin instance didn’t come back after a maintenance window, and it seemed (unfortunately not definitive) to have to do with stale DNS cache – as in, Vera had invalid DNS cache information so the plugin was trying to reach an IP address that wasn’t answering any more. When I ssh’d to the Vera and made some DNS queries, it immediately cleared up. This was sadly not very scientific, but all I could see at the time. If you had any log information to send me, I would certainly take a look at it.

watou

Sorry watou, saw your message too late. I had to reboot this morning and LuaUPnP.log has been reset.

I think the info you’d be after is probably long gone. Do you log info elsewhere that I might be able to find for you?

[quote=“DaveL17”]Sorry watou, saw your message too late. I had to reboot this morning and LuaUPnP.log has been reset.

I think the info you’d be after is probably long gone. Do you log info elsewhere that I might be able to find for you?[/quote]

No worries – yes, my logs rotate into the ether pretty quickly, too. I am a bit doubtful that there would have been anything actionable in the logs anyway. I had noticed (by logging the nest.com device’s status variable in dataMine) that my connection to nest.com had been down around 10pm-11:30pm EDT on Monday. But in my case it came back up without intervention – this time. That’s not to say that a future maintenance event or other outage won’t require it to be poked at manually, but that ought not be the norm.

Thanks for getting back to me in any case.

watou

My pleasure.

The other interesting thing I saw was, when I tried logging directly into nest.com, the maintenance page I got was in French. (I’m in the US.). Maybe it thought I was in Ontario? :slight_smile:

[quote=“DaveL17, post:188, topic:171456”]My pleasure.

The other interesting thing I saw was, when I tried logging directly into nest.com, the maintenance page I got was in French. (I’m in the US.). Maybe it thought I was in Ontario? :)[/quote]

Mais oui! Pourquoi pas? :slight_smile:

@watou
I do not have a Nest Thermostat … but I am working on a control point.
Does your Plugin respond to the standard Services and Actions for a Z-Wave Thermostat ?
Or did you create your own ServiceID and Actions ?
Does it have the Same DeviceID ?

Yes.

Yes, in addition to the standard ones.

No. Here are the DeviceTypes and ServiceIds the plugin implements:

DeviceType: urn:schemas-watou-com:device:HVAC_ZoneThermostat:1
ServiceIDs:
urn:watou-com:serviceId:HVAC_ZoneThermostat1
urn:upnp-org:serviceId:HVAC_FanOperatingMode1
urn:micasaverde-com:serviceId:HVAC_OperatingState1
urn:upnp-org:serviceId:HVAC_UserOperatingMode1
urn:upnp-org:serviceId:TemperatureSensor1
urn:upnp-org:serviceId:TemperatureSetpoint1_Heat
urn:upnp-org:serviceId:TemperatureSetpoint1_Cool
urn:micasaverde-com:serviceId:HaDevice1

DeviceType: urn:schemas-watou-com:device:NestHumidistat:1
ServiceIDs:
urn:micasaverde-com:serviceId:HumiditySensor1
urn:micasaverde-com:serviceId:HaDevice1

DeviceType: urn:schemas-watou-com:device:NestStructure:1
ServiceIDs:
urn:watou-com:serviceId:NestStructure1
urn:upnp-org:serviceId:HouseStatus1
urn:upnp-org:serviceId:SwitchPower1
urn:micasaverde-com:serviceId:HaDevice1

DeviceType: urn:schemas-watou-com:device:Nest:1
ServiceIDs:
urn:watou-com:serviceId:Nest1

Each device has the appropriate category number assigned, if that helps.

watou

@watou
Thanks for the quick feedback … If looks like if I detect your device type I can send standard Thermostat commands …

[quote=“RichardTSchaefer, post:192, topic:171456”]@watou
Thanks for the quick feedback … If looks like if I detect your device type I can send standard Thermostat commands …[/quote]

I believe so. Garrett’s Android app was able to work correctly with it before even knowing I had a different device type, so that’s a good indicator (I think).

Will your service point present a clean programmatic interface for others to use, by any chance? I have some ideas… :wink:

[quote=“watou, post:185, topic:171456”][quote=“DaveL17, post:184, topic:171456”]@watou

I’ve been experiencing some hinky behaviors in UI5 lately and one of the error messages was that Vera couldn’t log into Nest. It was because Nest was performing system maintenance–fine, no problem! But today Nest.com was back up and I still wasn’t able to log in. I re-entered my username and password, and all was well.

Probably nothing, but I thought you’d want to know.
Dave[/quote]

Thanks for that report. I did see once several weeks ago that my plugin instance didn’t come back after a maintenance window, and it seemed (unfortunately not definitive) to have to do with stale DNS cache – as in, Vera had invalid DNS cache information so the plugin was trying to reach an IP address that wasn’t answering any more. When I ssh’d to the Vera and made some DNS queries, it immediately cleared up. This was sadly not very scientific, but all I could see at the time. If you had any log information to send me, I would certainly take a look at it.

watou[/quote]

watou - it happened again (lost Nest login), and now I have some log data for you. I looked it over briefly, and I’m not sure that there’s anything that would help you. Regardless, I’ll pm it to you.

[FYI - I’m on version 1.0–the app store isn’t pushing 1.1 to me for some reason.]

Dave

[quote=“watou, post:193, topic:171456”][quote=“RichardTSchaefer, post:192, topic:171456”]@watou
Thanks for the quick feedback … If looks like if I detect your device type I can send standard Thermostat commands …[/quote]

I believe so. Garrett’s Android app was able to work correctly with it before even knowing I had a different device type, so that’s a good indicator (I think).

Will your service point present a clean programmatic interface for others to use, by any chance? I have some ideas… ;)[/quote]

SQ remote seems to work fine with it too!

[quote=“DaveL17, post:194, topic:171456”]watou - it happened again (lost Nest login), and now I have some log data for you. I looked it over briefly, and I’m not sure that there’s anything that would help you. Regardless, I’ll pm it to you.

[FYI - I’m on version 1.0–the app store isn’t pushing 1.1 to me for some reason.]

Dave[/quote]

Thanks, Dave! You should have my PM reply. I strongly recommend pulling the 1.1 plugin version, since the last maintenance event at nest.com made a big change (for LuaSocket/LuaSec code) in changing thermostat state. It shouldn’t affect passively receiving status polls, though, but best to be up to date. Either way, full log data might illuminate the situation. Thanks for taking the time to help me track this down.

watou

[quote=“watou, post:196, topic:171456”]Thanks, Dave! You should have my PM reply. I strongly recommend pulling the 1.1 plugin version, since the last maintenance event at nest.com made a big change (for LuaSocket/LuaSec code) in changing thermostat state. It shouldn’t affect passively receiving status polls, though, but best to be up to date. Either way, full log data might illuminate the situation. Thanks for taking the time to help me track this down.

watou[/quote]
Thanks watou. PM’d you a link to the log on Dropbox.

Happy to help any way that I can.
Dave

I wanted to follow up on the troubles I was having with Nest logins. The trouble stems from problems I’m having on another front, and are not related to the plugin.

Cheers to watou for going above and beyond in working with me offline to zero in on what my problem actually is.

Thanks watou!

Hi Guys, can someone educate me on something-

I’d like to buy 2 Nests and use the plugin, but I need to understand what the investment looks like and how it would integrate in my scenario.

For this plugin, do I need to buy a Vera 3? Would a Vera lite work? I’m just trying to understand what is the minimum requirement to use a plugin.

Hypothetically, could I then register the Vera as a Zwave device on my Honeywell Tuxedo Touch, register the Nest as a therm and also control the therm through the Honeywell?

I’m sorry for the basic questions… very new to this. The answers to this question will essentially determine if I am going to go to Nest 2’s or if I am going to stick with some RCS Technology (ie Trane) therms.

Thanks all.

Brian

This is pretty awesome. I’ve been looking at the Neat theromostat also and was curious if it would work with verde. Now does it work with veralite or only vera3?