wireless-sensor-mqtt 🌡
MQTT client reporting measurements of FT017TH wireless thermo/hygrometers
Requirements
- MQTT broker
- FT017TH sensor
- CC1101 transceiver
- Linux machine with CC1101 connected to SPI port &
GDO0connected to some GPIO pin (wiring instructions for raspberry pi)
Setup
$ pip3 install --user --upgrade wireless-sensor-mqtt
Usage
$ wireless-sensor-mqtt \
--gdo0-gpio-line-name GPIO24 \
--mqtt-host HOSTNAME_OR_IP_ADDRESS \
--mqtt-topic-prefix MQTT_TOPIC_PREFIX
Measurements will be published on topics
MQTT_TOPIC_PREFIX/temperature-degrees-celsius
and MQTT_TOPIC_PREFIX/relative-humidity-percent
(e.g., living-room/temperature-degrees-celsius
with --mqtt-topic-prefix living-room).
Add --debug to get debug logs.
MQTT via TLS
TLS is enabled by default.
Run wireless-sensor-mqtt --mqtt-disable-tls … to disable TLS.
MQTT Authentication
wireless-sensor-mqtt --mqtt-username me --mqtt-password secret …
# or
wireless-sensor-mqtt --mqtt-username me --mqtt-password-file /var/lib/secrets/mqtt/password …
Home Assistant 🏡
Home Assistant will detect two new sensors automatically, if connected to the same MQTT broker and MQTT discovery is enabled (enabled by default since version 0.117.0).
When using a custom discovery_prefix, run wireless-sensor-mqtt --homeassistant-discovery-prefix custom-prefix ….
Docker 🐳
Pre-built docker images are available at https://hub.docker.com/r/fphammerle/wireless-sensor-mqtt/tags
$ sudo docker run --name wireless_sensor_mqtt \
--device /dev/spidev0.0 --device /dev/gpiochip0 \
fphammerle/wireless-sensor-mqtt \
wireless-sensor-mqtt --mqtt-host HOSTNAME_OR_IP_ADDRESS …
Optionally add --read-only --cap-drop ALL --security-opt no-new-privileges before image specifier.
Annotation of signed tags docker/* contains docker image digests: https://github.com/fphammerle/wireless-sensor-mqtt/tags
Docker Compose 🐙
- Clone this repository.
- Edit
docker-compose.yml. sudo docker-compose up --build
Metadata
Release files for wireless-sensor-mqtt 1.0.0
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 |
|---|---|---|---|---|
| wireless-sensor-mqtt-1.0.0.tar.gz | 98.5 kB | Without provenance | Details for wireless-sensor-mqtt-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wireless_sensor_mqtt-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for wireless_sensor_mqtt-1.0.0-py3-none-any.whl |
Total release size: 118.7 kB
Release files / wireless-sensor-mqtt-1.0.0.tar.gz
| Download URL | wireless-sensor-mqtt-1.0.0.tar.gz |
|---|---|
| Size | 98.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b39111897448a509b7ae3913faf8f0b2b2a245b5b907d4cca82e4bead781f410
|
|
BLAKE2b-256 checksum How to use checksums |
360b3c62da3dbf7ddf28f85c53c43226d8e99c62a8c08ddd6f3eb21c278b672f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / wireless_sensor_mqtt-1.0.0-py3-none-any.whl
| Download URL | wireless_sensor_mqtt-1.0.0-py3-none-any.whl |
|---|---|
| Size | 20.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c49baf9420c7cc28dec279ca95af706b0de5aee36c6de3b5c06c4e4a7425d673
|
|
BLAKE2b-256 checksum How to use checksums |
50a68095b1a6b7c67b01c184f54bb252fce59b1e4e954becc1d9a22ace1d2f40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for wireless-sensor-mqtt 1.0.0
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.