Use with Nest Temperature Sensor?
Answered
Good afternoon,
I know that Nest recently released remote sensors for rooms. I understand that I would need a minimum of one puck with the smart vents, but would the sensors be adequate for feeding room information to the smart vents?
I ask as the nest options seem to be priced a bit lower and suspect they would integrate seamlessly with the app.
Thanks!
-
I have a Nest protect, so I cant test it on an account that doesnt have one - But I can confirm that it works with a migrated account, I moved my account about a year and half ago. Overall, if a Nest Protect is required, you could just make that a requirement for Flair users.
It works great in Home Assistant - Its a public API, so it should be easy enough to get Googles approval for it.
-
So we did some additional research - as best we can tell there is no official remote sensor api support from google and instead it appears that home assistant instead has reversed engineered the request/response for the nest protect to make things work. While it doesn't present risk wrt a one off user to use this, without official api support it would not be commercially acceptable to integrate in this way. Here are the docs for the api https://developers.google.com/nest/device-access/api
There isn't an option for communicating with the remote sensors under the thermostat section and there isn't anything about communicating with their smoke alarms. We would love to integrate with the remote sensors but we don't currently see an officially supported way - perhaps we are missing something? -
To be frank, this response seems like a cop out.
"...home assistant instead has reversed engineered the request/response for the nest protect to make things work..."
Why can't you guys reverse engineer the request/response. The home assistant integration was built by unpaid developers."...While it doesn't present risk wrt a one off user to use this..."
2. Doesn't present a risk to a one off user? How many people do you think are using the home assistant integration successfully? Simply place a warning in the app for using the nest temperature sensors. State that because there isn't 'official' device support from the nest API yet, there may be unexpected results and you are not responsible for the system not behaving exactly the same way as with the pucks. If the user wants to make sure everything works flawlessly then they need to purchase a puck.
At least give us the option to use this feature or not. Again, it feels like you guys are just dragging your feet because you want to maintain the revenue stream of the pucks. I'll reiterate. I will not buy $120 puck for each room of my house instead of buying a $33 nest temperature sensor. If you came out with a temperature sensor of your own for ~$35, I would buy that instead in a heartbeat. The google home app is awful for the thermostats, I'd much rather use flair. -
Sandeep - you would also need to have the ecobee thermostat as thats the only thing that can directly communicate (radio) with ecobee remote sensors.
-
I haven't gotten to play with it yet, but I have a feeling the new Scripts interface may have a way to help us with this. They just launched it so let's give it a shot.
https://home.google.com/automations -
Another update to hopefully keep this discussion going!
https://www.theverge.com/2024/5/15/24157154/google-home-api-matter-smart-home-chromecast-google-tv
-
I'm still waiting on integration with Nest temperature sensors. Over $100 for each vent is already on the pricey side for me so I'm not also going to spend over $100 additional for a sensor for each room. The link that Chandler posted 2 months ago said Google opened the API Flair said they were waiting for. Integrate those Nest Temp Sensors, and I'll be getting a bunch of vents.
-
https://developers.googleblog.com/en/build-the-future-of-home-with-google-home-apis/
It looks like Google Home APIs are going public. Will Flair commit to making their smart vents compatible with Nest sensors?
-
We have asked for this many times from the Google team without any luck. As soon as its officially available we can jump on integrating as we have done for many brands now. Our ask/suggestion is to make sure you are contacting Google with the request given that's the current bottleneck.
-
Hi everyone,
Following up on Chrissie’s note above about the bottleneck being on Google’s side: Flair can’t pull room temperatures until Google opens up access to their remote sensors in their software system (the Smart Device Management API).
To get Google’s engineering and product teams to actually prioritize this, I have submitted a formal feature request directly to Google’s Issue Tracker (their internal public roadmap and bug tracker).
Google decides what to work on based on how many people "Star" an issue. If enough of us upvote it, their engineers will see the demand.
If you want your Nest pucks to work with your Flair vents, please take 60 seconds to do this:
-
Click this direct link (make sure it opens the webpage directly in your browser, rather than searching Google):
https://issuetracker.google.com/issues/562567698
(Alternative method: If the link above gives you trouble, simply go to https://issuetracker.google.com/, make sure you are signed in, paste562567698into the search bar at the top, hit Enter, and click the Star icon on the issue.) -
Sign in with your normal Google/Gmail account (top right) if prompted.
-
Look at the very top of the page next to the title (
[SDM API] Expose Nest Temperature Sensors...). -
Click the Star (★) icon so it turns solid.
Important tip: Please do NOT post "+1" or "me too" comments on the ticket! Doing that sends an email notification to everyone watching it and can cause Google moderators to restrict commenting. Clicking the Star (★) is the only thing Google tracks to measure community demand.
Let's get this starred so both teams can finally bridge the two systems.
-
-
Hi M. A. and Brett Hebert,
I fixed the link in Brett's post and the URL now works.
Thank you for doing this. We appreciate it!
Regards,
The Flair Team
-
There appears to be some positive momentum at Google - see below:
If you're reading this post and haven't already done so, please see my September 17, 2026 post and follow the instructions to indicate you're affected by this and are requesting Google to fix it. Google will only act if we continue to maintain pressure through the Issue Tracker. Please do your part, it only takes ~60 seconds to indicate interest.
Please sign in to leave a comment.
Comments
52 comments