Google Drive
A connected Google Drive account, reporting your own storage usage as read-only sensors and doubling as a destination Backup & Restore can write scheduled backups to - the same browser-redirect OAuth2 consent screen Spotify uses, with your own Google Cloud app credentials.
Connecting
Devices & Services > Google Drive > "+ Add account" needs a Client ID and Client
Secret from an app you create yourself in the Google Cloud Console (with the Google Drive API
enabled and the shown Redirect URI added to it), then redirects your browser to Google's own
consent screen; approving it redirects back to Athena and saves the account automatically.
Athena requests only the narrow drive.file scope, so it can never see anything
already in your Drive - only files and folders it creates itself.
On first connect, Athena creates one Athena - <name> folder in your Drive
with a Backups subfolder inside it. Connecting the same Google account from more
than one Athena install (each with its own account name) gives each install its own separate
folder, so their backups never mix together.
Reached over a raw LAN IP (e.g. https://192.168.1.50:8088)? Google rejects a bare IP address as a redirect URI - and also rejects local-only endings like .local or .home, since it requires the redirect URI's own domain to end in a real top-level domain such as .com or .org. That domain never needs to be registered or reachable on the public internet - only your own hosts file needs to resolve it, and only for your own browser. Add a line like 192.168.1.50 local.athena.com to your hosts file (using this server's own IP and any name you like, as long as it ends in .com/.org/similar) - Athena is then reachable at https://local.athena.com:8088. Use that as the Redirect URI both in the connect form here and in the app in the Google Cloud Console. The hosts file is /etc/hosts on Linux and macOS (edit with sudo), or C:\Windows\System32\drivers\etc\hosts on Windows (edit Notepad as Administrator).
Entities
Three read-only sensors, checked every 15 minutes: available_space and
used_storage (your whole Drive's own quota, in GB - available_space
is left unreported on an unlimited-storage Workspace plan, which has no quota to subtract
from), and backup_storage (just the size of this account's own
Backups folder). Works with Dashboard
cards, History, and
Automations exactly like every other integration -
there's nothing to control, so it never appears as an Action node target, only as a state
source.
Using it as a backup destination
Once connected, the account shows up as a choice when adding a Google Drive destination under Backup & Restore's own scheduled-backup destinations - pick the account by name, no separate sign-in step. Deleting the account here also removes any backup destination still pointing at it.
Reconnecting
Google's own refresh token can stop working - most commonly because the connected app is still in
"Testing" publishing status in the Google Cloud Console, where Google expires refresh tokens
after about a week. When that happens the account's own page gets a "Reconnect" button (re-runs
the consent screen without losing history), a notification appears pointing straight at it, and a
needs_reconnect sensor is available if you want to build your own automation around
it (e.g. a push notification through ntfy).
Google Cast, Google Drive, Google Calendar, and Google Mail share one "Google" entry when picking a new integration to add from Devices & Services, since all four connect to the same account family - once any is configured, each still gets its own separate card.