cyberfly-client-sdk
A python client sdk to interact with cyberfly node to pubsub and store data
Install
pip3 install cyberfly-client-sdk
Example
listen on data
from cyberflySdk import CyberflyClient
kp= {"publicKey": "d04bbd8f403e583248aa461896bd7518113f89b85c98f3d9596bbfbf30df0bcb",
"secretKey": "a0ec3175c6c80e60bc8ef18bd7b73a631c507b9f0a42c973036c7f96d21b047a"}
client = CyberflyClient(node_url="https://node.cyberfly.io", device_id="093062d0-a357-4f8a-a1cb-35f1b43c12ae",
key_pair=kp, network_id="testnet04")
@client.on_message()
def do_something(data):
print(data)
while 1:
pass
publish data
from cyberflySdk import CyberflyClient
import time
kp = {"publicKey": "d04bbd8f403e583248aa461896bd7518113f89b85c98f3d9596bbfbf30df0bcb",
"secretKey": "a0ec3175c6c80e60bc8ef18bd7b73a631c507b9f0a42c973036c7f96d21b047a"}
client = CyberflyClient(node_url="https://node.cyberfly.io", device_id="093062d0-a357-4f8a-a1cb-35f1b43c12ae",
key_pair=kp, network_id="testnet04")
while 1:
client.publish("device id or any topic", {"Temp": 22})
time.sleep(1)
Metadata
Release files for cyberfly-client-sdk 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cyberfly_client_sdk-0.1-py3-none-any.whl | Python 3 | none | any | Details for cyberfly_client_sdk-0.1-py3-none-any.whl |
Release files / cyberfly_client_sdk-0.1-py3-none-any.whl
| Download URL | cyberfly_client_sdk-0.1-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7269206fe2b976ddfab0281c6a39e9ecc0f38a45dac06bb3f68abf68b30c57be
|
|
BLAKE2b-256 checksum How to use checksums |
1c8a51089332ae498cb29fb30d26e9fcb18c635ed593a042ab6039fc1bc6849a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.9
|
Security for cyberfly-client-sdk 0.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.