Central topic for questions/discussing the Google Nest App
You can use this topic to ask questions and share your experiences with the App or Devices supported by the App with community members.
This thread is not actively monitored by the Developer. For official support use the e-mail link in the AppStore [Support Contact »]
To update the this topic ask one of the moderators or reply.
Reserved
I’ve just installed the newly released Google Nest app, which is supposed to support live camera streaming from the Google Nest Hub Max, as well as motion detection based automations.
I first tried adding a Nest Camera device. The app successfully discovers the camera (it doesn’t explicitly identify it as a Nest Hub Max Camera, but that’s the only Nest camera I have). When I select the device, I get the message: “All good. This device works fine, but you cannot control it.”
I also tried adding the Nest Hub Max itself. The app finds the Hub Max, but when I select it, I see the same message: “All good. This device works fine, but you cannot control it.”
In both cases, there are no controls available and no live camera stream. I granted all permissions during the pairing process, and the camera on the Hub Max is enabled (the physical camera/mic switch is turned on).
Any ideas what might be causing this?
Just replying to myself here (in case anyone else is wondering)…
Live video streaming isn’t supported for Nest Cam devices (including Nest Doorbell), which makes the whole thing fairly useless, especially for the video doorbell, since it can’t actually show you any video 
Only motion triggering flows works.
Hi Peter,
Thanks for the heads-up. This is actually about the “Google Nest” Homey app from the app store, and it affects not only the Nest Hub Max but all Nest camera enabled devices in general. I’ve updated the topic title to reflect this by using the app name.
Cheers,
Alex
Interesting solution, but it wouldn’t work for me. Thanks anyway.
I bought a nest hub max as well and I just can’t add it to Google home or nest. It seems to be a issue that is there for a couple of years and google just doesn’t do anything to solve it. If you add it first before any other camera device it should be ok. Till now I have not been able to add it though. Total crap this camera stream option.
I have the same problem. In the app, if I long-press one of the camera cards, I get a “loading stream…” and a spinner, but nothing ever happens.
Hell, even open source solutions like the Google Nest SDM for Homebridge works better then this paid stuff… Weird.
The Nest app can set the cooling temperature from a Flow, but there is no way to read it or to notice that it changed. A Flow can push a value into the thermostat and never get it back.
Cards today:
So target_temperature.cool has an action but no trigger and no condition. The thermostat mode has a condition but no trigger. The HVAC state has neither.
The values are already on the device — nothing extra has to be fetched from Google. This is a HomeyScript dump of a thermostat paired through the official app:
target_temperature = 22 (Heating temperature)
measure_temperature = 25.3 (Temperature)
nest_thermostat_mode = cool (Thermostat mode)
target_temperature.cool = 25 (Cooling temperature) ← no Flow card
nest_thermostat_hvac = cooling (HVAC) ← no Flow card
HomeyScript can read it, but a script has to be polled from a timer, so it can never be a WHEN card — a Flow reacts to a setpoint change late, or not at all.
Why it matters: in cooling season the cooling setpoint is the setpoint, and the heating one is inert. Mirroring the setpoint onto other climate devices, nudging fans or blinds when someone turns the temperature down, logging or notifying on changes — none of it has anything to attach to for half the year.
What I’d like:
One detail worth flagging for whoever implements it: a thermostat in heating mode reports target_temperature.cool = null and flips back to a number when the mode changes. That should read as unknown rather than falling back to the last number — don’t fire the trigger when it becomes null, and let the comparison be false while it is unknown. A cooling setpoint is known condition makes that guard explicit.
I hit this myself and built a small read-only app as a workaround — it subscribes to a thermostat paired through the official Nest app and mirrors the values onto its own device so they gain Flow cards: GitHub - moKorean/com.lomohome.nest: Mirror a thermostat's cooling setpoint (target_temperature.cool) into Homey Flow · GitHub
It works, but it is the wrong shape: an extra device per thermostat, for values that are one card away from being usable already. It is MIT-licensed, so the capability mapping, the null handling and the card definitions are there for the taking if any of it is useful.
