Chromecast and Google Homes reportedly overloading home Wi-Fi [Updated]


Broaden / The Google Home Mini, the original Google Home, and the Google Well-versed in Max.

Update: Google has posted a support page for this publish promising a fix tomorrow (1/18). The page says the issue is limited to “People with an Android phone and a Chromecast built-in gambit (such as a Chromecast or Google Home device) on the same Wi-Fi network” and that a fix intention be rolling out via Play Services.

The original story is below.

Users on the Google hands forums and Reddit are reporting that Google Home and Google Chromecast colophons are causing issues with their Wi-Fi networks. Users say by one way up these Google hardware products leads to an unstable Wi-Fi network or a network that make headways down entirely.

The instability was originally thought to affect the TP-Link Archer router series with a singular Google device, the Google Home Max. The issue has been slowly slink out to other devices, though, with the Google Home, Google Home Mini, and Chromecast ostensibly having similar issues. TP-Link was singled out because it’s a popular router type.

TP-Link issued a beta patch for the Archer C1200, but the company light oned to the conclusion that the issue isn’t with its routers. In a support article, TP-Link inscribes:

Following initial research and investigation, our engineering team is confident that they’ve strong-willed one of the key origins of the issue. From what we have gathered so far, the issue plains to be related to some of the recent versions of Android OS and Google Apps.

This affair stems from these devices’ “Cast” feature, which sends MDNS multicast origination packets in order to discover and keep a live connection with Google offshoots such as Google Home. These packets [are] normally sent in a 20-second meantime. However, we have discovered that the devices will sometimes disseminate a large amount of these packets at a very high speed in a cut in on amount of time. This occurs when the device is awakened from its “slumber” state, and could exceed more than 100,000 packets. The longer your crest is in “sleep,” the larger this packet burst will be. This take exception may eventually cause some of router’s primary features to shut down—counting wireless connectivity.

For now, disconnecting your Google products from the network or disabling send functionality seems to fix the issue. A Google spokesperson told Engadget, “We’re sensitive that a small number of users are having issues, and our team is farm quickly to share a solution.”

Leave a Reply

Your email address will not be published. Required fields are marked *