Quick service for uploading data from your Goodwe inverter to PVOutput.org.
It grabs generation (W), load (W), inverter temperature and voltage (V). If you're a subscriber to PVOutput you can store state of charge of your battery too. The data is pulled via my pygoodwe library in the getDataPvOutput function.
Configuration
File in one of these places:
- ~/.goodwe2pvoutput.conf (Home dir)
- ./goodwe2pvoutput.conf (Current dir)
- /etc/goodwe2pvoutput.conf
Template: see goodwe2pvoutput.conf.example
Goodwe config
Determine the Station ID from the GOODWE site as follows. Open the Sems Portal. The Plant Status will reveal the Station ID in the URL. Example:
https://www.semsportal.com/powerstation/powerstatussnmin/11112222-aaaa-bbbb-cccc-ddddeeeeeffff
Then the Station ID is 11112222-aaaa-bbbb-cccc-ddddeeeeeffff.
PVOutput config
Get your API key and system ID from the account page on PVOutput
Running it
goodwe2pvoutput should do it for testing.
If you want to make it a systemd service:
- Download goodwe2pvoutput.service to
/etc/systemd/system/ - Make sure the config file is at
/etc/goodwe2pvoutput.conf - Run
sudo systemctl daemon-reloadto load the file sudo systemctl status goodwe2pvoutputto check it looks sanesudo systemctl enable goodwe2pvoutputto enable it on bootsudo systemctl start goodwe2pvoutputto start it
Dependencies
Contributing
You're probably better off contributing to other packages like the dependencies above, but if you feel the need - lodge an issue or PR on Github
Changelog
- 0.0.1 Initial Version
- 0.0.2 2019-10-12 Updated to include SoC upload
- 0.0.3 2019-10-12 Turns out the "defaults" aren't as default as I thought in ConfigParser. Fixed.
- 0.0.4 2019-10-12 Way more config error checking
- 0.0.5 2021-01-08 Fixed the example config "systemid" field was mistyped.
- 0.0.6 2021-07-15 Didn't change the module much, added lambda function.
Metadata
Release files for goodwe2pvoutput 0.0.6
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 | |
|---|---|---|---|---|
| goodwe2pvoutput-0.0.6.tar.gz | 4.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| goodwe2pvoutput-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 kB
Release files / goodwe2pvoutput-0.0.6.tar.gz
| Download URL | goodwe2pvoutput-0.0.6.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae1b0674278edd5c049ca15b5f0e030c518e7008d6cfdcdf44bc09cf25668318
|
|
BLAKE2b-256 checksum How to use checksums |
fcded1fb9fad70cf40cf1a79d3a850f7708a4a074f7068b217cc82c3b1c6983a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.4
|
Release files / goodwe2pvoutput-0.0.6-py3-none-any.whl
| Download URL | goodwe2pvoutput-0.0.6-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23ad127e95727cd880e91e80b77c74fbe8790de639fd4aa23217f88a9a333ac5
|
|
BLAKE2b-256 checksum How to use checksums |
b4685f7fee20d4a94e9d878c8ff310ea4986e4fd45b9fb5ff7b2e2a2aff5e7d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.4
|
Security for goodwe2pvoutput 0.0.6
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.