Nest integration configuration flow permanently stuck

I added the Nest integration, whose setup flow prompted me to follow the Nest integration instructions. I completed all of the steps (configuring OAuth, creating a Nest Device Access project, paying the $5 fee, etc.) to the point where I have a Device Access Project ID.

Unfortunately I didn’t have time to complete this in one sitting, so I canceled the setup flow in HA and returned later once I had the Device Access Project ID. Now, however, I can no longer add the integration; it gives me an “Aborted” error with the message “The component is not configured. Please follow the documentation.”

It seems that partially completing the setup process has persisted some state that is preventing me from continuing or starting the setup flow from the beginning. Does anyone know where that state is, so I can remove it?

This should not happen so there is definitely a bug here. I would love to understand what went wrong and help resolve it.

However, to get you unstuck see Application Credentials - Home Assistant which is likely the hidden state.

In an attempt to understand and resolve: Do you have anything in configuration.yaml?

I’m embarrassed to admit that I didn’t follow the first rule of debugging: make sure everything is up-to-date.

Your prompt to check Application Credentials made me remember (since that UI control didn’t exist) that I never upgraded to 2022.6+, because I wanted to verify first that a breaking change wouldn’t affect me.

After upgrading to 2022.8.7 I checked Application Credentials: nothing there. I assume that’s expected, since the integration didn’t exist yet previously. I then tried to add the Nest integration again, and after a weirdly long delay (several minutes) it worked, and the setup flow completed smoothly from there.

Thanks very much, and sorry for the noise.