Skip to main content

How to link your Wemo® devices to your Google Home


Google Home allows you to quickly and easily control your Wemo® devices just by using your voice.

There are a few basic requirements that need to be met before you can use your Google Home with your Wemo devices.
  •  A Google Home Virtual Assistant
  •  The Google Home App
  •  The Wemo App
  •  At least one supported Wemo device
 


Linking Wemo to your Google Home

The linking process is pretty easy as long as you have Remote Access working for your Wemo devices and your Google Home Virtual Assistant is set up and working properly.

Linking your Wemo with your Google Home Virtual Assistant consists of two parts:
  1. Pre-link procedures
  2. Linking your Google Home Virtual Assistant to your Wemo Home Wi-FI
Step 1:  Before linking to your Wemo Home Wi-Fi, you will need to have at least one Wemo device set up and working.
 
Step 2:  Set up your Google Home Virtual Assistant.  Next, you will need to set up your Google Home device and ensure it is working.  Click here for setup instructions.

2. Linking your Google Home Virtual Assistant to your Wemo Home Wi-Fi

Once everything is set up, you can connect your Google Home Virtual Assistant with your Wemo Home Wi-Fi to begin controlling your Wemo devices with your voice.

For the next steps, you will need to use your Google Home app.
 
Step 1:  Open your Google Home App and tap on the menu button to bring up the Google Assistant menu.
 
User-added image
 
Step 2:  Then, tap on Home control to bring up the menu.

User-added image
 
Step 3:  On the Home control screen, tap on the plus sign to begin linking your Google Home Assistant to your Wemo Home Wi-Fi.

User-added image
 
You will be taken to a list of available smart device partners.  Choose Wemo from the list.

User-added image
 
Step 4:  Now you are ready to connect your Wemo device to the Google Home Virtual Assistant.  This part will require you to toggle one of your Wemo devices.  Tap on Ready To Verify to begin the process.

User-added image
 
Step 5:  You will then be given minutes to toggle one of your Wemo devices so that the Google Home App can locate it.
 
User-added image
 
Step 6:  When found, the App will let you know which Wemo device it saw and what that Wemo did.  If this is correct, tap on Yes, that’s me.

 
User-added image
 
Step 7:  Once linked, you will be shown a list of your supported Wemo devices.  You can choose to assign rooms to these Wemo devices at this time or leave them unassigned.  Tap DONE when finished.

 
User-added image
 
Once everything has been set up, you will be greeted with a success screen to let you know you’re all set.  You will see some sample commands you can use to control your Wemo devices using your voice and the Google Home Virtual Assistant.
 
NOTE:  If the Google Home App does not detect the Wemo you toggled after a few minutes, it will let you know and ask if you need more time.  Tap on Give Me More Time to continue waiting and toggle the Wemo device again.  You may need to toggle it more than once.
 
User-added image
 
If you asked for more time and it still isn’t finding it, you will need to enter in the Name of your Wi-Fi Network and the MAC Address of one of your Wemo devices.  You can find the MAC Address at the back of your Wemo device (or under the faceplate for the Wemo Light Switch) or under the Settings & About section of your Wemo App.  Tap Submit once done.
 
User-added image
 

 
Wemo device not Detected

If detection still does not take place after doing the steps above, below are some troubleshooting tips you can try:
 
  • Confirm your phone or tablet has remote access.
  • If you are able to take your phone or tablet to a remote connection (a different Wi-Fi than your Wemo devices connect to or a cellular connection), switch to that and try controlling your Wemo devices.  If you are able to control them remotely, then remote access is enabled for them.
  • Try rebooting your router and modem.
  • If none of these steps help, give our support team a call.  For more information, click here.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k