rtl_433 VS rtl-sdr

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

A network protocol called rtl_tcp that has been ported to rsp_tcp by the guys at SDRPlay in order to increase the IQ bandwidth from 8 to 14 bits to get the most from their SDRs. SDRPlay has provided a rsp_tcp server app/image that can be run on various hosts including RPi. Your RSPxx SDR connects to the RPi via USB and the RPi connects to your local network via Ethernet or Wi-Fi. Any network client application that supports rsp_tcp/rtl_tcp (including SDRUno) can connect to the RPi and use the SDR just as if it was connected via USB. This not only allows you to use your SDR from potentially anywhere you have a computer, it also allows you to minimize the distance between the SDR and the antenna(s). In theory you could even run Ethernet cable right up to the antenna.

The version from Osmocom does have the -T option. https://github.com/osmocom/rtl-sdr

Correct, I am using the RTL-SDR software >> https://github.com/osmocom/rtl-sdr

rtl_sdr

For remote-location of an RTL dongle using Raspberry Pi or similar, which linux or windows clients can connect to over wifi or ethernet, there is rtl_sdr

Hmm. I'd check out the RTL-SDR Sourcecode, in particular rtl-test, and manpage. This tool lets you calculates the PPM error of your dongle.

Not sure if it’s exactly what you want, but you can control GQRX over TCP. If you want more granular control, you can use the rtl-sdr library to process your desired signal. In my opinion it’s a bit low level for your project so using its Python wrapper, PyRtlSdr so you can get most of the rtl-sdr functionality while using Python’s networking.