In conjunction with the launch of its new Nest Learning Thermostat, Google is launching an updated plugin to display and manage thermostat settings in its app. It turns out that this redesign also applies to older models.
The updated user interface for the Nest Learning Thermostat in Google Home more closely mirrors the appearance of the device in the Home app itself. The heating or cooling controls, current temperature, and humidity in the room will be displayed at the bottom.
In fact, one would assume that the new user interface would be available only for the new product, but it seems that this is not the case.
Android Police noticed that an updated plugin interface suddenly appeared in the Google Home app for the old generation of Nest Thermostat. They didn’t specify which thermostat they used, but it’s one of Nest’s legacy thermostats, and it’s not a 2020 model. In fact, based on the user interface, it was assumed that it was from the Nest Thermostat E.
Update
As we approach the debut of Google’s new Nest Learning Thermostat, the new user interface is becoming more common for users of older Nest thermostat models. Over the past few days, many more users have seen the updated design. Supported models include the 2020 Nest Thermostat and the Nest Learning Thermostat (3rd generation), so it looks like the updated user interface will be available for all thermostats.
It is noteworthy that the 2015 Nest Learning Thermostat shows temperature sensors in the Google Home app just like the updated model (see photo).
One of the features of Google’s flagship display is that it can extend the effective range of some devices, such as, for example, Nest Detect or Nest Yale smart lock. The fact is that these devices do not connect to the network via Wi-Fi, and they use “bridges,” namely Nest Connect, Nest Guard, or Nest Hub Max.
Google recommends repositioning your connected Nest devices to keep them connected after the update is released if you are using Nest Hub Max as a bridge/repeater. However, Google offers some users a free Nest Connect if it isn’t possible to move devices for their families.
Back in June, Google reported they would drop the range extender feature in future updates to the Nest Hub Max. At the time, Google called it the “Thread-Matter update.” The technical support page notes that the Matter update will have the tag “F7” in the name, and now the current stable update is “F6”. The “F” in the code stands for Fuchsia, the name of the operating system for smart devices.
Nest Hub and Nest Hub Max in the preview program will soon receive F7 updates – 7.20220419.2.166 and 7.20220419.2.164.
Apart from the disappearance of the bridge (or range extender) features, we don’t expect any significant changes with the F7 update for Nest Hub and Nest Hub Max.
Google also said that while the update would add support for Matter devices, it won’t make Matter available on your home network. That will roll out later this year with Matter support on Android devices.
The news reports that some Android users have started receiving system updates, and Matter device controls have appeared in the interface. These controls appeared in the new Matter devices & services item in the Devices & sharing section of the Google account settings and allow you to connect new devices. There is now a toggle to show notifications if there is an available unconnected Matter device nearby. These controls are currently unavailable to the public, but we expect them to become available in the coming weeks.
Quickly see who is at the front door using your TV.
Imagine you are comfortably settled on the sofa and watching the latest episode of your favorite series on Netflix with your children, but someone rings the doorbell, or you hear a noise from the children’s room. If you have a Google Chromecast at home connected to your TV, you don’t have to take out your phone or crane your neck to look at the Nest Hub display— ask Google to show you the feed from your doorbell or security camera right on that TV.
Any compatible security camera from Nest, Arlo, Wyze, Eufy, Netatmo, TP-Link Kasa, and more can be streamed live to the big screen using Chromecast. And starting last month, you can stream video from the new Nest cameras if you have a Chromecast with Google TV.
Below is a list of new Nest cameras you can now use to stream video.
Nest Cam IQ (indoor and outdoor — now discontinued)
Nest Doorbell wired (formerly the Nest Hello)
Nest Cam (indoor, first-gen)
(*Only works via Chromecast with Google TV)
With your cameras and Chromecast enabled, you can easily set up streaming to your TV. First, ensure you connect your camera and Chromecast to the same Wi-Fi network. Then follow these steps.
Add your Chromecast TV to the Google Home app
First, you need to make sure you connect your Chromecast to the same account as your smartphone or tablet.
Open the Google Home app.
Find the icon from your Chromecast – it will be in the room you placed it in during setup.
Tap and hold the icon.
Click on settings in the upper-right corner.
Tap on “Recognition & Sharing.”
If you didn’t connect the device, you would see a banner in the upper part of the screen titled “Enable voice control and more.”
Tap the banner and follow the instructions to link the Chromecast with Google Home.
However, suppose your device is already connected. In that case, the banner won’t be there, and your email address should be displayed under “Linked account(s),” indicating that your TV is already connected.
Watch video from your video call or security camera on your TV
Using voice commands, you can view a live feed from any compatible security camera or video call directly on your TV.
Say “OK, Google” or “Hey, Google” to your smart speaker or Google Assistant on your smartphone, and then “followed by [camera name] on [TV or Chromecast device name].”
On the Chromecast with Google TV, hold down the Assistant button on the remote and say the wake-up phrase “OK, Google” or “Hey, Google,” and then “show [camera name].”
To stop streaming, say “stop [Chromecast or TV name]” or tap on the “Home” button on the Chromecast on the Google TV remote.
People don’t often mourn recently lost technology, but Chromecast Audio is one of the few examples when this technological idea was almost perfect. However, it was quickly buried in “Google’s hardware graveyard.” It’s been three years since then, but there are still no reliable alternatives to this small device to transfer audio from Google.
The Chromecast Audio’s launch wasn’t a flashy event since it was introduced alongside Chromecast (video) 2nd Gen in 2015. The thing that killed Chromecast Audio was the same price as a regular Chromecast with video support. That’s the reason why the production of devices stopped in 2019.
Google hasn’t given a reason why they killed Chromecast Audio, but it doesn’t take a genius to figure that out. There isn’t anything special about this USB device when the Google Nest Mini speaker exists for the same price. Since 2019, Google has focused on smart speakers. At the same time, the Nest speaker line was better positioned to promote its Google Assistant voice assistant. Of course, the two products catered to very different users, but it was clear that Google would push in the market with its smart speaker.
Then, Google had a patent dispute with Sonos over streaming patents. The patents have certainly impacted Google’s range, but Chromecast Audio had a huge influence particularly. In addition, the patent disputes have already been resolved, and if the rumors are true, it’s time for Chromecast Audio to make its return.
Smart speakers can’t compete in the world of high-definition streaming.
Smart speakers have a long life cycle. Combined with low prices and frequent sales, most users had already bought them. With the release of updated speakers, there are also no obvious benefits, so why should the user upgrade?
Music streaming is considered the best use case for smart speakers. High-resolution audio is becoming commonplace in music services. However, some brands imagine it differently.
Echo Studio from Amazon was made to service the audiophile market, but it’s far from the most popular product in the Alexa line. Apple also ditched the full-sized HomePod and replaced it with the Mini. Google Home Max was the leader in the high-quality audio segment, but it couldn’t gain popularity due to its high price.
There is one thing in common for these devices – the high price. Audiophiles understand the value of good speakers for high-quality sound, but to achieve that, it’s better to spend money on regular high-end speakers.
Chromecast Audio combines the convenience of streaming audio with the sound quality of your own speakers.
Chromecast Audio was and still is the perfect solution for users who want to combine the convenience of audio transfer with the quality of their high-end equipment. For the user, the device already offers optical output for connecting your high-quality DAC, but if Google wants to improve the device more, they could consider more modern formats such as MQA. This simple and cheap USB device is perfect for streaming Hi-Fi audio.
The Cast protocol is almost perfect for streaming
Apart from hardware, Chromecast Audio was also perfect thanks to the Cast protocol, which conveniently combines local media and streaming services. For audiophiles who have a massive music library, the protocol makes streaming to one or more speakers easy. It also nicely integrates with Android apps. Whether it’s your favorite podcast app or streaming radio service, most will have support for streaming.
The Google Cast protocol supports local and online content. Amazon and Apple can’t compete with that.
Alternatives like Alexa speakers just can’t do that. Instead, you need to enable “skills” for each service. Local music playback is also incredibly frustrating on the Echo speakers. And Homepod is not allowed to be used for anything outside the Apple ecosystem.
Once the patent lawsuit is settled, Chromecast Audio could be the perfect home audio product for those who want higher sound quality than smart speakers and the complete freedom to stream audio content from any source.
In my opinion, the updated Chromecast Audio will become the perfect solution for transferring sound across the home.
If people are ready to pay three times the original price to buy Chromecast Audio, then the market exists for it.
It’s been three years since Google stopped production of Chromecast Audio, but demand for the product hasn’t dropped. Resale prices have been steadily increasing and reached nearly $120 on eBay, which is three times the original price. Of course, you can’t take eBay prices as an indicator of demand, but it’s pretty clear that if people are willing to spend that much, there are reasons for Chromecast Audio to come back.
First introduced in 2016, Google Wi-Fi routers provide a fast and stable Internet connection at your home. The Internet connection is on a “web” network. Besides, Google made it as simple as possible to manage devices.
A bit of history
The original Google Wi-Fi, just like its second version, uses the same hardware as a regular home router that connects to your modem.
In 2019, the line included two different pieces of hardware – a router Nest and an access point Nest Wi-Fi. By the way, the access point uses double features, acting as a Google Assistant speaker.
Google plans to bring back the unified design of the original Google Wi-Fi. You can buy a new Nest Wi-Fi for 1, 2, or 3 pieces in a box, depending on your needs or the area coverage of your home. But for now, we can’t say that the new router, like its predecessor, will be equipped with a Google Assistant speaker.
Pros of Wi-Fi 6 in the updated router
Back in 2019, due to the official launch of the Wi-Fi 6 standard, the Nest Wi-Fi became obsolete in the eyes of some enthusiasts. Now Google has confirmed that the new devices will benefit from Wi-Fi 6 and possibly even Wi-Fi 6E.
Ideally, the Google Wi-Fi router with Wi-Fi 6 support will run at 9.6 Gbps, which is a significant improvement compared to 3.5 Gbps, the maximum value for Wi-Fi 5. When you upgrade individual network devices to those that support Wi-Fi 6, you will notice an improvement in network performance.
The new Wi-Fi 6E standard will also use the third 6 GHz spectrum to counteract potential interference.
Turn on and forget.
Although Wi-Fi 6E does not directly affect your maximum Internet speed, it should bring you closer to the “best case scenario” for your local network. Plus, you don’t need to know much about Wi-Fi 6 or 6E because Google Wi-Fi makes it easy.
There are rumors that the updated Google router will release in several colors. The new device will have a color palette that will complement existing devices released by Google this year.
A little over a month ago, I made a review on the Nest Learning Thermostat. It is a handy device that will support the comfortable temperature inside your room and will save your money on heating at the same time.
As you know, Google owns Nest, and how it often happens in big companies, not all areas of production keep up with user requests. And the fact that Google has partially closed the Nest API has been sad news for independent developers. If you use the Nest app, which manages only its own devices, you may have paid attention to the fact that the app did not update for quite a while. It also does not have that many devices.
I think it will be much more convenient for anyone to control their devices from within one app. I chose Home Assistant as the system since you can integrate many devices from different brands, manage them, and add any automatization algorithm.
I must warn you: to get access to the Nest Smart Device Management API you will need to pay 5 dollars. It is a one-time payment for API access.
After finishing setup through Home Assistant, you will gain access to these essences: Climate, Sensor, Camera.
Registering device access
For this step, enable Nest API and create an account for Home Assistant to exchange info with the Nest API.
Creating and configuring Cloud Project in the Cloud Console:
Click on “OAuth consent screen” and start setting it up.
Choose “External” (this is the only option if you are not a G-Suite user), and then click on “Create”.
On the “App Information” screen, enter the App name and the User Support E-Mail, and then type in your E-Mail address in the “Developer contact email” section. They are displayed only during the OAuth to give Home Assistant access to your account. Click on “Save” and “Continue”. Do not add unnecessary info (for example, the logo) to avoid additional Google checks.
On the “Scopes” step, click on “Save and Continue”.
On the “Test Users” step, add your Google account (example@gmail.com) to the list. Click on “Save” in your test account and then “Save and Continue” to finish the process.
Go back to the OAuth consent screen and click “Publish App” to set the “In Production” status.
The warning states that your application will be available to any user with Google Accounts that you have entered on the application information screen. It does not compromise your Google Account or your Nest data.
Make sure to disable the “Testing” status since you will be logging out of your Google account every week.
Configuring OAuth client_id and client_secret in the Cloud Console
At the end of this section, you will get the client_id and client_secret you need for the next steps.
Go to the “Credentials” page and click on “Create Credentials”.
Select “OAuth client ID” in the drop-down list.
Choose “Desktop App” in the “Application type” type field.
Give an understandable name to your credentials.
You will now see a message created by the OAuth client. Pay attention to “Client ID” and “Client Secret”. They are crucial to the next steps.
Creating device access for project_id in the Device Access Console
Now that you have set up the authentication, create the Nest Device Access Project, which requires $5. When done, you will have device access to project_id, which is crucial for further steps.
Check the “Accept the Terms of Service” and click on “Continue to Payment” where you will need to pay 5 dollars.
The “Device Access Console” should now be displayed. Click on “Create project”.
Give a name to your project and click on “Next”.
You then are prompted to enter the OAuth client ID you created earlier in the previous section. Click on “Next”.
Turn on “events” by clicking on “Enable and Create project”.
Note the Project ID. You currently have project_id, client_id, and client_secret required for Home Assistant.
Setting up Home Assistant
Now you have everything required to set up Nest in Home Assistant. Open “configuration.yaml” and write according to the sample you see below.
# Example configuration.yaml entrynest:
client_id: CLIENT_ID
client_secret: CLIENT_SECRET
# "Project ID" in the Device Access Console (not Cloud Project ID!)project_id: PROJECT_ID
Be sure to restart Home Assistant in the “Server Controls” section.
Setting up devices
After you added a Nest configuration entry to “configuration.yaml” and rebooted Home Assistant, you need to add Nest integration through the user interface. To do this, you can use the “My” button:
You can do the same manually:
Go to your Home Assistant interface.
On the sidebar, click on “Configuration”.
In the configuration menu, select “Integrations”. (in version 2021.12 Devices & Services)
In the lower right corner, click the “Add Integration” button.
Use the search box, select “Nest” and follow the instructions.
Setting up the Nest integration will guide you through the steps of authorizing your Home Assistant to access your account on Nest devices.
Setting up OAuth for Device Authorization
This section will allow Home Assistant to access your account by generating an OAuth token.
Select “OAuth or Apps”, because we created credentials for the computer programs above in the Google Cloud Console.
Click the “authorize your account” link.
A new tab will open where you can select your Google Account. It should be the same developer account you set up before.
The Google Nest permissions screen will allow you to choose which devices to configure and select from several of your homes. Maybe you want to turn on everything. However, you can skip any feature you do not need to use.
You will get redirected to another account selection page.
You may see a warning screen stating that Google has not tested this program because you have just set up an unverified developer workflow. Click on “Continue” to continue.
You will then get prompted to grant additional permissions. Click on “Allow”.
Confirm that you want to grant permanent access to Home Assistant.
Copy the token.
Insert the token into the Google Home Assistant Link Account dialog box.
The next step is to enter the Cloud Project ID to receive updates from your devices. Open the Cloud Console and copy the Project ID.
If everything is as planned, you will see a working Nest integration.
Using automation and triggers
Nest integration makes device triggers available and the ability to enable automation in Home Assistant. For complete information, see the Home Assistant Automation Guide.
You can use nest / set_away_mode to set Home or Away mode:
# Example script to set away, no structure specified so will execute for allscript:
nest_set_away:
sequence:
- service: nest.set_away_mode
data:
away_mode: away
Controlling the thermostat
The Nest climate platform allows you to control the thermostat from Nest. However, please note that due to the limitations of the European Nest E thermostat, integration with the Home Assistant is not possible for this thermostat.
After setting up the integration and adding the thermostat card to the Lovelace interface, you will be able to control your Nest devices via Home Assistant.
Also, it is now possible to add new climate entities in triggers and automation, calling the appropriate service using previously created configuration files. You can view the templates in the Home Assistant developer tools.
