Issues with setting up rtl_433(next) and rtl_433 Auto discovery (next)

Configuration
21

i recieve device info in the RTL_433 (next) from my weather station and doorbell, but when i check the mqtt broker logs i see this:

2025-08-15 00:10:46: New connection from 172.30.32.2:43022 on port 1883.
2025-08-15 00:10:46: Client <unknown> closed its connection.

this is my config in rtl_433 (next)

rtl_433_conf_file: ""
retain: true
mqtt_host: mqtt://core-mosquitto
mqtt_port: 1883
mqtt_user: addons
mqtt_password: password
mqtt_topic: rtl_433/%i/events
frequency:
  - 433100000
  - 433120000
  - 433920000
protocol:
  - 40
22

Hi, I have the watchman oil sensor and I am trying to discover it like you have. I have rtl_433 and auto discovery installed and running along with mqtt explorer etc. Do you need the watchman USB receiver for this to work or is this instead of the USB receiver? Thanks for your help.

23

You don’t need any other device other than the Watchman senosr and RTL dongle. MQTT explorer isn’t needed for auto discovery but can be very handy for a manual setup .

24

Probably doing something stupid.
I have 2x USB SDR’s and can’t get them both working at the same time.
I have created the xxx.conf.template files each with different device 0 or 1, I can even swap between them and use each device as a single. But for some reason can’t get it to run both at the same time. Can anyone give me a point in the right direction. What goes in the addon config file field, should it show both adapters loading in the log (as I expect it should)?

25

Scratch that, a wipe of the config files and start again seems to have fixed it, and still can’t see why, but it works so I am happy.

26

I am picking up the watchman 433 signal, no watchman usb involved for me.

That said, it is not stable, y rtl_433 (next) frequently stopps. when i start it, it first sees the RTL-SDR dongle but then loses it immediatley:

Starting rtl_433 with rtl_433.conf... [rtl_433] rtl_433 version 25.02-29-g02657216 branch master at 202506261252 inputs file rtl_tcp RTL-SDR SoapySDR with TLS [rtl_433] MQTT: Publishing MQTT data to core-mosquitto port 1883 [rtl_433] MQTT: Publishing availability to MQTT topic "rtl_433/9b13b3f4-rtl433-next/availability". [rtl_433] MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/devices[/type][/model][/subtype][/channel][/id]". [rtl_433] MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/events". [rtl_433] MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433-next/states". [rtl_433] Found Rafael Micro R828D tuner [rtl_433] RTL-SDR Blog V4 Detected [rtl_433] SDR: Using device 0: RTLSDRBlog, Blog V4, SN: 00000001, "Generic RTL2832U OEM" [rtl_433] Exact sample rate is: 250000.000414 Hz [rtl_433] rtlsdr_read_loop: LIBUSB_ERROR_NOT_FOUND: Entity not found! Check your RTL-SDR dongle, USB cables, and power supply. [rtl_433] SDR: async read failed (-5). [rtl_433] cb transfer status: 1, canceling... [rtl_433] Input: Async read stalled, exiting! s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

A lot of faff. I wish there was a rtl433 addon solution where instructions where not opaque and teh config file was eassily accessible.

That said, occassionally it works. Hugely frustrating that someone goes to the trouble of writing and addon but then does not provide any beginner friendly guides to make usage and customisation easy.