Google Home and Nest speakers come in very handy as they help users get answers, play music, control smart devices, and a lot more with just voice commands. However, some users of Google Home and Nest speakers have reportedly been having trouble with basic voice commands. This left many users unable to get their devices to respond to simple requests.
The issue reportedly started in the last week of December. For example, when asking, “What’s the weather?” or “What is the time?”, the devices stay silent and unresponsive. The speakers might light up or show a processing sign but deliver no answer. This issue seems to affect users in several regions and on multiple devices, including Google Home, Nest Hub Max, Home Mini, Nest Audio, and Nest Hub.
Android Authority was able to replicate the issue. Also, it is clear from the post’s comments section that a lot of users are dealing with the same issue as they shared their experiences.
This issue appears to affect basic commands primarily
While basic queries aren’t being answered, other smart home commands appear to be working fine. For instance, users are still able to ask their devices to control smart lights, start their vacuum cleaners, and adjust other smart devices. The issue seems limited to specific types of questions rather than all commands.
Interestingly, the problem does not seem to be widespread, as many users have reported no issues with their devices. However, for those who are facing the issue, it can be frustrating as their devices fail to respond to voice queries they rely on for everyday tasks.
Some users have tried basic troubleshooting steps to fix the issue, such as unplugging and resetting the affected devices or restarting their routers. Unfortunately, these steps haven’t helped them to solve the issue.
The issue should now be fixed for most users
While the reason for the issue is still unclear, Google is reportedly investigating the root cause. A Google representative told Android Authority, “The team is still investigating the root cause but has resolved the issue, so all users should be up and running now.”
