This isn’t normal. You shouldn’t have to mess with this. Do you have anything else using the same Google API tokens? Like a second hub? I ask because thus happened with another user that had the GCal app loaded on two different hubs and had a similar issue. Google API tokens need to be setup for each integration/hub.
So I think I may have figured it out....
In my google settings, the Publis Status was in "Testin". I was not able to click "Production".
I had this section blank:
Once I put links in those three, I was able to click "Production".
Is this what I was doing wrong?
Having said that, if so, what should I actually be putting in those 3 blanks???
The GitHub instructions are a little outdated. Google Auth Platform has changed it's layout.
Apologize for the confusion. Google has changed that interface many times since I published this solution and I just haven't had the motivation to keep them updated especially since this is a set and forget solution - I am rarely in the Console.
My "Publishing status" is In Production so that could be it. Back when I set mine up those URLs weren't necessary and mine are still blank. Hopefully the change in status resolves this issue.
I'll report back in a week or so.....from what I read, when it isn't in production mode and in Test mode, it only lasts 7 days....so this would make sense.
That is unrelated to GCal Search. This project doesn’t use the file API so this must be related to something else you are using. I personally sit receive this email.
Hmm. I wonder if I accidently enabled too much or I have a legacy project I never cleaned up? Does this project use the Google Calendar API? I see all these other API's enabled too. When I drill into them, I see OAuth credentials for Hubitat Calendar.
I have two GCal projects, but the other one, which I didn't think I was using, only has the Telemetry API enabled. However I see this other project has Service account for "g3plugin" enabled.
Maybe I got my projects crossed?
Definitely because the solution really only needs access to 3 APIs assuming you use all three capabilities: Calendar, Tasks, and Gmail. Here is my list though Telemetry must have been added automatically because I didn't enable it. I only use Calendar and occasionally Gmail and Tasks are enabled because I support the use of it even though I don't personally use it.
Thanks for the help @ritchierich. I removed all those other API's and shutdown that unknown project that was labeled gcal3. Let's see what breaks
@rakeshg asked whether GCal Search utilizes the HE Cloud APIs and whether it would require the new Cloud Extend subscription here so I wanted to provide the answer in this thread in case others are wondering...
GCal Search uses direct API calls from your local hub to the Google APIs. The only time that the HE Cloud APIs are utilized is when you first setup the App or reset the API credentials and go through the Google Login process again where an OAuth call back is utilized. Otherwise token refreshes and searches are all direct from your hub to Google.
Starting with the 2.5.2.129 release you can go to Logs \ Cloud Calls tab to see which apps are utilizing the HE Cloud and you shouldn't see GCal Search listed unless you go through the Google API Authorization process.