Google will change a few Nest thermostats after ‘w5’ wi-fi issue breaks remote control

Google’s Nest thermostats make it easy to comfortably connected and easy to control the temperature of your home remotely, but the twist is that all such relies on will work on a wireless connection. Over the last few months, some Nest owners have encountered a “w5” error with wi-fi which completely disconnected all the wireless remote connections.

JOIN NNS ON TELEGRAM

So guys let just talk about the few error work into such devices which may completely get overcome by the experts. But before that let’s just talk about the error, which has been popping up
since November ongoing forum threads, won’t pull the plug on actual control over your thermostat, but now the smartphones have take responsibility to control it from a smartphone or smart speaker. While it’s nice to know this issue won’t entirely wreck your A/C, it does essentially break the highest the most selling point of the product prospectively.

But guys there is not only the way by which temperature could control but just not by a single idea here are some for some users, that this problem can be fixed through a standard reset or other troubleshooting measures. On the other hand for the others, the known hardware with the internal Wi-Fi chip requires a full hardware replacement — which Google will provide for free after a customer contacts support. Google explained to The Verge:

A very small number of Nest thermostat users are experiencing a known issue with the Wi-Fi chip that causes remote connectivity issues. This does not affect the thermostat’s ability to control the customer’s heating and cooling system in the home but does impact the user’s ability to manage the thermostat remotely. If a user sees this error and it can’t be resolved through troubleshooting, they are prompted to contact customer support for assistance and will be issued a replacement device.

So this problem is not new good guys according to the sources this may record that this problem is too old and wasn’t come to control for so long and there are so many reports of this issue have come up most in recent weeks than previously, suggesting that a recent Nest update could have caused the “w5” error for more users. Android Police noted some cases where the issue appeared “immediately” after an update.

So guys this tip I’ll also recommend to you that If you’re having this issue, get in touch will Google support and also leave a comment below letting us know whether a reset fixes the issue, or if you end up getting a replacement Easley and get updated always.

Source

 

Leave a Comment