Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Nest Integration - Configuration failed at the very end of the process (once again)
See original GitHub issueThe problem
This issue is the continuation of https://github.com/home-assistant/core/issues/73455 (which was closed since resolved…but not for that much unfortunately).
To resume my problem (which may have changed from the original one), the “add integration” process fails at the very end: when I click on link account, a new browser tab is opened pointing to http://localhost:8123/auth/external/callback?code=***** but remains blank (nothing is loaded nor is loading). If I go back to the home assistant tab a pop-up is present saying something like Loading the next step for Nest. After a while (a minute or so) the message changes to Error.
As suggested in the previous issue, I activated advanced logs with the following lines in my configuration.yaml:
logger:
default: info
logs:
homeassistant.helpers.config_entry_oauth2_flow: debug
However, the log is not so verbose:
Logger: aiohttp.server
Source: runner.py:120
First occurred: 18:01:26 (2 occurrences)
Last logged: 18:08:11
Error handling request
I also have this error in the registry but I am not sure it is related:
Logger: frontend.js.latest.202212131
Source: components/system_log/__init__.py:256
First occurred: 17:54:49 (2 occurrences)
Last logged: 18:02:06
:0:0 ResizeObserver loop completed with undelivered notifications.
As fat as I understand, there is no more information on the complete registry (concerning this problem).
In my previous post, @allenporter wrote:
The other related problems here i've seen are my home assistant url is not the same as the url you are using to talk to home assistant
But I did not understand what he meant. There may be part of the solution there…
I also tried to create new credential and then a new Device Access Project to see if I messed-up something, but nothing changed.
Thanks in advance for your help.
What version of Home Assistant Core has the issue?
core-2022.12.8
What was the last working version of Home Assistant Core?
Not known
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Google Nest
Link to integration documentation on our website
https://www.home-assistant.io/integrations/nest/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I do not understand why at the end of the process I have home-assistant.io as authorized domain in my OAuth Consent screen; I left it empty in the configuration process as per instructions. By the way, that may be normal…
Issue Analytics
- State:
- Created 9 months ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Container setup looks just fine. Thanks!
Hello, I am working directly on the same machine where HA is installed, so I do not know why some other Android devices are connecting to something in the meanwhile.
I activated the debug log for the additional components and started the process again. This is the timeline:
Link Account) just before 8.35. Since then I get theLoading the next step for Nestmessage and wait.Errorjust before 8.40.Here follows the associated log. I masked what I think may be sensible as you warned me (thanks for that), hoping I did not masked too much. I also deleted some lines concerning sensors and automations, which should not be related to this issue.
Please let me know in case I still left some confidential information on it. 😉