in

‘Untrusted device’ errors on Chromecast? What to know – including potential workarounds

ZDNET

Is your Chromecast device having issues? You’re not alone.

Second-generation Chromecast and Chromecast Audio devices are facing a problem that prevents them from casting content. If you try to use an affected device, you’ll see one of two errors — either, “Untrusted device: [name] couldn’t be verified. This could be caused by outdated device firmware,” or “We couldn’t authenticate your Chromecast.”

Also: Your TV’s USB port is seriously underrated: 5 benefits you’re not taking advantage of

Both error messages link to separate Google support pages, but those pages don’t address this issue. The only other option is to close the dialogue box.

Older Chromecast devices affected

The issue seems limited to older Chromecast devices, as no third-generation or Chromecast Ultra users have reported the problem.

Frustration is mounting on Reddit, where users have reportedly tried a number of fixes, including restarting the device, reinstalling Google Home, removing the device from Google Home and adding it again, restoring the device to factory settings, clearing cache data, and changing networks, but nothing works.

Also: Is your live TV streaming service still worth it? I review the options for every budget

Some users have even wondered if Google has quietly ended support for the older Chromecasts, but that doesn’t seem to be the case, as the company says a fix is on the way.

A fix is in the works

This morning, a Google Nest representative on Reddit posted that the company was aware of the issue and said a fix is in the works. The rep warned not to factory reset your device (even though the linked support page recommended doing so). If you have, though, instructions are on the way to get your device running again soon. The company doesn’t seem to have acknowledged the issue anywhere except this Reddit post.

Also: How to clear the cache on your TV (and why you shouldn’t wait to do it)

One Reddit user did post a few potential workarounds, but they’re a little complex.

Google didn’t explain what went wrong. Most speculation on Reddit is that the issue lies in an expired certificate on the Google server. This means that it’s entirely up to Google to fix, and you don’t have to do anything except wait. If Google does end up posting instructions, we’ll update here.


Source: Robotics - zdnet.com

This portable speaker beats the Bose SoundLink Max in key ways – for $200 less

I changed these 6 TV settings to drastically speed up its performance (and why they work)