Allows you to record RF signals and play them back on a Rapsberry Pi.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitignore Support packaging Jan 10, 2017
LICENSE Initial commit Jan 4, 2017
README.rst Update README.rst Feb 5, 2019 Actual initial-commit Jan 10, 2017
requirements.txt Actual initial-commit Jan 10, 2017 play back multiple signals Jan 12, 2017
setup.cfg Support packaging Jan 10, 2017



Allows you to record RF signals and play them back on a Rapsberry Pi.

Nowadays, many remotes are sending over cheap RF transmitters. Especially alot of the home automation devices usually communicate over these RF links.


Through pip:

$>sudo pip install rpi-rfsniffer

Latest development version (in linux):

$>git clone
$>cd rpi-rfsniffer
$>sudo python install


By default it assumes you have attached the transmitter on pin 11 and the recevier on pin 13:

# To record signal
$>rfsniffer record remotename.button1
  Press remotename.button1
  Recorded 64 bit transitions

# To transmit/send that signal (twice)
$>rfsniffer play remotename.button1 remotename.button1

# To dump all the recorded signals
$>rfsniffer dump

Hardware guide

All pin assignments refer to board numbers (rather than chipset pin layout). Allthough it has only been tested on RPi2, according to RPi doc all boards should be pin compatible. Worth mentioning is that it is assuming soft pull-down resistor mode for all recordings, so you should avoid GPIO pins 2-3 since these have fixed pull-up resistors.

Signal recording

Worth mentioning is that rfsniffer only is a thin wrapper around RPi.GPIO. rfsniffer simply reads bitflips using RPi.GPIO.wait_for_edge(..) and records the timing between these transitions. It ignores any signals with fewer than 5 transitions due to that its assumed that most RF systems have atleast a 5 bit preamble. Furthermore, it will continue reading a signal until atleast 1 second has passed without any additional signals. So if you record a buttonpress, you will likely want to release the button as you would normally so that rfsniffer can detect that there are no more signals and then store the signal in the database.