<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TD030 error on device add in Nest Thermostats</title>
    <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287642#M58798</link>
    <description>&lt;P&gt;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/255752"&gt;@jeff16&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wonder about several things after seeing hundreds of posts on this:&lt;/P&gt;&lt;P&gt;1) Why does the "&lt;EM&gt;assisting device&lt;/EM&gt;" failure occur only with some customers? It hasn't happened to us and we've added several new Google Nest devices in the last year.&lt;/P&gt;&lt;P&gt;2) Why does the "&lt;EM&gt;assisting device&lt;/EM&gt;" process even fail? Is it a distance issue because it is using Bluetooth? Or since the failure often occurs when the "&lt;EM&gt;assisting device&lt;/EM&gt;" is a thermostat, is it because the thermostat is too busy, or just a lousy "&lt;EM&gt;assisting device&lt;/EM&gt;"? If it fails with another battery camera, is it because the battery camera is normally "&lt;EM&gt;Idle&lt;/EM&gt;"?&lt;/P&gt;&lt;P&gt;3) If Google Nest's reason for using the "&lt;EM&gt;assisting device&lt;/EM&gt;" process in the first place is to ensure that every device in a Google Nest "&lt;EM&gt;home/structure&lt;/EM&gt;" is on the same Wi-Fi network (thereby preventing families from sharing a Google Nest "home/structure" at several houses, as some customers have theorized), perhaps Google Nest does NOT ever want to let people enter their own Wi-Fi credentials if there is already an existing Google Nest device.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Nov 2022 20:54:01 GMT</pubDate>
    <dc:creator>MplsCustomer</dc:creator>
    <dc:date>2022-11-17T20:54:01Z</dc:date>
    <item>
      <title>TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283634#M57919</link>
      <description>&lt;P&gt;I am trying to add two nest thermostats to my nest app.&amp;nbsp; I can add one, but then the second one fails to connect with a TD030 error.&amp;nbsp; If I then remove the working device, I can add the second device perfectly, but then it can't connect the original working device with a TD030 error.&amp;nbsp; It's failing when it's trying to connect to the assistive device, but adds perfectly if this awesome "assistive" device is not on the account.&amp;nbsp; Both are on the same network and can see the internet fine.&lt;/P&gt;&lt;P&gt;How do I tell it to just connect both with the internet and not use this extremely helpful "assistive" device?&lt;/P&gt;&lt;P&gt;How do I charge the nest engineer that wrote this setup code for my time?&lt;/P&gt;</description>
      <pubDate>Sun, 13 Nov 2022 19:31:14 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283634#M57919</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-13T19:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283664#M57929</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Google Nest&lt;/STRONG&gt;: it is long past time for you to fix this "&lt;EM&gt;assisting device&lt;/EM&gt;" problem that has been plaguing Google Nest users for more than a year. Since it seems it is frequently a thermostat that fails at being an "&lt;EM&gt;assisting device&lt;/EM&gt;", customers can get around the error by temporarily removing the thermostat while installing the other Google Nest device, but when the customer has two thermostats, they're stuck.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Nov 2022 20:03:37 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283664#M57929</guid>
      <dc:creator>MplsCustomer</dc:creator>
      <dc:date>2022-11-13T20:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283680#M57930</link>
      <description>&lt;P&gt;I found reddit posts 3 years old with this same problem.&amp;nbsp; I feel like I just have to dump all this crap and move on, but it's sunk cost.&amp;nbsp; In general, the quality of the Nest Minis, the thermostats and the Google Home app is just shameful - like embarrassingly bad.&amp;nbsp; I guess we just have to wait a year or two before they cancel it all anyway.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Nov 2022 20:18:22 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/283680#M57930</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-13T20:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287569#M58779</link>
      <description>&lt;P&gt;Hey there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry to hear about the trouble.&amp;nbsp;I wanted to follow up and see if I could be of any help. I found an &lt;A href="https://goo.gle/3Oedw0A" target="_blank"&gt;article&lt;/A&gt; with some troubleshooting steps for the error code you are getting. Please let me know if you&amp;nbsp;are still having any trouble from here, as I would be happy to take a closer look and assist you further.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Jake&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 19:33:20 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287569#M58779</guid>
      <dc:creator>Jake</dc:creator>
      <dc:date>2022-11-17T19:33:20Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287627#M58793</link>
      <description>&lt;P&gt;No, that didn't fix the problem.&amp;nbsp; To fix the problem, you have clear out the WWN connection settings after you setup one of them.&amp;nbsp; This has been happening for 3 stupid years, and Google doesn't clear the WWN connection settings once the "assistive device" fails to be found.&amp;nbsp; It's embarrassing and shameful - this is a 5 line fix - it screws up everyone with more than one device and Google just doesn't care.&amp;nbsp; There are hundreds of people over the last 3 years complaining about this on reddit, and Google doesn't just fix the problem, and they don't even document the correct way to fix their own problem.&amp;nbsp; It's SHAMEFUL.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 20:33:47 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287627#M58793</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-17T20:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287633#M58796</link>
      <description>&lt;P&gt;What should happen is that when you setup a second Nest, if the connection to the "assistive device" fails, you just have the user do the full normal setup, as if it was the only Nest.&lt;/P&gt;&lt;P&gt;Here is how it works now:&lt;/P&gt;&lt;P&gt;If setting up new Nest, is there an existing other device on the account (an "assistive device)?&amp;nbsp; If so, contact that assistive device and make the setup faster.&amp;nbsp; If not, show a TD030 error and WASTE THE USER'S TIME.&lt;/P&gt;&lt;P&gt;What it should do instead:&lt;/P&gt;&lt;P&gt;If contacting the assistive device fails, just do a normal full install.&amp;nbsp; No wasted time - I mean you have to type the wifi password type - WHO CARES?&lt;/P&gt;&lt;P&gt;The fact that there is three years of people with this problem, IS ABSURD.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 20:39:40 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287633#M58796</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-17T20:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287642#M58798</link>
      <description>&lt;P&gt;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/255752"&gt;@jeff16&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wonder about several things after seeing hundreds of posts on this:&lt;/P&gt;&lt;P&gt;1) Why does the "&lt;EM&gt;assisting device&lt;/EM&gt;" failure occur only with some customers? It hasn't happened to us and we've added several new Google Nest devices in the last year.&lt;/P&gt;&lt;P&gt;2) Why does the "&lt;EM&gt;assisting device&lt;/EM&gt;" process even fail? Is it a distance issue because it is using Bluetooth? Or since the failure often occurs when the "&lt;EM&gt;assisting device&lt;/EM&gt;" is a thermostat, is it because the thermostat is too busy, or just a lousy "&lt;EM&gt;assisting device&lt;/EM&gt;"? If it fails with another battery camera, is it because the battery camera is normally "&lt;EM&gt;Idle&lt;/EM&gt;"?&lt;/P&gt;&lt;P&gt;3) If Google Nest's reason for using the "&lt;EM&gt;assisting device&lt;/EM&gt;" process in the first place is to ensure that every device in a Google Nest "&lt;EM&gt;home/structure&lt;/EM&gt;" is on the same Wi-Fi network (thereby preventing families from sharing a Google Nest "home/structure" at several houses, as some customers have theorized), perhaps Google Nest does NOT ever want to let people enter their own Wi-Fi credentials if there is already an existing Google Nest device.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 20:54:01 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287642#M58798</guid>
      <dc:creator>MplsCustomer</dc:creator>
      <dc:date>2022-11-17T20:54:01Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287651#M58800</link>
      <description>&lt;P&gt;1) it depends on whether the assistive device has bad WWN settings stored.&amp;nbsp; What are the WWN settings?&amp;nbsp; Some dumb token based system for accessing another Nest device.&amp;nbsp; Why do they get bad info? Who knows?&amp;nbsp; The question is why doesn't the new device just ignore the assistive device if it can be found.&lt;/P&gt;&lt;P&gt;2) Because it probably has a stale token.&amp;nbsp; But the real reason is that all of this janky-ass nonsense seems to be made by interns at Google, and Google itself doesn't care because they don't do the support.&lt;/P&gt;&lt;P&gt;3) I think all the assistive device stuff does *AT ALL* is share the wifi password.&amp;nbsp; Who cares - if it fails, I can type it in twice.&lt;/P&gt;&lt;P&gt;Morons.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 20:57:28 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287651#M58800</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-17T20:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287658#M58803</link>
      <description>&lt;P&gt;And separately, getting these stupid dumb forum notices that "hey, you got a kudo" or "hey, this is your 5th reply" is so insulting on a forum that I'm ONLY ON BECAUSE THE DEVICE DOESN'T WORK!&lt;/P&gt;&lt;P&gt;They are essentially congratulating me for my problems NOT BEING SOLVED.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Nov 2022 21:00:11 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/287658#M58803</guid>
      <dc:creator>jeff16</dc:creator>
      <dc:date>2022-11-17T21:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/317683#M67123</link>
      <description>&lt;P&gt;Hey there,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sorry for the late reply. I wanted to check in and see if you are still in need of any help. Please let me know, as I would be happy to assist, and answer any questions you may have.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Jake&lt;/P&gt;</description>
      <pubDate>Thu, 22 Dec 2022 20:15:09 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/317683#M67123</guid>
      <dc:creator>Jake</dc:creator>
      <dc:date>2022-12-22T20:15:09Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/320411#M67884</link>
      <description>&lt;P&gt;Hi everybody,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://www.googlenestcommunity.com/t5/user/viewprofilepage/user-id/255752"&gt;@jeff16&lt;/a&gt; It's us again, I'm bumping up this thread to see if you're still in need of assistance. Let us know if you have more questions in mind.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for lending a hand, Jake and MplsCustomer.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Emerson&lt;/P&gt;</description>
      <pubDate>Mon, 26 Dec 2022 20:25:48 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/320411#M67884</guid>
      <dc:creator>EmersonB</dc:creator>
      <dc:date>2022-12-26T20:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: TD030 error on device add</title>
      <link>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/323045#M68591</link>
      <description>&lt;P&gt;Hey jeff16,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just one quick final check in here since activity has slowed down. We'll be locking the thread in the next 24 hours, but if you still need help, I would be happy to keep it open. If there's more we can do, just let me know.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;Emerson&lt;/P&gt;</description>
      <pubDate>Thu, 29 Dec 2022 16:07:52 GMT</pubDate>
      <guid>https://www.googlenestcommunity.com/t5/Nest-Thermostats/TD030-error-on-device-add/m-p/323045#M68591</guid>
      <dc:creator>EmersonB</dc:creator>
      <dc:date>2022-12-29T16:07:52Z</dc:date>
    </item>
  </channel>
</rss>

