Tigerente
A command line tool to connect to and manage LEGO Spike Primes running Spielzeug.
It works by running a background process that keeps the bluetooth connection alive; any commands are sent to it.
Name
Nobody had a good idea how to name this, so we chose something that has to do with toys.
Features
- Connect & Disconnect
- Sync folders
- Reboot
- Start & Stop programs
TODO / Roadmap
--watch-Flag to sync changes directly without rerunningtente sync- Command to download and flash Spielzeug automatically
- Command to rename a device
- More?
Example usage
# Connect to a hub
$ tente connect
These devices seem to be nearby:
- HubA (34:08:E1:8D:26:98)
- HubB (38:0B:3C:A2:27:91)
Choose a device to connect to: HubB
[✔] (00:11) Connected to HubB.
# Sync the "src" folder to the connected hub
$ tente sync src
[ℹ] You are connected to HubB.
Sync directory... ━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:04
[✔] Synced.
# Again, but ensure you are connected to HubA
$ tente sync src --dev HubA
[ℹ] You are connected to HubA.
Sync directory... ━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:05
[✔] Synced.
# Disconnect from the connected hub
$ tente disconnect
[ℹ] You were connected to HubA.
[✔] (00:03) Disconnected.
1 maintainer
Metadata
1 maintainer
Release files for tigerente 0.5.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 | Actions |
|---|---|---|---|---|
| tigerente-0.5.1.tar.gz | 17.6 kB | Without provenance | Details for tigerente-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigerente-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for tigerente-0.5.1-py3-none-any.whl |
Total release size: 40.2 kB
Release files / tigerente-0.5.1.tar.gz
| Download URL | tigerente-0.5.1.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28b53b2fbdb4a4b98030e4fa5c402c4238c52654af9e49674e41759208006435
|
|
BLAKE2b-256 checksum How to use checksums |
a5e493e6a5188bb1c2094f7c6e9752deb24f40b1b574cf6879885648ea88771a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / tigerente-0.5.1-py3-none-any.whl
| Download URL | tigerente-0.5.1-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ebdbd9eb9fdd4625e18373890fffef46fb9274405e386e3845c425e110c95d6a
|
|
BLAKE2b-256 checksum How to use checksums |
4ac1129102e5c9156ed8b26107f92c069a2fd878cd6b19268682db3b4988b35c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.21 {"installer":{"name":"uv","version":"0.9.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Arch Linux","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for tigerente 0.5.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.
