I think he means on chrome > 3 dot menu > more tools > dev tools > network tab
this lets you see debug/source/etc info on the web pages
Yes thatās what I mean. But the latest release fixed your fan control issue so there is no need to capture the payload.
Sorry, I canāt believe I missed that. 
I hoped that the update will show my thermostats, but it didnāt. Sad face 
Can I help you somehow? Do some diagnostics, maybe at home.nest.com?
Hello ā Google announced that Gen 1/2 thermostats can no longer be remotely controlled at the end of this month. Will this legacy integration continue to work afterwards? I presume not, as it still relies on Googleās cloud services, correct?
Correct. I donāt see how this could continue working
Iām trying to get this working using Legacy Nest Account Configuration. It accepts my access token but during the initializing phase I only get this error:
Failed Setup, will retry: Failed to initialize Nest: invalid literal for int() with base 10: ānoneā
Can you enable debug logs and attach them in a new GitHub issue?
I am struggling to get the integration working, receive the following error:
Failed setup, will retry: Failed to initialize Nest: āserial_numberā
I filed an issue on Github with the log.
This is exactly what I wanted as it will solve one of the biggest problems in my home, the nest thermostat. I do not want to give even more money to google than I have to. I added this integration to my HA and it was able to find my door lock. However, it did not add my gen 3 nest thermostat. I already see that this issue is already on GitHub. Great work so far!
Context:
Google semi-bricking Gen1 and Gen2 Nest thermostats and not providing a way of opening them up to local control. FULU bounty won (although weirdly the Fulu page not updated?).
Github for that here
There is also a Home Assistant addon!