It has been observed that many people who are using Google Home and Google Chromecast setup are facing a unique problem. They have set up Google Cast app on their devices, and after doing so, they found that their Wi-Fi networks stopped working. It is not known as to how an improper Google Cast app setup by Google Home speaker and Chromecast keys can lead to saturation of some Wi-Fi networks.
Many Google Home speakers or Chromecast com setup keys have recently been experiencing disruptions on their Wi-Fi network. “Sometimes, a bug in the cast app on Android based smartphones may incorrectly transfer a mammoth amount of network traffic, which in turn can slow down Wi-Fi networks or affect those in other ways.” This thing was admitted by Google after a number of complaints messages appeared on its forum”. People with an Android phone and a Chromecast-enabled device (such as a Chromecast device or Google Home) on the same Wi-Fi network might encounter this problem.”
Initially, a few users who were accessing the internet via router were facing this problem. The affected routers are those of TP-Link, NetGear, Linksys, ASUS and Synology manufacturers. The first three have developed downloadable patches to protect their equipment against crashes caused by Google devices. On its website, TP-Link took care to explain the origin of the problem to its customers.
In a house, Chromecast keys and Google Home Support speakers are connected to other devices, such as TVs or smartphones, with Google Cast. This allows the circulation of video or audio content online between the devices. For example, a smartphone can be connected to the Google Home speaker via Cast. This feature is responsible for disruptions on some Wi-Fi networks. Seeing this problem comes as a surprise for users because everything was normal in Google Home and Chromecast, but then, this problem arrived and caused disruption in the service of Google Home and Chromecast.
Devices connected to Google Home send signals (called mDNS packets, or Multicast Domain Name System) to it every 20 seconds on average. The problem is that they continue to send these packets even when they are idle, in order to maintain the connection to the smart speaker. These signals are then placed on the queue.
When the device is finally unlocked, all mDNS packages are sent at once. The flow can then go up to 100,000 packets issued in a very short time. The longer the device waits for a long time, the greater the number of signals sent simultaneously. This can lead to network overload; see the router shutdown in some cases. It is possible to temporarily resolve the problem by resetting the router to clear its memory or disable the Cast tool on the Android device.
Google has given explanations in which it said that only a small number of users were facing this problem. Google has also told that it is going to dispatch a patch as well, which users can download and fix this problem. The patch is available online, and users who are facing the problem with their Wi-Fi networks can easily get the patch from a reliable website.