GitXplorerGitXplorer
r

rtl433_to_mqtt

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
519121b8898c74f66ab5dd415c7aac79be3b3c50

removing debug

rrh0 committed 3 years ago
Unverified
3a1e98ce37962de2db1a57e9a7367b898af2b904

adding a bit of debug

rrh0 committed 3 years ago
Unverified
1710a3306b183bc04362bc8c18724dfec9c0febf

emoji adjustment

rrh0 committed 4 years ago
Unverified
b02bdf2089f9eb9c275df423cd22927611c7d607

emoji

rrh0 committed 4 years ago
Unverified
b4335404282dc019819ce3b9f9e39f9d9af2bc3f

more readme edits

rrh0 committed 4 years ago
Unverified
2a0a1adfc87209703a132360a74f253fd8db9042

markdown adjustments

rrh0 committed 4 years ago

README

The README file for this repository.

rtl_433 to MQTT 📡 📢

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:

  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.