Pi Setup<\/h2>\n\n\n\n
First we will setup the Pi. I won’t go through the full setup, as there are many guides out there, but here is a very quick overview of the setup:<\/p>\n\n\n\n
- I am using the DietPi<\/a> operating system<\/li>
- Once the OS is installed, you need to install rtl_433<\/a>. This is the software we will use to capture the signal, and then send it to Home Assistant via MQTT.<\/li>
- Plug in the RTL-SDR USB and reboot the Pi. <\/li>
- Test the SDR is working by running:
sudo rtl_433<\/code>. Any signals received and decoded will appear on screen, I usually get a stream of signals from the tyre pressure monitors of passing cars and a local weather station:<\/li><\/ul>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/www.atombrake.info\/wp-content\/uploads\/2021\/04\/image.png?resize=525%2C207&ssl=1\")
Example of signals received, showing the SDR is working.<\/figcaption><\/figure>\n\n\n\n - If you test the doorbell now, it is unlikely that it will be decoded, as each doorbell uses a unique signal. Mine changes each time the pairing mode is activated, or the chime sound changed.<\/li>
- Press ctrl-C to exit rtl_433<\/li><\/ul>\n\n\n\n
Capture the signal<\/h2>\n\n\n\n
To capture the signal we will use the pulse analyser mode to capture the signal, this will analyse the signal from the doorbell and give us the details needed.<\/p>\n\n\n\n
Run:
sudo rtl_433 -A<\/code> and then activate the doorbell.<\/p>\n\n\n\nIn my case, the output was as follows:<\/p>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/www.atombrake.info\/wp-content\/uploads\/2021\/04\/image-1.png?resize=525%2C545&ssl=1\")
Full output of doorbell signal<\/figcaption><\/figure>\n\n\n\n The important line is:<\/p>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/www.atombrake.info\/wp-content\/uploads\/2021\/04\/image-2.png?resize=525%2C19&ssl=1\")
Flex decoder specification<\/figcaption><\/figure>\n\n\n\n Save this line for later.<\/p>\n\n\n\n
Setting up Home Assistant & MQTT<\/h2>\n\n\n\n
It might be possible to do this by plugging the SDR into the device running Home Assistant, to simplify this step but I am running Home Assistant as a virtual machine running under Hyper-V which does not have USB pass-through.<\/p>\n\n\n\n
I’m not going to go through the full steps for setting up Home Assistant, as they are documented very well elsewhere.<\/p>\n\n\n\n
Once you have the basics setup, you’ll need to install the Mosquitto broker add-on through the supervisor menu, this allows home assistant to listen to MQTT messages on the network. You’ll then need to add the MQTT integration. If you are using the built in mosquitto broker, then the configuration of this is very simple. Finally you’ll need to create an account for MQTT logins. This doesn’t need to be an administrator, just a standard user.<\/p>\n\n\n\n
Putting it all together<\/h2>\n\n\n\n
I have configured a system service on my Pi so rtl_433 starts on boot, and restarts on failure. The service calls a single line script which is as follows:<\/p>\n\n\n\n
rtl_433 -R 0 -X ‘n=doorbell,m=OOK_PWM,s=352,l=692,r=5296,g=696,t=136,y=0’ -F “mqtt:\/\/<Home Assistant IP>:1883,user=<username>,pass=<password>”<\/p><\/blockquote>\n\n\n\n
Breaking this down:<\/p>\n\n\n\n
- -R 0 tells rtl_433 not to run any of the built in decoders<\/li>
- -X ‘n=doorbell,m=OOK_PWM,s=352,l=692,r=5296,g=696,t=136,y=0’ is the decoder captured in step 2 above. The n= can be anything.<\/li>
- -F “mqtt:\/\/<Home Assistant IP>:1883,user=<username>,pass=<password>” tells rtl_433 to output in MQTT format, and gives the details of where to send the message.<\/li><\/ul>\n\n\n\n
When running the command, you should see that it successfully makes an MQTT connection:<\/p>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/www.atombrake.info\/wp-content\/uploads\/2021\/04\/image-4.png?resize=525%2C106&ssl=1\")
MQTT connection established<\/figcaption><\/figure>\n\n\n\n Once this is running, head back to Home Assistant, to into the MQTT integration and click “configure”. This will allow you to run an MQTT listener.<\/p>\n\n\n\n
Initially start listening to all messages using the wildcard character #<\/p>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/www.atombrake.info\/wp-content\/uploads\/2021\/04\/image-3.png?resize=525%2C229&ssl=1\")
MQTT listener running<\/figcaption><\/figure>\n\n\n\n This will output all messages which should initially just be the connection details from the Pi into Home Assistant. Pressing the doorbell will generate additional traffic, including message codes. These message codes are unique and what we will monitor for in Home Assistant.<\/p>\n\n\n\n
We need to create a binary sensor in configuration.yaml:<\/p>\n\n\n\n
binary_sensor:\n## Doorbell\n - platform: mqtt\n state_topic: \"rtl_433\/raspberrypi\/devices\/doorbell\/codes\/#\"\n payload_on: \"{13}98e8\"\n off_delay: 5\n name: Doorbell<\/code><\/pre>\n\n\n\nThe bit which will need changing is the “payload on” code – this should be taken from the listener above.<\/p>\n\n\n\n
Once the file has been updated, save and restart Home Assistant. This will create a binary sensor which changes to “on” for 5 seconds when the doorbell is pressed.<\/p>\n\n\n\n
The next step is to use the sensor to generate alerts. I have setup two forms of alerts:<\/p>\n\n\n\n
- An alert on my Android phone (through the Home Assistant app)<\/li>
- Google homes playing a doorbell sound.<\/li><\/ol>\n\n\n\n
My automation looks like the following:<\/p>\n\n\n\n
alias: Doorbell\ndescription: ''\ntrigger:\n - platform: state\n entity_id: binary_sensor.doorbell\n to: 'on'\ncondition: []\naction:\n - service: media_player.volume_set\n target:\n device_id:\n - Google Home 1\n - Google Home 2\n data:\n volume_level: 0.75\n - service: media_player.play_media\n data:\n media_content_type: audio\/mp3\n media_content_id: 'URL of MP3'\n target:\n entity_id:\n - media_player.kitchen_speaker\n - media_player.office_speaker\n - service: notify.mobile_app_phone_name\n data:\n data:\n tag: doorbell\n ttl: 0\n priority: high\n message: Doorbell\n - wait_template: ''\n timeout: '00:00:10'\n continue_on_timeout: true\n - service: media_player.volume_set\n data:\n volume_level: 0.25\n target:\n device_id:\n - Google Home 1\n - Google Home 2\nmode: single\n<\/code><\/pre>\n\n\n\nBreaking this down, the trigger is the state of the sensor changing from ‘off’ to ‘on’<\/p>\n\n\n\n
The actions in order are:<\/p>\n\n\n\n
- Set the volume on my google home speakers to 75%<\/li>
- Play the MP3 stored at the URL provided<\/li>
- Pop up an android notification<\/li>
- Wait 10 seconds<\/li>
- Set google home speakers volume to 25%<\/li><\/ol>\n\n\n\n
Further Work \/ Improvements<\/h2>\n\n\n\n
There are a few areas where I think this setup could be improved:<\/p>\n\n\n\n
- rtl_433 is resource intensive on my Raspberry Pi, I have done some basic reading that there may be a better way to compile it in a more optimised way<\/li>
- The Google Home notification stops any music currently playing, and doesn’t restart it. I would prefer to play the notification and then resume whatever was playing in the background, at the previous volume.<\/li><\/ol>\n\n\n\n
Thanks for reading, I hope this has been useful! If you have any comments, suggestions for improvements to this setup please leave a comment below.<\/p>\n","protected":false},"excerpt":{"rendered":"
We have a pretty standard doorbell with a wireless chime, but living in a three floor house means the chime cannot be heard in all rooms. These doorbells usually run on 433MHz, which means we can use some cheap hardware to intercept the signals. In this project I have used a Raspberry Pi with a … <\/p>\n
- Once the OS is installed, you need to install rtl_433<\/a>. This is the software we will use to capture the signal, and then send it to Home Assistant via MQTT.<\/li>