Nest Thermostat plug-in

[Dragon470]

In short yes the thermostat would think everyone is gone.

All thermostats should be in a public location that gets the most traffic. People who only have 1 thermostat and it is inside their bedroom or other location that doesn't really get foot traffic should be moved. I have told this to many people and have heard from several say they are much more comfortable. This really may not be best or possible in all house I know.

For nest thermostats that are in bad locations you can turn off the auto away. Programming special days or weekly schedules can be done online already with nest.com or right on the device.

[abuttino]

But wouldn't the sound sensors still pick up the fact you are still home?

[Dragon470]

I never heard of a sound sensor being on the Nest. And this https://community.nest.com/message/3045 appears to confirm that thought. The nest has 2 sensors which regulate the away status. motion and ambient light.

[abuttino]

I never heard of a sound sensor being on the Nest. And this https://community.nest.com/message/3045 appears to confirm that thought. The nest has 2 sensors which regulate the away status. motion and ambient light.

Actually, that makes me feel at ease... Ever since google bought Nest, who knows what they share with the gov

[Dragon470]

Big changes may be coming. I am not sitting around any longer for Nest to come out with their API.

Abuttino, you might not like me again. I will be changing the function of getting information out of the plugin. I am doing this to better accept multiple nest setups. Each call (action) would have to have the accompanied nest device id (or common name)sent in the function call.

I only will be doing this so only one instance of the plugin will be polling for each nest account (multiple instances for multiple accounts would still be allowed).

This update will also change the way events are generated. If the event comes from a specific thermostat it will say that ex. Nest.Family Room.hvac_heater_state.False Some events will not have the device name in it as it is for all thermostats not just one.

I have some of this done, but got all messed up, which is why the last update ended the way it did with some of that function changed. I was trying to add in the schedule information when things just did not go according to plan. The schedule information is off the agenda for now. Hopefully I will have a version to be available by the 16th for testing.

[abuttino]

I like the idea!

Don't mind change if it can be replicated without having a user editing the scripts.

I'd prefer the name of the room be a payload instead. This way you don't need to have several events of room names to activate each macro.

Also, did Nest get back to you on test thermostats for development? I am going to need this for my app as well.

[barnabas1969]

In short yes the thermostat would think everyone is gone.

All thermostats should be in a public location that gets the most traffic. People who only have 1 thermostat and it is inside their bedroom or other location that doesn't really get foot traffic should be moved. I have told this to many people and have heard from several say they are much more comfortable. This really may not be best or possible in all house I know.

For nest thermostats that are in bad locations you can turn off the auto away. Programming special days or weekly schedules can be done online already with nest.com or right on the device.

OK, thanks. I understand why you would move the Nest, but apart from the motion detection of the Nest, your thermostat should be located near the air intake of the system.

[abuttino]

There are other methods of using geofencing than Tasker. If you have an ISY99i to ISY994iR-Pro, I wrote scripts for this plugin and can use a variable status on the ISY for away, set temp and ambient temp. If you don't have an Android, you can use "MobiLinc" with Geofencing on the iPhone.

Another, much more unreliable method, is using the ping plugin for EG. I have the scripts built for another user that requested it.

This plugin is the glue that holds the Nest together for home automation and it's nice that Dragon is continuing development on it. I am considering learning more about Python to help out where possible and to make my contribution to it.

Although, Nest is a bit overdue on the API, this plugin is completely functional for all desired operations.

[Dragon470]

I will do the payload for the device name as that will require a little less rewrite. I will be starting this project tonight or tomorrow night. If the TV doesn't distract me too much.

[Dragon470]

I uploaded the beta for the multi-nest plugin. Everyone please test. Including ones with only one nest. Let me know of any compatibility issues. Besides the need to re-add the actions and then needing to disable/delete old action.

Note: The get_object action will default to timestamp if there is an error, you will just have to save the new selection.

[abuttino]

Nest.hvac_ac_state.True u"home2"

Can you make ALL events give payload on status and thermostat name?

[Dragon470]

ALL events will have [data, thermostat name or "structure"]. "structure" as of now will indicate any data that is not directly tied to an individual thermostat.

Up next schedule data output.

[abuttino]

Why has the plugin stopped working?

Is nest down?

[Dragon470]

I just looked at mine, I could not even ping (local network) my thermostat. I checked it said network connected on device. I went back and pinged again and it worked. I then tried to connect to home.nest.com it just stalls. So somebody was having problems.
My logs showed mine getting info up to 12:42:11.

Update #1 A few minutes after all this mine is now reporting just fine again. But home.nest.com still says offline once it did log on. I am sure they are just having a temporary issue. Things like this is why the thermostats can be independent when they have to be.

Update#2 I also just noticed that the outside temperature on the home.nest.com website is really off. So to me, this issue is all on their end. 13:40

Update #3 home.nest.com reports the thermostat fine, but now the plugin is offline again. 14:05

[abuttino]

Just about the same here. In and out.