reposit-python-client
Python client library to communicate with a Reposit Controller.
Compatibility
- Python 2.7
- Python 3+ preferred
Installation
pip install reposit
Quickstart
from reposit.auth import RPConnection
from reposit import Controller, Account
user = RPConnection('username', 'password')
account = Account(user)
user_keys = account.get_user_keys()
controller = Controller(user, user_key=user_keys[0])
print(controller.battery_capacity)
Data
| Method | Params | Description | Unit |
|---|---|---|---|
battery_capacity |
- | Get the capacity of the battery | kWh |
battery_min_state_of_charge |
- | Get the minimum state of charge of the battery | Percentage (%) |
has_battery |
- | Bool of whether the user has a battery or not | True/False |
has_inverter |
- | Bool of whether the user has an inverter or not | True/False |
get_solar_generation |
|
Get a list of solar generation data based on start or end | kW |
latest_solar_generation |
- | Get a list of the latest generation data. Goes back the last 24 hours. | kW |
get_house_consumption |
|
Get a list of house consumption values based on start or end | kW |
latest_house_consumption |
- | Get a list of the latest house consumption. Goes back the last 24 hours. | kW |
get_battery_data |
|
Get a list of battery data based on start or end | kWh |
latest_battery_data |
- | Get a list of the latest battery data. Goes back the last 24 hours. | kWh |
get_remaining_charge |
|
Get a list of the battery's remaining charge values based on start or end. There should be at least a 5 minute gap between start and end timestamps (i.e. 300 seconds) Note: This can be used to calculate the state of charge with the formula: (remaining_charge / battery_capacity) * 100` |
kWh |
get_meter_data |
|
Get a list of meter data based on start or end. There should be at least a 5 minute gap between start and end timestamps (i.e. 300 seconds) | kW |
latest_meter_data |
- | Get a list of the latest meter data. Goes back the last 24 hours. | kW |
feed_in_tariff |
- | Get the feed-in-tariff | Dollars ($) |
Links
Metadata
Release files for reposit 0.4.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 |
|---|---|---|---|---|
| reposit-0.4.0.tar.gz | 7.4 kB | Without provenance | Details for reposit-0.4.0.tar.gz |
Release files / reposit-0.4.0.tar.gz
| Download URL | reposit-0.4.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e690c40cea9d0113fdb5013de0bd5fc9197ddca325c34848a689fb48ce1f46e6
|
|
BLAKE2b-256 checksum How to use checksums |
337ade33ff97973d80cfdadcca8f34a83591faf41e206c7eb21f1aab5300ac3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.13.0 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/2.7.10
|
Security for reposit 0.4.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.
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.