Skip to content

Configuration instructions should include moving the new project from testing to production. #38799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
l0cut15 opened this issue Apr 29, 2025 · 5 comments
Assignees

Comments

@l0cut15
Copy link

l0cut15 commented Apr 29, 2025

Feedback

Following the current instructions will result in keys expiring after 7 days this is a know problem which is documented. 100% of new users configuring this integration by following these instructions will run into this problem and need to search for a solution.

Add instructions to promote the project to production to the integration configurations instructions.

URL

https://www.home-assistant.io/integrations/nest/

Version

2025.4.4

Additional information

No response

@home-assistant
Copy link

Hey there @allenporter, mind taking a look at this feedback as it has been labeled with an integration (nest) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nest can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign nest Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@allenporter
Copy link
Contributor

Ok, something must have changed on Google side as the instructions explicitly address this, or a step was missed.

See the troubleshooting section which explains the misconfiguration and how to fix it.

@YumTaha
Copy link

YumTaha commented Apr 30, 2025

True, the documentation could be clearer about how to move from testing to production, especially since the 7-day expiration can catch new users off guard.

Even though there’s a troubleshooting section, it might be helpful to highlight this common pitfall earlier in the setup steps or add a small “Heads up” note with a direct link to the fix.

@allenporter
Copy link
Contributor

I'm not sure i follow whats missing... Today it says "Navigate back to the OAuth consent screen and click Publish App to set the Publishing status is In Production." and it has a screenshot showing in production. (My assumption is that people don't read that then not sure why they'd read anything else -- and its not their fault, the problem is there are just too many steps so its easy to miss, so not sure adding even more information will work)

@allenporter
Copy link
Contributor

Note, it also says it again after "Make sure the status is not Testing, or you will get logged out every 7 days."

I consider this 3 times on the page where it says it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants