pyopenems
$ pip install pyopenems
cli
$ python -m openems --server-url='ws://localhost:8081' --username='admin' --password='password' get-edge-list
edge0
edge1
edge3
edge4
edge5
edge6
$ python -m openems --server-url='ws://localhost:8081' --username='admin' --password='password' get-edge-config edge0
{
"components": {
"_appManager": {
"alias": "Core.AppManager",
"factoryId": "Core.AppManager",
"properties": {
"apps": "[]",
"keyForFreeApps": "0000-0000-0000-0000"
},
"channels": {
fetching meter value
$ python -m openems ... get-meter-list edge0
meter0
meter1
$ python -m openems ... get-channel-list edge0 meter0 | head
meter0/ActiveConsumptionEnergy
meter0/ActiveConsumptionEnergyL1
meter0/ActiveConsumptionEnergyL2
meter0/ActiveConsumptionEnergyL3
meter0/ActivePower
meter0/ActivePowerL1
meter0/ActivePowerL2
meter0/ActivePowerL3
meter0/ActiveProductionEnergy
meter0/ActiveProductionEnergyDaily
$ python -m openems ... get-channel-data edge0 meter0/ActiveConsumptionEnergy 2024-01-01 2024-01-01
,meter0/ActiveConsumptionEnergy
2023-12-31T15:00:00Z,5831900.0
2023-12-31T15:05:00Z,5831900.0
2023-12-31T15:10:00Z,5831900.0
2023-12-31T15:15:00Z,5832000.0
2023-12-31T15:20:00Z,5832000.0
(snip)
2024-01-01T14:35:00Z,5837900.0
2024-01-01T14:40:00Z,5838000.0
2024-01-01T14:45:00Z,5838000.0
2024-01-01T14:50:00Z,5838000.0
2024-01-01T14:55:00Z,5838100.0
fetching pvinverter value
$ python -m openems ... get-pvinverter-list edge0
pvInverter1
$ python -m openems ... get-channel-list edge0 pvInverter1 | head
pvInverter1/ActiveConsumptionEnergy
pvInverter1/ActiveConsumptionEnergyL1
pvInverter1/ActiveConsumptionEnergyL2
pvInverter1/ActiveConsumptionEnergyL3
pvInverter1/ActivePower
pvInverter1/ActivePowerL1
pvInverter1/ActivePowerL2
pvInverter1/ActivePowerL3
pvInverter1/ActivePowerLimit
pvInverter1/ActiveProductionEnergy
$ python -m openems ... get-channel-data edge0 pvInverter0/ActiveProductionEnergy 2024-01-01 2024-01-01
2023-12-31 15:00:00+00:00,5700.0
2023-12-31 15:05:00+00:00,5700.0
2023-12-31 15:10:00+00:00,5700.0
2023-12-31 15:15:00+00:00,5700.0
2023-12-31 15:20:00+00:00,5700.0
2023-12-31 15:25:00+00:00,5700.0
2023-12-31 15:30:00+00:00,5700.0
2023-12-31 15:35:00+00:00,5700.0
2023-12-31 15:40:00+00:00,5700.0
setting controller value
$ python -m openems update-component-config edge0 ctrlPeakShaving0 peakShavingPower 300
Metadata
Release files for pyopenems 1.8.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 | Actions |
|---|---|---|---|---|
| pyopenems-1.8.0.tar.gz | 12.4 kB | With provenance | Details for pyopenems-1.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyopenems-1.8.0-py3-none-any.whl | Python 3 | none | any | Details for pyopenems-1.8.0-py3-none-any.whl |
Total release size: 19.2 kB
Release files / pyopenems-1.8.0.tar.gz
| Download URL | pyopenems-1.8.0.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e50148b95a2707e05fc80ca855b5c27385f45293bd20cf48c84467fee8ea5fa8
|
|
BLAKE2b-256 checksum How to use checksums |
a5da733f726cd332bc3d6393524e4eb708fd38c1c525f9308f0ecb3019d9c7e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 15, 2025.
Transparency logRelease files / pyopenems-1.8.0-py3-none-any.whl
| Download URL | pyopenems-1.8.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
489d1e505dbd6984ab10c8d8636b72fc1525c8e930ef2d0b9d2618b174d036af
|
|
BLAKE2b-256 checksum How to use checksums |
d656c87f44a999a9c23d8d331ccaa1916d89897419f82c511b263aab3d88a463
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 15, 2025.
Transparency logSecurity for pyopenems 1.8.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 pyopenems-1.8.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 Aug 15, 2025.
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.