Hi all, I’m hoping someone has hit this and found a fix.
Setup
- Raspberry Pi 5, HAOS 18.3, Supervisor 2026.09.3, Core 2026.9.4
- Nooelec NESDR SMArt v5 (RTL2832U + R820T,
0bda:2838) plugged directly into the Pi, antenna attached - Two Nabu Casa ZBT-2s (Zigbee and Thread) on the other USB bus
- Mosquitto add-on; rtl_433 publishing to MQTT
Symptom
Both the rtl_433 (0.7.0 / rtl_433 25.12) and rtl_433 (next) add-ons start, find the tuner, set the sample rate, and then stop here:
Found Rafael Micro R820T tuner
Exact sample rate is: 250000.000414 Hz
[R82XX] PLL not locked!
After that there’s nothing: no “Tuned to 433.920MHz”, CPU at ~0.03%, and no MQTT events. The add-on still shows as running. verbose and output log are on.
Config
device 0
sample_rate 250k
frequency 433.92M
pulse_detect squelch
gain 25
protocol 40
protocol 210
verbose
convert si
output log
Already tried
- Reseating the dongle and checking the antenna
- Fixing the frequency (it was wrongly set to 433.0M)
- Switching from the
nextadd-on to stable; both behave the same
Related: there’s an open GitHub issue with the same symptom on a HA Yellow (HAOS 18.2) with the same dongle. The dongle worked on Windows but not on HAOS, and then started working again on its own: rtl_433-next receives no data after “[R82XX] PLL not locked!” with Nooelec NESDR SMArt v5 · Issue #254 · pbkhrv/rtl_433-hass-addons · GitHub
Questions
- Has anyone seen the R820T stall like this on HAOS 18.x, especially on a Pi 5?
- Could it be a USB power or bus issue with the ZBT-2s on the same Pi? Would a powered hub be worth trying?
- Are there kernel or driver changes in recent HAOS releases (DVB driver blacklist, librtlsdr) that could cause it?
Next I’m running rtl_test on another machine to rule out the dongle. Thanks!