rtl_433 icon indicating copy to clipboard operation
rtl_433 copied to clipboard

RTL stops receiving data with HA on RPi 4

Open donoghdb opened this issue 4 years ago • 9 comments

I have tried a number of addon's for HA but the issue still occurs where rtl_433 stops receiving data after a number of hours. Im using protocol 43. I have an automation to restart the addon after a time period and sometimes that works, other times i need to unplug the SDR. How can i see what is happening and why it is not receiving data? I am using this integration https://github.com/pbkhrv/rtl_433-hass-addons/tree/main/rtl_433

donoghdb avatar Dec 14 '21 21:12 donoghdb

Likely the band you are watching is jammed or the signal drifted out of range. See https://triq.org/rtl_433/ANALYZE.html

zuckschwerdt avatar Dec 15 '21 08:12 zuckschwerdt

looking at the data, most of the time i get data every 15 minutes then sometimes nothing. No sign of it drifting (not that i can see anyway from the charts). I switched to a mac so i can watch the data come in. I wonder if anyone else has seen the issue of the Oil watchman randomly stopping sending data. There is nothing around that is changing to suddenly interfere with the signal.

donoghdb avatar Dec 15 '21 21:12 donoghdb

The -S unknown mode can help to find undecoded transmissions. It will take up some disk space though. Or perhaps try the HTTP output and follow signals there, use Modes->Raw to visualize but not save the signals.

zuckschwerdt avatar Dec 17 '21 06:12 zuckschwerdt

I have a similar issue but wasn't sure if it was the same so opened another issue. If it turns out these are related they can be combined.

https://github.com/merbanan/rtl_433/issues/1912

bkenobi avatar Dec 23 '21 03:12 bkenobi

I moved my antenna, reinstalled HA and RTL and I am no longer getting the issue. The data I'm getting on the terminal is the same as MQTT. I do have an automation checking the time between messages and if it's above 30 minutes it restarts the addin. But since I have done the above, it has not triggered.

donoghdb avatar Dec 23 '21 08:12 donoghdb

The data output to MQTT is the same as decoded. In my case one or more devices stop being decoded after a while. I currently have 5 total (1 blueline, 4 accurite). The blueline has been going offline recently. Was off yesterday, i restarted rtl_433 and it was back. It went down again last night but havent checked it yet.

bkenobi avatar Dec 23 '21 15:12 bkenobi

It looks like this thread is largely dead, but I will say I have the same problem. It's frustrating. Even restarting sometimes doesn't fix it. Seems if I turn it off for a while, then it will kick back in. Also, strangely, if I play with the antenna it sometimes comes back. If I run directly off a computer, no problem, but on a Pi, it will die every couple days. I'd definitely take any advice on perhaps how to tune the radio settings a bit more? I'm running pretty much default, which works, until it doesn't.

danielgoepp avatar Jun 23 '22 10:06 danielgoepp

I should have updated but in my case the issue turned out to be a faulty sensor. In my experience the Blueline device is very poor quality. My 1st unit lasted a few years before water got in combined with battery corrosion. The 2nd (this one) lasted a couple months. The 3rd was doa. The 4th unit has been perfect since installed (1/2022 ish).

I have also tested a lot more acurite sensors. I have a 5in1 weather station and ~8 temp/humidity sensors that can all work together (though the do start to interfere). During all of this I've had minimal issue with the radio or rtl_433. In the other thread i provide a solution in case the unit doesn't work the 1st time due to a bad auto-gain setting.

bkenobi avatar Jun 23 '22 14:06 bkenobi

@bkenobi thanks for the follow up. I just started reading that other thread now...that will take a while :) I have an Acurite Atlas and 3 different radios, they all seem to do the same (2xNooelec NESDR and one that I got with the ADS-B PiAware project).

danielgoepp avatar Jun 23 '22 20:06 danielgoepp

This feels like several reports that all amounted to flaky hardware. If you have a situation where you think there's a bug in rtl_433 please feel free to open a fresh issue, tested against up-to-date git master.

gdt avatar Sep 30 '23 22:09 gdt