rtl_433 VS rtl-power-fftw

And there's a multiformat receiver block too: https://github.com/merbanan/rtl_433

pi@pi4b8:/etc/systemd/system $ cat rtl_433.service # based on https://github.com/merbanan/rtl_433/issues/1651 [Unit] Description=RTL_433 service script StartLimitIntervalSec=5 Documentation=https://github.com/merbanan/rtl_433/README.md After=syslog.target network.target [Service] Type=exec ExecStart=/usr/bin/rtl_433 -C si -F mqtt # Restart script if stopped Restart=always # Wait 30s before restart RestartSec=30s # Tag things in the log # View with: sudo journalctl -f -u rtl_433 -o cat SyslogIdentifier=rtl_433 StandardOutput=syslog StandardError=syslog [Install] WantedBy=multi-user.target

For example, rtl_433 has the spec for an X10 sensor say I know what data I want to put where, is there some tool/site I could enter in what the "specifications" of the signal waveform are and the data I want to send as a byte-string or binary-string and it would create a playable .sub file for me?

For "outdoor distances" I'd probably stick to something LoRa or 433MHz based. YoLink has quite a few options using the LoRa protocol. I use basic 433Mhz based AcuRite sensors paired with an RTL-SDR dongle connected to a machine running RTL_433, and use Home Assistant to trigger automations and alerts.

866-868MHz is SRD/ISM band (in UK/EU). Can be things like energy meters, TPMS, medical devices etc. Try rtl_433 on it.

I'm trying to add a Honeywell doorbell to Home Assistant by using the RTL-433 GitHub project/program. When I run the program the SDR dongle is detected but it doesn't display anything when I press the doorbell (the image shows what I see after running the program and pressing the doorbell). I have also tried Honeywell Activelink (FSK) aka [116], so I have tried both 115 and 116 decode protocols.

rtf_433 IoT & embedded device signal receiving https://github.com/merbanan/rtl_433

https://github.com/AD-Vega/rtl-power-fftw can help. This can be easily piped for various outputs and works with GNUPlot off the bat. Use this on an Android based SDR for foxhunting and Signal seeking.

I like to use rrl_power_fftw

You could use rtl_power_fftw to better record the wider band over a time period. This is similar to rtl_power from librtlsdr, but is more efficient and can dwell for as little as 100ms on any 2.4MHz window (24MHz done in 1 second, f.e.). You can then plot this data through GNUPlot to get visual representations.

These are made using rtl-power-fftw and GNUPlot

I have a rooted Android with an RTL-SDR attached, which I'd take with me if buying a new laptop. I'd sit near the laptop's on display with a stubby duck in the SDR and use rtl-power-fftw to rapid scan 27-1724MHz (fastest is 100ms dwell at 2.4MSps). Takes a minute or two and can be fed into GNUPlot to give you a pretty graph of signals seen. Do it at a low gain and any spikes you see are likely from those sources.

rtl-power-fftw

Look into rtl_power_fftw. It can be run for hours on any host (including a Raspberry Pi) and the spectrum results examined later.

rtl_power_fftw is likely more well suited. It's multithreaded, so can sample IQ and process the data as it samples. It's also faster and uses libfftw for processing (faster and more accurate). Outputs more friendly, too. I use this in part with a signal heatmap project; https://www.reddit.com/r/RTLSDR/comments/ifer8j/progress_on_the_android_sdr_linuxdeploy_rtl_power/