My apologies if I did not make this clear the first time. I will try again.In the actual Google Drive integration’s “Add Credentials” instructions, there is not a clear separation between Home Assistant users that are not already using a Google Cloud Console project, and those who already have established such a project to enable other Google API connections to Home Assistant. A novice user who has only used Google Cloud Console once before (Nest) still needs clear instructions just as a completely new user would need. (The instructions for the Home Assistant Nest integration are the most detailed step-by-step found - even for the portions that are the same.)The referenced video did not show using the instructions / following the links in those instructions, as shown here at 17:10 in the video:(In fact, this particular video creator has much more experience with Home Assistant than I ever will. He likely does not need instructions.)The instructions found from the integration itself (the image at 17:10) are generally written assuming the user does not already have other Google APIs enabled with Home Assistant. A novice who is just always following written instructions is not going to have the experience that tells them otherwise - especially directly within the Home Assistant user interface and following the links provided. From these Integration Instructions:1. Following the link to OAuth consent screen… there is nothing labeled “configure” or suggesting that action. The page resolves to https://console.cloud.google.com/auth/overview?project=<your_project_name>I could not do anything so I moved directly to step 2 (having already only created a link for Nest, as my first / only time using Google Cloud Console was only 9 months prior).2. The link did resolve to Credentials. Steps 3 to 5:  In my case, I reasoned that the user only needs to create new credentials if the existing credential does not already have the required Authorized redirect URL in place. Thus, I could re-apply my existing credentials already existing in that project for Home Assistant to Google Nest. (ChatGPT resolved an earlier question:  do I need to create a new project, and if no, can I rename the existing project:  no and kinda yes - limitations from Google Cloud).For the inputs, it is not clear for the novice if the “Name” field is the same as the Google Cloud’s App Name. I assumed it was.The rest of the inputs are clear.Suggestions for improvements to the structure of the Integration Instructions:A)  Existing Google Cloud Console project for Home Assistant (Google Sheets, YouTube, Nest, Google Mail):   1) Add the Google Drive API to that project. (Use link) 2) Enter below the existing Branding - App Name, OAuth Client ID, and OAuth Secret.B)  Completely new project (Prerequisite:  Google Account) 1) Create Google Cloud Project (use link)  2) Enable the API (use link) [hint: confirm project first] 3) Create the Credentials (use link) {continue with instructions originally numbered 3, 4, and 5 renumbered respectively as 4, 5, and 6} 7) Enter below the Branding - App Name, OAuth Client ID, and OAuth Secret.C) Follow the instructions on the following screen to complete the integration.These specific instructions are also not fully duplicated at https://www.home-assistant.io/integrations/google_drive/ and the prerequisite information found there could also be improved for clarity by simply explaining it is possible to use the same exact Home Assistant to Google Cloud Console project ***and***  credentials “ as the ones for Google Sheets, Nest, YouTube, and Google Mail. ”It helps in my experience that instructions on a support page are as nearly identical as those given in the user interface of the application. It also helps if the support page provides further guidance (screenshot) for each instruction - if not directly, at least point the user to other resources.Thank you for your consideration.On May 4, 2025, at 7:31 AM, tronikos ***@***.***> wrote: tronikos left a comment (home-assistant/home-assistant.io#38870) Does the included video help? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>