Skip to main content

RPI_SGP30

Library to read eCO2 and TVOC from the SGP30 sensor. Based on the smbus2 i2c library for ease of use.

It should be compatible with both python 2 and 3 but is currently only tested under Python 2.7

Quick usage-example:

from smbus2 import SMBusWrapper
from sgp30 import Sgp30
import time
with SMBusWrapper(1) as bus:
    sgp=Sgp30(bus,baseline_filename="/tmp/mySGP30_baseline") #things thing with the baselinefile is dumb and will be changed in the future
    print("resetting all i2c devices")
    sgp.i2c_geral_call() #WARNING: Will reset any device on teh i2cbus that listens for general call
    print(sgp.read_features())
    print(sgp.read_serial())
    sgp.init_sgp()
    print(sgp.read_measurements())
    print("the SGP30 takes at least 15 seconds to warm up, 12 hours before the readigs become really stable"
      for i in range(20):
              time.sleep(1)
              print(".",end="")
      print()
       print(sgp.read_measurements())

Current design considerations:

The class strives to to be light-weight and portable. It is currently a bit to tightly bound to the smbus2 class. In most cases I try to ease of readability rather than purity or speed.

Features that are known to be missing (listing in rough order of importance):

  • The handing of baseline values is not that great, it should probably be up to the end user to save and restore them as needed.

  • Write doc-strings for all or at least most methods.

  • reading raw-values.

  • A more “driver like” class that takes care of all chip identification, polling at regular intervals, restoring baseline and so on.

  • Run real hardware tests under Python3

Hardware notices:

If you have the Adafruit board with built in level shifters and voltage regulator it is should work if you just plug in SDA to pin 3, SCL to pin 5, VCC to pin 17 and GND to pin 20. You should then be able to find the SGP30 an address 0x58 using i2cdetect -y 1. If you get an error message you probably need to enable i2c in the kernel using raspi-config and reboot

Feel free to contact me with bugs, questions or issues.

Metadata

Release files for sgp30 0.1.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sgp30 0.1.6
File Size Uploaded Provenance Actions
sgp30-0.1.6.tar.gz 5.7 kB Without provenance Details for sgp30-0.1.6.tar.gz

Release files / sgp30-0.1.6.tar.gz

Download URL sgp30-0.1.6.tar.gz
Size 5.7 kB
Tags Source
SHA-256 checksum
How to use checksums
91bc4bface05839d2f6f81f1378a491bdde54de47f01733aa4645bb6da19dd53
BLAKE2b-256 checksum
How to use checksums
7ec3a41fbb8db2ceda7ddbb58e664c4b10046f4618f0d43e8f8d4e910473bbcb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.20.1 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/2.7.15

Security for sgp30 0.1.6

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page