Google Home and Nest speakers are very useful because they assist users get answers, play music, control smart devices, and far more using voice commands. However, some users of Google Home and Nest speakers have reportedly done so having trouble with basic voice commands. This left many users unable to get their devices to answer easy requests.
The problem apparently began within the last week of December. For example, whenever you ask, “What’s the weather like?” or “What time is it?”, the devices are silent and don’t respond. The speakers may light up or display the processing sign, but provide no response. This issue appears to be the case affect users in several regions and on multiple devicesincluding Google Home, Nest Hub Max, Home Mini, Nest Audio and Nest Hub.
Android Authority was capable of reproduce the difficulty. It can be clear from post comment section that many users encounter with the identical problem, sharing their experiences.
This issue appears to primarily affect core commands
While there are no answers to basic queries, other smart home commands appear to work positive. For example, users can still ask their devices to regulate smart lights, run vacuum cleaners, and customize other smart devices. The problem appears to be limited to certain query types and not all commands.
Interestingly, the issue doesn’t appear to be widespread as many users haven’t reported any problems with their devices. However, for individuals who struggle with this problem, it may possibly be frustrating because their devices don’t reply to the voice queries they depend on for on a regular basis tasks.
Some users tried to resolve the difficulty with basic steps corresponding to disconnecting and resetting affected devices or restarting their routers. Unfortunately, these steps didn’t help them solve the issue.
The issue should now be resolved for many users
While the reason behind the difficulty continues to be unclear, Google is reportedly investigating the basis cause. A Google representative told Android Authorities: “The team is still investigating the root cause, but has resolved the issue, so all users should now proceed.”