https://github.com/rh0/rtl433_to_mqtt
Simple dockerfile for rtl_433 specifying output to MQTT
https://github.com/rh0/rtl433_to_mqtt
dockerfile mqtt mqtt-client rtl-433 rtl-sdr
Last synced: 2 months ago
JSON representation
Simple dockerfile for rtl_433 specifying output to MQTT
- Host: GitHub
- URL: https://github.com/rh0/rtl433_to_mqtt
- Owner: rh0
- Created: 2020-02-05T02:22:17.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-04-25T16:08:15.000Z (about 3 years ago)
- Last Synced: 2025-01-28T23:50:17.979Z (4 months ago)
- Topics: dockerfile, mqtt, mqtt-client, rtl-433, rtl-sdr
- Language: Dockerfile
- Homepage:
- Size: 3.91 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# rtl_433 to MQTT :satellite: :loudspeaker:
Dockerfile to help containerize some functionality from https://github.com/merbanan/rtl_433. Specifically publishing recieved device messages to an MQTT broker.
## Setup
Connection details for the MQTT broker are handled via the following environment variables:
+ **MQTT_HOST** _host for mqtt broker_
+ **MQTT_PORT** _mqtt port, defaults to 1883_
+ **MQTT_USER** _mqtt username_
+ **MQTT_PASS** _mqtt password_
Since rtl_433 uses USB attached SDRs you'll need to pass through the device to container (this requires the privileged flag).
For example, with docker compose:
```yaml
rtl433:
build:
context: https://github.com/rh0/rtl433_to_mqtt.git
image: rh0/rtl433_to_mqtt:latest-dev
container_name: rtl433
restart: always
env_file:
- ./rtl433.env
privileged: true
devices:
- /dev/bus/usb:/dev/bus/usb
```
If all goes well and your radio is in range of a 433mhz device broadcast, your MQTT broker should start receiving messages from those devices in the `rtl_433` topic.