-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems like a memory leak or long run time crash? #19
Comments
I am having the same issue. Sometimes is runs for days, sometimes just hours. Each time I can clear with a restart. Tried looking for logs, but nothing is there. |
See here |
That seems like a crude work around. I want a real fix. When I get some time I'll try debugging it. |
I was experiencing the issue described here. There's references to other issues that might also help to debug it. |
I ordered a heatsinked R820T USB dongle to replace the one I have now in hopes that overheating is the source of the problem. For anyone interested: NooElec NESDR Nano 3 - Premium Tiny RTL-SDR w/Aluminum Enclosure, 0.5PPM TCXO, SMA & MCX Input & Custom Heatsink. RTL2832U & R820T2-Based Software Defined Radio |
Have you had better luck with the Nano? Would you recommend it? |
So far no time to implement it. I'm buried at work. |
i'm solved!
instead:
As repository https://github.com/merbanan/rtl_433 I used its mqtt function directly. |
In case anyone is interested, my usage pattern is a little different, but I have about the same functionality as @robertopiumatti's solution. Yet I still have the hang after a period of time, requiring reboot of the Raspberry Pi3 to resolve. This script isn't all that clean and I admit it. But there are some good ideas in it as well.
|
@alanmimms you may want to check out my solution. It turns out rtl_433 can send its output to a mqtt broker natively ! |
This is a cool add-on. I use it for remote controls and for monitoring temperature sensors.
After a week or two of uptime, I find the add-on stops working. All I have to do to fix it is to hit
restart
in theadd-on details
page, but it's slightly annoying. Do others see this behavior?The length of time it works with no issue makes me think it's a very infrequent driver hang or maybe a memory leak. I have not yet looked into the memory leak theory by paying attention to size of the process, etc., but that's the next step to debugging this I suppose. What exactly does the
restart
button do? Does it completelyrmmod
the driver? Or does it simply restart the userland process(es)?The text was updated successfully, but these errors were encountered: