teleco_daisy
small library to talk to the Teleco Automation Daisy.
this is alpha. currently supported are:
- pergola slats
- pergola rgb light
- pergola white light
if anybody stumbles over this and has different hardware, let me know and we try to integrate it together.
Development
HTTP Toolkit and adb
the best way you can get your devices integrated into this project is to:
- download https://httptoolkit.com/
- get yourself an android telephone with ADB (I think it needs to be rooted, not sure right now)
- use HTTP Toolkit and adb mode to selectively sniff the traffic from the Daisy app
if you've come this far, here comes the crucial part:
-
when clicking buttons in the daisy app, for let's say turning on your light bulb, you should see a corresponding
teleco/services/tmate20/feedthecommands/entry in HTTP Toolkit. -
take note of what you did (i.e. "I turned the light on") and the resulting
REQUEST BODY. it will contain something like:"commandsList": [ { "commandAction": "POWER", "commandId": 100, "commandIndex": 0, ....
-
you will also need to note the idDevicetype for the new component that you have. see next section.
a quick glance at your setup
To help get a quick overview of the items you have and the corresponding idDevicetypes, I added a little script to discover your local setup:
python discover.py <username> <password>
should produce some output that might already help a tad as well.
Metadata
Release files for teleco-daisy 0.2.1
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 | |
|---|---|---|---|---|
| teleco_daisy-0.2.1.tar.gz | 7.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| teleco_daisy-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.2 kB
Release files / teleco_daisy-0.2.1.tar.gz
| Download URL | teleco_daisy-0.2.1.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f348acb93f101e52a80f44b9ff956fa78574ae145c661b07f8ffac9542a0a9da
|
|
BLAKE2b-256 checksum How to use checksums |
91b21c4cef5f60e1245ab06048359b1f9125bdafc89836c521235924965cb085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"TUXEDO OS","version":null,"id":"forky","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / teleco_daisy-0.2.1-py3-none-any.whl
| Download URL | teleco_daisy-0.2.1-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d92fca17a89a01519156f655d2e1aee512f7e06398b9c78db0fcbc807ac8d74f
|
|
BLAKE2b-256 checksum How to use checksums |
6ea9394a0c8ac5091e689abb5e33cc5dd00100c14eee25e3bd06b40688bd9b70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.0 {"installer":{"name":"uv","version":"0.13.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"TUXEDO OS","version":null,"id":"forky","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for teleco-daisy 0.2.1
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.