govee-api-laggat Package
Python implementation of the govee API 1.0 to control the cheap and colorful LED strips.
Why / Motivation
I want to use this package in an Home Assistant Component to control my new light strips.
Remember: this is NOT the integration, but the library the integration uses.
The custom integration project lives here: github.com/LaggAt/hacs-govee
Usage in your project
Look at the /example folder in this repo.
Govee trademark
Govee and the Govee logo are trademarks or registered trademarks of Shenzhen Intellirock Company Limited, and used by Govee with permission. Neither your use of the Govee Logo grant you any right, title, or interest in, or any license to reproduce or otherwise use, the Govee logo. You shall not at any time, nor shall you assist others to, challenge Govee's right, title, or interest in, or the validity of, the Govee Marks.
Links
- PyPi project and python package: pypi.org/project/govee-api-laggat
- Home Assistant custom integration Git: github.com/LaggAt/hacs-govee
- Govee API documentation: Govee API Reference
API Key
To get an api key you need to install the 'Govee Home' app on your mobile and browse the user tab - About - Request API key. Usually you get your key within seconds by mail.
Issues / Improvements
There are two projects, this one is the API implementation for python. The second project is the custom integration into Home Assistant which currently lives github.com/LaggAt/hacs-govee
Feel free to fork and start a pull request in your feature/bug branch. If you cannot fix or extend it yourself, you may want to add an issue in the correct project, but it may take a bit longer.
development
- pip install setuptools wheel tox
- Fork and clone the repository
- Make a 'feature/NAME' or 'bug/NAME' branch
- Run tests: tox
- commit and start a pull request
1 maintainer
Metadata
1 maintainer
Release files for govee-api-laggat 0.2.2
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 | |
|---|---|---|---|---|
| govee_api_laggat-0.2.2.tar.gz | 20.9 kB | Without provenance | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| govee_api_laggat-0.2.2-py3.8.egg | Legacy Egg format | - | - | Details |
| govee_api_laggat-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 95.8 kB
Release files / govee_api_laggat-0.2.2.tar.gz
| Download URL | govee_api_laggat-0.2.2.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea7673737cd8f545c614aeebd5278e3331332306a45b96a76eeee52705aac08e
|
|
BLAKE2b-256 checksum How to use checksums |
eac0aca7f6519e7e14bea4db0d1f59c62bd4cd27787e3fa5fa18dc494e965181
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.12
|
Release files / govee_api_laggat-0.2.2-py3.8.egg
| Download URL | govee_api_laggat-0.2.2-py3.8.egg |
|---|---|
| Size | 51.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
2008abbc695748c5b9d12091aea0f9a7f088c77b8a9fb6e82b50941f7afcbda6
|
|
BLAKE2b-256 checksum How to use checksums |
6b25c1a2afa20d508c5ba70eda2e47fd695d5f56bb98ac49ad22e9ce25cb112c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.12
|
Release files / govee_api_laggat-0.2.2-py3-none-any.whl
| Download URL | govee_api_laggat-0.2.2-py3-none-any.whl |
|---|---|
| Size | 23.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb88f1438065768f959ba3d09e654beb5e3fb1c473b2f44917b6ff333be2d7d0
|
|
BLAKE2b-256 checksum How to use checksums |
f16cb36c9d283086cf7f9b1a20f08830fa7230035d64213c4bceab40e43fbd19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.12
|
Security for govee-api-laggat 0.2.2
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.
