Amazing development. Thank you!!! Finally, I can get my Nest thermostat integrated. Whow.
Thank you for this! I’ve got the integration set up, but for some reason, the 2 Nest Thermostat Es that I recently added to my home are not showing up with this integration. I have 2 regular Nests (2nd and 3rd generation) that are working fine. They all show up on home.nest.com. Anyone know what I could be missing?
Try this. I have been try to get mine to work for a while and just followed his instructions and it works.
So that others can skip some of the investigative work I did this afternoon, let me mention the following interface for accessing event data from Nest cameras:
headers = {
'User-Agent': USER_AGENT,
'X-Requested-With': 'XmlHttpRequest',
'Referer': 'https://home.nest.com/',
'cookie': f"user_token={self._access_token}"
}
# grab device event data occurring between start and end
r = self._session.get(url=f'{self._camera_url}/cuepoint/{camera}/2?start_time={start}&_={end}', headers=headers)
The start and end values are UTC time in milliseconds. This will retrieve a sequence of events between {start} and {end} associated to the camera specified by {camera} (which is the uuid of the device). I am using this to generate events like:
"event_type": "nest_camera_event",
"data": {
"start_time": 1591577186623,
"end_time": 1591577192515,
"types": [
"face"
],
"face_name": "James",
"zone_ids": [],
"importance": 100,
"name": "Media Room"
}
The possible types include at least ‘person’, ‘motion’, ‘face’, ‘sound’, ‘doorbell’, ‘person-talking’
With all the usual disclaimers about being undocumented, unstable, subject to change, etc., this allows for some pretty powerful stuff.
Hi folks
Installed the integration. Two thermostats showed up.
How do i add them to lovelace, sorry for noob
On the main Lovelace page, click the three dots top right, configure UI, click the orange plus sign bottom right, scroll through the cards until you find thermostat and click it, choose the entity name for you stat (it is probably already prepopulated with one), click save. Rinse and repeat for all stats.
thank you for reply, im doing it so. it says im in yaml mode. I guess i am
So i go to unused objects, and choose one of the thermostats (strange they are like sensor with just temperature, not a thermostat)
enter it inside my lovelace.yaml
and get the following error
in developer page it is seen as like this
I noticed that when you turn the fan mode to on it only stays on for 30 minutes, is there any way that it can stay on continuously? Thanks.
Can anyone point me at what i am doing wrong?
I think it should be as follow if you use the UI to add the entity:
type: entities
entities:
- sensor.upstairs_thermostat
Tried this bro, same error, just a - added in front of sensor word in error message
Didnt help
Would there be any chance of getting the Nest Guard to work. I would like to know the status of the different door sensors. So if a door is opened or left open.
Do they not show up as climate devices?
Do you have the following in your configuration.yaml (or something similar):
badnest:
issue_token: !secret nest_token
cookie: !secret nest_cookie
region: eu
climate:
- platform: badnest
scan_interval: 10
Also do you have any other lines starting with “Climate”
What type of thermostat are they? And do you see anything like the following in the home-assistant.log when it starts up?
2020-06-09 22:35:18 INFO (MainThread) [homeassistant.components.climate] Setting up climate.badnest
...
2020-06-09 22:35:18 INFO (MainThread) [custom_components.badnest.climate] Adding thermostats
2020-06-09 22:35:18 INFO (MainThread) [custom_components.badnest.climate] Adding nest thermostat uuid: <UUID>
@TheMattS thanks so much for your work on this. After a little fighting I was able to pull all three of my cameras in using Nest auth last night and they appear to be working, with one exception. Only one of the three cameras appear to pull in at it’s full HD resolution, the other two appear to only pull in thumbnails - and when clicked in lovelace actually get smaller when they are “enlarged”. Any idea why? All the cameras have the same properties in developer states.
EDIT: Disregard the first question. Google in their infinite wisdom failed to change my resolutions back on 2 of 3 cameras when they lifted the COVID related bandwidth restrictions. Changing the cameras in Nest directly resolved this if anyone else sees it.
Also, since adding bad nest, I randomly get "authentication failed from (what ever my current device IP is) when accessing the cameras as a notification in HA. Just an annoyance as it still appears to be working.
Token and cookie - yes man
In other case i could not see the thermostats at all ( badnes would be unable to login without that info)
my logs show following, badnest starts and loads thermostats as temp sensors not like thermostats (wtf)
and there is no Climate in logs. ( ithought it should be default)
Do you have this in your configuration.yaml too?
climate:
- platform: badnest
scan_interval: 10
Which of the Nest Thermostats do you have?
#google NEST
badnest:
issue_token: !secret nest_token
cookie: !secret nest_cookie
region: eu
climate:
- platform: badnest
scan_interval: 10
camera:
- platform: badnest
that is a string from my config yaml
I have 2 nest 3rd gen thermostats and 2 nest sensors, that monitor temperatures in other two rooms at night. so its total 4 nest pcs. that are all shown as temperature sensors (only two should be as sensors, other two should be thermostats)
Try removing the spaces in front of “climate” so it sits inline with “badnest” and “camera”
Im not sure how to write it correctly. Can you help me with your idea please, by writing the complete string i should put it?
badnest:
issue_token: !secret nest_token
cookie: !secret nest_cookie
region: eu
climate:
- platform: badnest
scan_interval: 10
camera:
- platform: badnest
sensor:
- platform: badnest
“climate:” has to start in the same column as the “camera:”, “sensor:”, “badnest:” lines - if it starts in a different column it is in a different configuration block, so no spaces before the “c” in climate on the line it is on.