# RPiParticle [](https://travis-ci.org/FriskByBergen/RPiParticle)
## Overview
This is a small code in the _Friskby_ project, the RPiParticle package meant to be run on a RaspberryPi (but can run on any Python-enabled POSIX system) that deals with the necessary (micro) services for
sampling
submitting
updating
controlpanel
More information on the three first can be found at [python-friskby](https://github.com/FriskByBergen/python-friskby), and the final can be found at [python-friskby-controlpanel](https://github.com/FriskByBergen/python-friskby-controlpanel/).
The first three (in python-friskby) samples information about the weather, air, climate or surrounding environment, submits the values to a webserver, and keeps itself (and us) updated and upgraded. Security fixes and general improvements are notified via the updater.
The controlpanel is a webserver running on localhost that displays status information about our own device.
## Usage
### Installation
You can install rpiparticle using pip:
` sudo pip install rpiparticle `
This will install the client code as systemd services (the four above mentioned services for sampling, submitting, etc).
To run RPiParticle, you obtain an _unlocked_ device ID from the friskby project. If you don’t have one, you can either construct it yourself (needs login), or contact one of the friskby members.
To construct a device,
Configure your Device in the Devices table.
b. Configure two sensors attached to your device - these sensor must have the name of your device, suffix _PM10 and _PM25 respectively.
c. Make sure the “Locked” checkbox on your device is unchecked. Observe that this will automatically be relocked after you have associated the client with the device id.
After having obtained an unlocked device ID, you can go in to http://0.0.0.0. It will query the user for a device ID and then query the Webserver for a configuration file (containing post URL and a secret API key) for that device ID and download and store it to the file system.
### Manual restart
It should not be necessary to manually restart the friskby client, but if things go wrong for some reason, go to the raspberry pi’s website and press Restart or follow these steps:
SSH into the device
2. Stop the current client with: `bash sudo systemctl restart friskby-sampler sudo systemctl restart friskby-submitter sudo systemctl restart friskby sudo systemctl restart friskby-controlpanel `
Metadata
Release files for RPiParticle 0.9.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 |
|---|---|---|---|---|
| RPiParticle-0.9.3.tar.gz | 4.8 kB | Without provenance | Details for RPiParticle-0.9.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| RPiParticle-0.9.3-py2-none-any.whl | Python 2 | none | any | Details for RPiParticle-0.9.3-py2-none-any.whl |
Total release size: 14.7 kB
Release files / RPiParticle-0.9.3.tar.gz
| Download URL | RPiParticle-0.9.3.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d04655b0a46fe1c0c370421244a4962d7dc4c063a0cb640a88d6190ad122a375
|
|
BLAKE2b-256 checksum How to use checksums |
90a833826113bc9b0e417497a6184c7ca2e4c0f789764c7c2dddfe8da15e44b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / RPiParticle-0.9.3-py2-none-any.whl
| Download URL | RPiParticle-0.9.3-py2-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
a296a2b5bc13c377602762c6191761a8910576546387981cb424c2723eaa87f5
|
|
BLAKE2b-256 checksum How to use checksums |
0345c8c744f8e70408dbf9b5f7024dd6749b341b5db01a6a05720fb760de82c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for RPiParticle 0.9.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.