Edgar Cervantes / Android Authority
Tl; DR
- Google Chromecast (2nd generation) and Chromecast Audio users are faced with problems due to an authentication error.
- Users have tried several troubleshooting stages, but nothing works, while the new Chromecast models remain unaffected.
- Google has not yet recognized the problem, leaving users not knowing whether it is a bug or an unexpected end -of -life decision.
Users of Google Chromecast and Chromecast Audio and Chromecast devices are faced with important problems today, their devices unable to launch content. The reports have flooded Reddit and other forums, frustrated users meeting an error message that prevents them from using their devices.
The problem first gained ground on the R / Googlehome Subreddit, where several users have shared their experiences not to be able to connect to their Chromecast (2nd generation). Other wire users have confirmed the same problem, with reports from different countries, which suggests that this is not an isolated problem.
Users have attempted current troubleshooting methods – restart, resetting factory, reinstalling the Google Home application, Cache / Data cleaning and even trying different networks – but none of these steps seems to solve the problem.
Some users also report another variant of the problem with an error message that can be read as follows: “Unreliable device: [name] I could not be checked. This could be caused by an obsolete firmware. The error message only provides an option to close the dialog box, which means that users are completely locked in the flow. (H / t: 9TO5GOOGLE))
The problem seems to affect only older chromecast models, in particular chromecast and 2nd generation audio chromecast. New models, such as Chromecast (3rd generation) and Chromecast Ultra, work without any problems.
Naturally, many users fear that Google has silently killed the support of these old Chromecast models, the bricks actually during the night. Given the story of Google sunset products without much warning, this concern is not entirely unjustified.
However, based on the nature of the error message, this seems more likely to be a bug rather than an intentional closure. If Google had planned to stop the support, we could expect an official announcement, or at the very least, a clearer message explaining that the devices were no longer supported. The wording of the “unreliable device” error suggests in place a kind of firmware check failure, which could potentially be resolved with a server on the correction.
We will update this story if and when Google gives more clarity. In the meantime, let us know if you are faced with the same problem and have found a bypass solution.
