Replies: 2 comments 8 replies
-
To add: It seems rtl_433 literally gets stuck. All of the sudden no new messages. rtl_433 have 0% CPU in htop and this is the last thing on the output (don't know for how long nothing happened):
|
Beta Was this translation helpful? Give feedback.
7 replies
-
I also suggest higher-quality dongles. In addition to temperature stability and metal case, they are often better calibrated to frequency in the first place, and can receive weaker signals. To me, Nooelec metal-case TCXO units and Blog v3 are the only way to go, although I bet there are other good ones I'm not aware of. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I got a Raspberry Pi Zero WH and the PoE hat which I want to use as "RF gateway" (both zigbee2mqtt and rtl_433 but for now I start with rtl_433 exclusively). I have connected a cheap "RTL2838 DVB-T".
I installed Raspberry Pi OS, removed all bulk/crap I could think of and compiled rtl_433 from scratch.
Now the issue is, this works mostly. Most of the time. If I run it for long, it seems not everything is always received. For example, I use it for DSC security sensors (window/door) and sometimes when opening/closing, no update is sent. The sensors also provide a "heart beat" message every few hours but sometimes none is received.
I also have Acurite temperature sensors. Since they transmit updates so frequently I don't see the issue there (a few dropped frames are not even visible to me).
At least while I am looking, rtl_433 uses between 4 and 10% CPU. Total load 10-20% (with the remaining part mostly htop, screen, ssh; I removed everything but udiskd, polkitd, rngd, thd, rsyslogd, dhcpd, cron).
Currently I am using this as my command line:
rtl_433 -F mqtt://10.227.79.10,user=rtl433,pass=xxx,retain=0 -F kv -M newmodel -M time:unix:usec:utc -M level -M noise -M stats -C si -R 23 -R 11 -b 524288 # -R 209
Has anyone used rtl_433 on RPiZero and can share some advice?
What could I tweak to make things more reliable?
Is the "-b" option something that I should use or not for increased reliability?
Can I figure out somehow if the issue is poor RF performance versus some low-level driver issues (e.g., dropped data) versus some rtl_433 issue? For example, can it be that Pi's CPU is too poor and sometimes data is can be missed?
Noise is always between -10dB and -11dB:
[Auto Level] Current noise level -11.4 dB, estimated noise -11.4 dB
and SNR seems to be consistently ~11dB (no matter which sensor, if near or far). I assume the "Auto Level" assumes signal as 0dB and sets gain accordingly....
I already tried connecting with a USB extension cord. Initially SNR went up to +20dB (if I recall correctly) but subsequently dropped back to ~10dB where it was with adapter directly connected. Overall, I feel connecting via USB cable has improved things slightly but it's still not reliable and I don't get all open/close messages from my DSC Security Sensors...
Beta Was this translation helpful? Give feedback.
All reactions