aiogeodrops
Async Python client for GeoDrops soil-probe readings.
GeoDrops publishes every probe's readings to a public Google BigQuery table.
This library queries it over BigQuery's REST API with a Google service
account. It is built on aiohttp and PyJWT only (no Google Cloud SDK, no
gRPC), takes your aiohttp.ClientSession, and is fully typed.
It is the library behind the GeoDrops Home Assistant integration.
Install
pip install aiogeodrops
Prerequisites
A Google Cloud project of your own (queries run and are billed there, well within BigQuery's free tier for a handful of probes), with the BigQuery API enabled, and a service account that has BigQuery Job User on that project. Download a JSON key for the service account.
Usage
import asyncio
from pathlib import Path
import aiohttp
from aiogeodrops import GeoDropsClient
async def main() -> None:
key = Path("service-account.json").read_text()
async with aiohttp.ClientSession() as session:
client = GeoDropsClient(session, "my-gcp-project", key)
await client.validate_access()
# Find a probe's device id from the serial shown in the GeoDrops app.
reading = await client.lookup_serial("AAA111", lookback_hours=12)
if reading is None:
print("No reading in the last 12 hours")
return
latest = await client.fetch_latest([reading.device_id], lookback_hours=12)
probe = latest[reading.device_id]
print(probe.moisture_pct, probe.temp_surface, probe.read_at)
asyncio.run(main())
fetch_latest makes one query for all the device ids you pass. Each query
gives up after 60 seconds (query_timeout= to change).
Errors
All errors derive from GeoDropsError:
| Exception | Meaning | What to do |
|---|---|---|
GeoDropsCredentialsError |
The key isn't a usable service-account key | Fix the key; raised by the constructor |
GeoDropsAuthError |
Google rejected the key (deleted, revoked, account disabled) | Create a new key |
GeoDropsAccessDeniedError |
403: missing BigQuery Job User role, or BigQuery API not enabled | Fix it in Google Cloud; then retry |
GeoDropsQueryError |
BigQuery rejected the query (parent of GeoDropsAccessDeniedError) |
Check the project id |
GeoDropsConnectionError |
Network error, timeout, Google outage, rate or quota limit | Retry later |
Development
pip install -e ".[dev]"
ruff check . && ruff format --check .
mypy
pytest --cov=aiogeodrops
Releases are published to PyPI by GitHub Actions when a GitHub release is published.
Metadata
Release files for aiogeodrops 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aiogeodrops-0.1.0.tar.gz | 17.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiogeodrops-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.9 kB
Release files / aiogeodrops-0.1.0.tar.gz
| Download URL | aiogeodrops-0.1.0.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2eab43059c36883ab202f7b5113d4d79f3825e97ef6545a4cf20f7f0f63a59e6
|
|
BLAKE2b-256 checksum How to use checksums |
95b767e4b68aefcb5b5875161a6b77844585687c0a5be0a17bd2b3bb250cb91f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logRelease files / aiogeodrops-0.1.0-py3-none-any.whl
| Download URL | aiogeodrops-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e86a558fb7482368fe0f8e1d80f22b0a3b5cd00e3b2fc369d89455c120616d8
|
|
BLAKE2b-256 checksum How to use checksums |
eaa7c671f770483ddb5a3b38c1686d776411c049e5a4831e0f1763f9bf249c68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logSecurity for aiogeodrops 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aiogeodrops-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.