rtl_433_discoverandsubmit
A Home Assistant integration that connects to an MQTT server, listens to rtl_433 events and allows users to add devices through the standard discovery flow.
Features
- Connects to an MQTT server.
- Listens to
rtl_433events in real-time. - Uses Home Assistant's config flow to manage devices.
- No entities are created without user confirmation.
- Includes a command line interface for manual discovery.
- Allows sorting of devices by last seen time, model or message count.
- Press k in the CLI to reset message counters.
Screenshot of devices listed
Detailed device view and opportunity to add to Home Assistant
Device added to Home Assistant
Installation
You can install rtl_433_discoverandsubmit directly from PyPI:
pip install rtl_433_discoverandsubmit
Usage
Install the custom integration and add it via Home Assistant's integrations page. During setup you will be asked for MQTT connection details and the topic to listen to. Newly discovered devices will trigger a prompt asking whether they should be added.
The package also installs a small CLI tool called rtl_433_discoverandsubmit which can be used without Home Assistant. Run it with your MQTT connection details:
rtl_433_discoverandsubmit --mqtt_server 192.168.1.10 --mqtt_port 1883 --topic rtl_433/+/events
Use the s key to cycle sorting of detected devices and k to reset the message counters if you want to start again. Accepted devices are persisted in ~/.rtl_433_discoverandsubmit/devices.json.
##Contributing
Feedback, bug reports, and pull requests are super welcome on this project. If you face any issues, please raise them in the issue tracker.
##License
This project is licensed under the MIT License. See the LICENSE file for more details.
Metadata
Release files for rtl-433-discoverandsubmit 0.1.14
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 |
|---|---|---|---|---|
| rtl_433_discoverandsubmit-0.1.14.tar.gz | 16.6 kB | Without provenance | Details for rtl_433_discoverandsubmit-0.1.14.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rtl_433_discoverandsubmit-0.1.14-py3-none-any.whl | Python 3 | none | any | Details for rtl_433_discoverandsubmit-0.1.14-py3-none-any.whl |
Total release size: 35.4 kB
Release files / rtl_433_discoverandsubmit-0.1.14.tar.gz
| Download URL | rtl_433_discoverandsubmit-0.1.14.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
759871e93b418dd7b1e65fbd0406e54b88223ff66e8e9d69bc11afcc4bab63bd
|
|
BLAKE2b-256 checksum How to use checksums |
254fd989aa71b359cf1e822b5290ad495c9c527ed7e08927e60c35aab3be4d92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / rtl_433_discoverandsubmit-0.1.14-py3-none-any.whl
| Download URL | rtl_433_discoverandsubmit-0.1.14-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
82077ef832bb01e666c63416505c24ae0e6914178a90e6fd2e9b072250173697
|
|
BLAKE2b-256 checksum How to use checksums |
03b341bbee2ba1ecf589da1284a3f778272e16ac50afbc2cb6d149c956992065
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for rtl-433-discoverandsubmit 0.1.14
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.