Actually my thanks were directed towards RonnieBee who told me to clear the port from the ‘External Url’ setting in the General Configuration page. The ‘instructions’ I have been following were in post 263, I had been confused by the mismatch between the callback url and allowed url in OAuth, and didn’t think to look in the settings page,
but Daniel, thank you as well for all your help. I now have the integration loading. (Still some issues with the subscriber, but that’s another thread!)
1 Like
Wow that’s nice!
But this way the thermostat start heating home at fixed time, and i already do that with the alarm on my phone and nodered. If you set a time on the nest schedule the house at that time it’s already at the temp setted (or at least nest tries to do that based on it calculation), looks like i can’t do that right now.
Since it’s a native integration i was hoping that all nest fuctions were available, maybe in the future
So I figured out why updates weren’t coming even though I had set up everything correctly. You need to initiate events for the first time manually.
Initiate events
To initiate events for the first time once the Pub/Sub subscription has been created, make a call to list your devices as a one-time trigger:
curl -X GET 'https://smartdevicemanagement.googleapis.com/v1/enterprises/project/devices' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer token'
The subscriber sends that request on start-up to get the initial device list… Very odd that would help, and thanks for the info.
agreed, not sure if this was a unique scenario to me. For others having the same issue, two things worth checking:
- the api traffic data/graph
- history of ack and unack messages from the pub/sub
for me, both were zero indicating that the messages were not being sent. Once I did the manual initiation, things started to function normally, and I am getting regular updates, and I am seeing activity across both the points above.
@Guddu_Mony Did you follow my instructions from the post above? The Initiate Events definitely doesn’t need to be run:
Yes, I did that step as well as I followed Mulai | Device Access | Google for Developers before post #263 was updated. I kept skipping page 4 though since the bottom of page 3 references troubleshooting and I did not have anything to troubleshoot at that point so I kept skipping Next 4. Subscribe to Events…. I think I was thinking the integration would do that? Once I completed page 4 everything was working.
Hmm, I think you must be referring to Nest Sense: Auto-Schedule, Time-to-Temp, Early-On, Sunblock and Leaf settings. You would be correct that there’s nothing like this currently in HA that I am aware of. Someone would need to develop a new Nest-like scheduler add-in that would monitor temperature changes after heating was turned on to learn how long it took the system to heat from the current temp to the desired temp so next time early-on could be triggered to get the temperature to the desired temp at the scheduled time (or cooling as the case may be). Not quite sure what Sunblock does or how it works. Oh and let’s not forget Air filter reminder!!
None of the above info is exposed in the current API. Maybe if Google gets hundreds of requests for it we might see it in a year, or two, or never…
1 Like
Yes i think It’s called time to temp. You destroyed my hope 
I had followed the official directions. I did run through you instructions to check that I had completed all of them.
Its possible that I made an error somewhere, but everything seems to be working perfectly after the manual initiation.
Any further luck with this one? I’m hitting the same thing. I registered and paid my $5. My Nest account wasn’t initially migrated, but I did migrate it so Nest is now using the same e-mail address as the account I registered. Tried incognito browser – same thing.
On a separate note does the integration support any other functions than the camera feed for the nest Hello? kike person detection etc. Just curious, as I think I saw it in the permissions list from google.
If these events could be used in HA, it could make for some very nice automations.
Motion/person/sound/chime events are in progress https://github.com/home-assistant/core/pull/43548
1 Like
Thx : The subscription_id is more clear and it’s work
Yes, was able to migrate to using the new API with relative ease. My recommendation is to take your time, there are lots to get wrong but if you follow the instruction you should be fine. There is a lot of help with links in the thread above.
I dont know if its a bug at this point or I have something misconfigured. I went through the steps from Townsmcp post. If I reboot or reload the integration, the nest thermostat information updates, otherwise it never does. Sorry if it’s been mentioned, just a lot of posts in this topic. Thanks
RTSP stream from camera giving various issue in HA. Unable to pull this into AppDaemon also, will only display still images.
Same here, irregular updates, sometimes minutes, mostly > 30-60 minutes… Following your post.
I don’t get any updates. Goes for days with nothing unless I reload or restart HA
@Townsmcp (James),
You are the man of the hour. I spent all last night and most of today trying to get this integration working. Came across your instructions and I’m up and running in least than 30 minutes. {{ kudos, my friend }}. It’s a shame HA team could not accomplish such simplistic instructions.
1 Like