-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Broken hardware or mistake on my side? #3087
Comments
Unfortunately your usb stick is not using a good tuner. Fitipower FC0012 is not known for being sensitive, quite the contrary, and especially at 868Mhz it's close to its limit. Interference must be limited, use a good usb cable extension 50 cm / 1m , to reduce computer noise, a good antenna. Then play with -g gain level and -Y options could help. |
@ProfBoc75 Thanks for your advice! I now used the following command line on the Windows PC: Then the magic happened:
I tried to translate these settings to the following conf file and moved back to my Home Assistant computer, which is even closer to the doorbell.
Here, I get fewer
What am I doing wrong? |
Noise at -15 dB could be ok, depends on the signal noise ratio (snr) should be around 10 / 12 dB. Try to get the figures with option If you have a RSSI close to 0 dB , then SNR = 15 dB with Noise = -15 dB it's ok, very good signal. Again, lot of attention around the antenna and nothing around the stick and antenna that could generate rf noise like a computer, a screen, any electronic device generates rf interference/noise. Another option is Edit: if the usb stick box is made of plastic, so it doesn't filter out any external interference, you can wrap a small sheet of aluminum foil around it (2 or 3 wraps around it are sufficient) to create a Faraday cage / electromagnetic shield, which will also reduce noise too. |
OK, this looks good. Conf file is:
Output is:
If I got your point right, that is a quite usable signal, right? |
@Tobster77 yes, looks good for me. You can remove -M options if you want, up to you (it's verbose only) Notice that, because of the filter=150 this could exclude some sensors, since it's working as a low pass filter, any other sensor with lower pulse than 150 us will be filtered out. If you want to change your usb stick dongle, you may look at Rafael Micro R828D tuner (formerly R820T) or better Rafael Micro R860 (formerly R820T2). R820Tx does not exist anymore since years even if Chinese low-cost web sites propose usb RTL SDR dongle supposedly based on this component, most of the time it's not the good tuner and supplied with FC0012/13 tuner which does not cover the full range of frequency up to 1.7 GHz, and not only, the sensitivity and noise are not good too. Fitipower FC0012 tuner frequency range is from 22 to 948.6 MHz, bad sensitivity, bad noise floor. |
Thanks a lot! The cheap stick now works well. Your proposal of the filter setting was the game changer... :-) |
I try to receive a Honeywell doorbell type DW915s ringing. The doorbell uses 868Mhz and a protocoll called ActivLink. I think found it in this list .
I bought a simple SDR USB stick (https://www.berrybase.de/dvb-t/dab/fm/sdr-usb-stick-mit-rtl2832u-chipsatz?number=125187) and tried first in Home Assistant, but I could get no readings. I also tried a 315M remote, but no readings as well.
I then installed the stick on a Windows PC together with Zadig drivers. Here I could enable verbose mode: Looks like both the doorbell and the remote cause some receivable data, but it seems not to be proper. For example, the doorbell causes some data on honeywell_cm921_decode, but this does not seem to be a clear reading, only debug data.
Logs are attached for 315M, 868M and - to be sure it is no frequency issue - 868.35M.
Am I too silly to configure this, or is this a hardware issue?
Thanks for your help!
rtl_433_868M.txt
rtl_433_315M.txt
rtl_433_868_35M.txt
The text was updated successfully, but these errors were encountered: