SDR recognized, but no decoding of signals

703 views
Skip to first unread message

linuxus

unread,
Dec 31, 2021, 5:39:08 AM12/31/21
to rtl_433
Hello,

I've reinstalled rtl_433 from the AUR today because it didnn't decode signals for some reason. Unfortunately, it still doesn't decode anything although I can see the strong signal of my weather station in Gqrx and I tuned rtl_433 to that frequency.
I'm using a Manjaro system and my SDRs are the DX Patrol MK2 and the NooElec NESDR Mini 2. I don't remember if I was already able to decode signals with the second SDR, but with the DX Patrol MK2 it always worked flawlessly in the past.

Does anyone know what might be the problem why rtl_433 doesn't decode signals in my case?
Thank you for your help in advance!

Christian Z.

unread,
Dec 31, 2021, 6:52:13 AM12/31/21
to rtl_433
Try different center frequencies and sample rates. See https://triq.org/rtl_433/ANALYZE.html

Christian Z.

unread,
Jan 8, 2022, 2:31:03 PM1/8/22
to rtl_433
But how can I now disable these messages?:
sample rate too low for protocol 198 "EnOcean ERP1" 
Current signal level -19.0 dB, estimated noise -24.1 dB
Estimated noise level is -25.7 dB, adjusting minimum detection level to -22.7 dB 

Don't enable features you don't need. You enabled protocol "-R 198" and stats with "-M level"
 
Now it also shows the data in this format as well as in the colored format:
{"time" : "2022-01-08 19:30:53.157938", "protocol" : 25, "model" : "GT-WT02", "id" : 94, "channel" : 1, "battery_ok" : 

Don't add "-F json" if you don't need it.
 

Christian Z.

unread,
Jan 8, 2022, 5:32:52 PM1/8/22
to rtl_433
I started rtl_433 by running "rtl_433 -F kv" because that option delivers the normal output that I was  used to from former versions. But in addition to that it outputs lots of other data

That might be from settings in a .conf file that got installed. Watch the first lines of output for the path, then change the options in the .conf file.

linuxus

unread,
Jan 9, 2022, 3:12:53 PM1/9/22
to rtl_433
When I set the the variable "verbose" to 0 and put an # in front of the report_meta entries that doesn't help either.

Christian Z.

unread,
Jan 9, 2022, 10:49:10 PM1/9/22
to rtl_433
Delete the whole file. It's just an example and obviously not the one you want.

Tuatha De danaan

unread,
Jan 10, 2022, 10:49:18 AM1/10/22
to Christian Z., rtl_433
I made an easy video to follow to demod this signal. Use it to double check your rtl433 data. https://youtu.be/jUv9Ib1c6LM

On Jan 9, 2022, at 10:49 PM, Christian Z. <chri...@zuckschwerdt.org> wrote:


Delete the whole file. It's just an example and obviously not the one you want.

--
You received this message because you are subscribed to the Google Groups "rtl_433" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtl_433+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rtl_433/569d8e37-a652-4769-b616-ed1164b5b31bn%40googlegroups.com.

Christian Z.

unread,
Jan 10, 2022, 11:04:10 AM1/10/22
to rtl_433

I made an easy video to follow to demod this signal. Use it to double check your rtl433 data. https://youtu.be/jUv9Ib1c6LM

Very nice and easy walkthough!
 

linuxus

unread,
Jan 10, 2022, 1:06:24 PM1/10/22
to rtl_433
Thank you for creating that video! As I've already mentioned in one of my previous messages I could solve the problem by installing the git version. Now it's all about getting rid of these noise level messages.

linuxus

unread,
Jan 10, 2022, 1:07:30 PM1/10/22
to rtl_433
When I delete the config file, I can't receive anything anymore.

Christian Z.

unread,
Jan 10, 2022, 2:25:50 PM1/10/22
to rtl_433
When I delete the config file, I can't receive anything anymore.

Did you have a center frequency setting in there? You can also use e.g. "-f 868.3M" for that.

linuxus

unread,
Jan 10, 2022, 2:29:25 PM1/10/22
to rtl_433
Yes, 433.975 MHz.
Reply all
Reply to author
Forward
0 new messages