Frequenz Gridpool Library
Introduction
High-level interface to grid pools for the Frequenz platform.
TODO(cookiecutter): Improve the README file
Supported Platforms
The following platforms are officially supported (tested):
- Python: 3.11
- Operating System: Ubuntu Linux 20.04
- Architectures: amd64, arm64
CLI
This package ships the gridpool-cli command with three subcommands.
Setup
Set the Assets API credentials before running the CLI:
export ASSETS_API_URL="grpc://..."
export ASSETS_API_AUTH_KEY="..."
export ASSETS_API_SIGN_SECRET="..."
Print component formulas
gridpool-cli print-formulas <microgrid_id>
Optional prefix formatting:
gridpool-cli print-formulas <microgrid_id> --prefix "{microgrid_id}.{component}"
The per-category formulas (pv, battery, chp, ev) read the component
first and use the meter as the fallback. Use
--prefer-meters-in-component-formulas for the opposite order, which is what
versions before component graph v0.5.0 produced:
gridpool-cli print-formulas <microgrid_id> --prefer-meters-in-component-formulas
Render component graph
Rendering requires optional dependencies. Install with:
pip install frequenz-gridpool[render-graph]
gridpool-cli render-graph <microgrid_id>
To save without opening a window:
gridpool-cli render-graph <microgrid_id> --no-show --output component_graph.png
Generate microgrid config
Derive metadata, formulas and component IDs for one or more microgrids from the Assets API and print them as dotted-key TOML to stdout:
gridpool-cli generate-config <microgrid_id> [<microgrid_id> ...]
Redirect stdout to save the result:
gridpool-cli generate-config <microgrid_id> > microgrid.toml
You can layer existing config files with the Assets API by precedence
(--default < Assets API < --override). Values from a --default file are
overridden by the API, while a --override file keeps its own values and the
API only fills the gaps:
gridpool-cli generate-config <microgrid_id> \
--default defaults.toml \
--override overrides.toml > microgrid.toml
If no microgrid IDs are given, they are taken from the supplied files:
gridpool-cli generate-config --override existing.toml > microgrid.toml
--prefer-meters-in-component-formulas works here too, so a regenerated
config can keep the meter-first order of the per-category formulas:
gridpool-cli generate-config <microgrid_id> \
--prefer-meters-in-component-formulas > microgrid.toml
Contributing
If you want to know how to build this project and contribute to it, please check out the Contributing Guide.
Metadata
Release files for frequenz-gridpool 0.6.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| frequenz_gridpool-0.6.4.tar.gz | 25.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| frequenz_gridpool-0.6.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.4 kB
Release files / frequenz_gridpool-0.6.4.tar.gz
| Download URL | frequenz_gridpool-0.6.4.tar.gz |
|---|---|
| Size | 25.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab3037e0723c442ac0c02c42f575f8da46bbc015965a9f9095b56c29b536e2db
|
|
BLAKE2b-256 checksum How to use checksums |
178f4c79614177cc45b4af5eb980ea2e63e6d2055052dc81eaf2f6d6c8e052b3
|
| 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 Aug 18, 2026.
Transparency logRelease files / frequenz_gridpool-0.6.4-py3-none-any.whl
| Download URL | frequenz_gridpool-0.6.4-py3-none-any.whl |
|---|---|
| Size | 25.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
635ffc39591d43bd7a5e36697b2db580e4012e8c175e4fe644abe19d15c7a0a7
|
|
BLAKE2b-256 checksum How to use checksums |
c9aa6c8a6d395dc66fb0d5ed0f1e196e34051f0ccbc06391a69ad6464357796c
|
| 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 Aug 18, 2026.
Transparency log