tritium_remote
A library for interacting with Tritium systems. Hosted docs are here (require login).
- Connects to a running Tritium system by WebSocket
- Uses GraphQL to send commands and request data
Implemented in Rust with bindings to other languages:
This library is currently only published and tested on Linux. However the rust crate ought to work on other platforms.
This is only to be used on a trusted local network. The Tritium system will be accessed over LAN without encryption.
APIs
Sequence playback
- Start & stop sequence
Scripting
- Start & stop scripts
- Post messages to named channels to which scripts may subscribe
Generic Queries and Mutations
- Execute user-supplied GraphQL query or mutation documents
- Optional variables, supplied as JSON
- Any response is returned as a JSON encoded object
Running Examples
The Rust and Python examples use the TRITIUM_AUTH_TOKEN environment variable to get the JWT access token they need.
To generate an access token...
- Log into the Tritium cloud UI
- Connect to your locally-running system
- Go to the "Scripts" page
- Select the API Keys tab
- Click "CREATE AN API KEY"
$ export TRITIUM_AUTH_TOKEN="{paste token here}"
$ cargo run --example system_info
License
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Metadata
Release files for tritium-remote 1.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| tritium_remote-1.4.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details |
| tritium_remote-1.4.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.17+ x86-64 | Details |
| tritium_remote-1.4.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | CPython 3.9 | Linux glibc 2.17+ x86-64 | Details |
| tritium_remote-1.4.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.8 | CPython 3.8 | Linux glibc 2.17+ x86-64 | Details |
| tritium_remote-1.4.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.7 | CPython 3.7 pymalloc | Linux glibc 2.17+ x86-64 | Details |
Total release size: 71.4 MB
Release files / tritium_remote-1.4.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | tritium_remote-1.4.1-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 14.3 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
37c86629dfa8ae32411fd767cb45914a52f5c892cb8e4240135d2064302021ce
|
|
BLAKE2b-256 checksum How to use checksums |
f8ddc72a47a3d8b484afd315e666a3fab16652eb304e950636bc8b9a7610d9f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / tritium_remote-1.4.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | tritium_remote-1.4.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 14.3 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
7896fed5eddd5656271b49a418563b0341cf5e9f9f3e1f0f67223b2d80361de4
|
|
BLAKE2b-256 checksum How to use checksums |
7db5c7451f9e92e383ee52c1d72e9bc9c776c2554876c1a0ad0787315abd89fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / tritium_remote-1.4.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | tritium_remote-1.4.1-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 14.3 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
a9af28ce454792568fc4733030b8be73a2a07499769907327805fae41784abff
|
|
BLAKE2b-256 checksum How to use checksums |
cb52934aa5b7f19d57b02b68ba1cdf533b2e34c0281946fcd83bc309a6da35fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / tritium_remote-1.4.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | tritium_remote-1.4.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 14.3 MB |
| Tags | CPython 3.8 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
066b1654f4dbbed2c831701a0b2896e71b234ecfcb03849019c637d710dd22f4
|
|
BLAKE2b-256 checksum How to use checksums |
abb4df9533a0f3810af43db37da99840c6917cc4895fa8359d4a5eba51fd72b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / tritium_remote-1.4.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | tritium_remote-1.4.1-cp37-cp37m-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 14.3 MB |
| Tags | CPython 3.7 CPython 3.7 pymalloc Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
2fcc4439ef05483db12a451fd561cfd4db9225e8b8041589a9fa63c6f61f93b8
|
|
BLAKE2b-256 checksum How to use checksums |
4fd755c71fa5740870ada049e73d8c3164b40db44cf745a31157422254d80993
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for tritium-remote 1.4.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.