The problem with Google Assistant on Android Wear and Google Home

A big part of the Android Wear 2.0 update is the inclusion of Google Assistant. If you've never used it, Google Assistant is like a friendlier version of Google Now that can remember things and help you by doing more "stuff" than the original could. It's pretty cool, and even though it's not been around for long we've already seen it get better and smarter. And now, it's on your watch.

Assistant is on different devices with different hardware and different abilities.

That means you can tell your watch to do things like add milk to your shopping list, tell you the weather or how traffic looks for your evening commute, or even play a movie on your Chromecast. It can do all those things and will. But Google Assistant acts differently depending on what device it's running on, and there are some things your watch can't do as well as other devices can and even some things your watch can't do at all. And you'll notice that right away if you already have a Google Home.

Google Home can't show you pictures of cats if you ask it to. If you have an Android TV, it will try to show you pictures of cats on it but will eventually tell you that it just can't do that. It makes sense because Google Home has no display. Your watch can show you pictures of cats but it also has limitations, and it's not going to be able to play the latest episode of your favorite Netflix show. It's a little frustrating but expected. At least until LG or Motorola makes a version with a projector module, anyway.

Here, kitty kitty

The internet is made of cats and now you can have them on your wrist.

If you have both a Google Home and a new Wear 2.0 watch, things can get even more frustrating. Google Assistant doesn't yet "decide" which device is best to use when trying to answer your questions. By default, any time Google Home can hear you ask Assistant to do something, it will try to do it. Even when it can't do it, or when you want it to be done through your watch.

For example, if I'm in the bathroom combing my hair and getting ready for work I might want to know if traffic on my commute looks good. If I ask Assistant, and if Google Home hears, it will answer through the Home speaker instead of showing the traffic card on my watch. Or it will do both. Or it won't do either. And there is no setting of any type to tell it what you wanted to be done in a case like this.

Google Home trumps everything else when it comes to the Assistant chain of command.

This isn't something new with your watch and people with both a Google Home and a Pixel have seen the same issues since Assistant became a thing. Your phone will tell you that things are being answered on another device and Google Home will tell you it can do that thing when it can't do it. Google knows what's up here and they have some sort of solution in the works. But that doesn't help us in the here and now.

We don't have any real advice how to get one Assistant to do some things and the other Assistant to do other things. Nobody does, and all you can do is turn off the microphone on one or the other (or both when Google doesn't need to hear things) which isn't very great. But know that it's not just you or something you're doing wrong, and we're all waiting to see what Google does to fix it since Assistant is going to be on plenty of other things in the near future.

Jerry Hildenbrand
Senior Editor — Google Ecosystem

Jerry is an amateur woodworker and struggling shade tree mechanic. There's nothing he can't take apart, but many things he can't reassemble. You'll find him writing and speaking his loud opinion on Android Central and occasionally on Twitter.

13 Comments
  • If I can control my Hue lights from my watch when Home cannot hear me, I'm happy
  • This disparity of what an Assistant can do across devices is irritating. I can have the regular old Ok Google on my phone set a reminder for tomorrow at 7 AM. When I asked my Google Home to set a reminder, it apologized that it couldn't set reminders yet. Really? Basic simple functionality for a digital assistant. When I asked Alexa to do it, she added it to a list of "to-do" items, but never notified me with an alarm at 7 AM. So, they both failed, just in different ways.
  • i havnt invested in any of this stuff for reasons like exactly what you just stated. Its still new. You jumped on the bandwagon early so you gotta take the lumps. Sorry brah. But i stopped carring about the smartwatches because i jumped on that early on too. The experience was lacking and led to me not caring anymore. i am interested now that 2.0 is around tho. Whats the best according the AC community now?
  • LOL. I ask my Echo dot to wake me up at 5 AM tomorrow morning, it says ...."ok". Then at 5 AM the alarm goes off.
  • An alarm is not a reminder. Google home has no problem with alarms and timers. IMO turning the mic off is not a solution. That's just more aggravating. When I want to talk to my pixel I just hold the home button then speak. It's not hard.
  • You simply say "Hey Google" for the home only.
  • Correct. But that's not the issue. The issue is trying to use your device with "OK Google" while in listening range of the home
  • Some very beta stuff is in testing that fixes a lot of this. As soon as it moves to the public betas of a couple Google apps (it's not all wrapped up into just the Google app) I'll make sure I talk about it a little bit.
  • First thing in the need for the devices to be able to talk to one another, then if you ask one of the devices it can then send your command to the proper Google device...
  • Wait, the guy at Best Buy told me I could cast traffic to my television. Are you telling me this isn't true?
  • The main problem is that neither is available to me in Canada yet.
  • If my Google Home is nearby, I will whisper to my LG Sport. But sometimes I wonder if G.Home is trying to eavesdrop and is maybe getting jealous of all the attention LG Sport is getting. If someday I am mysteriously murdered, you guys know who did it. AVENGE ME!
  • I am not sure why this is a surprise, this was always the case with any device that responded to "OK Google". You could have ten phones and ten tablets on a coffee table and all of them could respond. Rather annoying for a tech geek