RPi.Sensor
Generic Python base class to create infinite loop to work with different sensors connected to Raspberry Pi. Project contains also extended Python base class with MQTT support.
RPi.Sensor library is stable in terms of running as a base class. Sensor logic and additional functionality before and after sensor measurement should be implemented in child objects anyway… But there are new features developed (and bug fixed as they are found) so it is recommended always use the latest version.
If you want to see example of implemented sensors, have a look at my other RPi repo.
Installation
Install the latest released version using pip:
pip install https://github.com/ricco386/RPi.Sensor/zipball/master
Alternatively install latest released version from pypi:
pip install --upgrade RPi.Sensor
Make sure all dependencies (listed below) are installed (done automatically when installing via pip)
Dependencies:
Usage
Inherit Sensor object or MqttSensor.
Main purpose of the sensor object is to run infinite loop for reading from the sensors. Object has build in basic functionality to terminate the infinite loop correctly (uppon CTRL+C or kill signal), basic logging etc.
Intention is to have ability to easily run some code before (or after) reading the sensor, this is is skeleton that doesnt do any logic and should be used only as a base for building the interactions with the sensors.
If you want to see example of implemented sensors, have a look at my other RPi repo.
If you find a security vulnerability please read through SECURITY.rst file and report it responsibly. All other issues and feature requests report via Github issue tracker.
License
For more information see the LICENSE file.
Metadata
Release files for RPi.Sensor 0.5.3
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 |
|---|---|---|---|---|
| RPi.Sensor-0.5.3.tar.gz | 8.1 kB | Without provenance | Details for RPi.Sensor-0.5.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| RPi.Sensor-0.5.3-py3-none-any.whl | Python 3 | none | any | Details for RPi.Sensor-0.5.3-py3-none-any.whl |
Total release size: 19.3 kB
Release files / RPi.Sensor-0.5.3.tar.gz
| Download URL | RPi.Sensor-0.5.3.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27ac91db0b7c7952c1a2d43b75c3897a1ac4c7245dbfd6005f2e1c3e63ac5a61
|
|
BLAKE2b-256 checksum How to use checksums |
b005cb8507dbf25de6d0bb51799ac773ecc10cef154262b1c9b03b2696a2e609
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Release files / RPi.Sensor-0.5.3-py3-none-any.whl
| Download URL | RPi.Sensor-0.5.3-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e61120377cb02c87310573ecc5d871f6bd821b9f94aec01de71b90a50c987d17
|
|
BLAKE2b-256 checksum How to use checksums |
cdd18d92abd8ad56ec99009ff23615756d2f782d85ad604732cf7ce836303a1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.48.0 CPython/3.8.3
|
Security for RPi.Sensor 0.5.3
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.