{"id":3516,"date":"2018-12-31T14:00:05","date_gmt":"2018-12-31T22:00:05","guid":{"rendered":"http:\/\/192.168.3.4\/?p=3516"},"modified":"2018-12-31T13:36:07","modified_gmt":"2018-12-31T21:36:07","slug":"monitoring-wireless-sensors","status":"publish","type":"post","link":"https:\/\/www.cloudacm.com\/?p=3516","title":{"rendered":"Monitoring Wireless Sensors"},"content":{"rendered":"

In this post we’ll cover how to monitor inexpensive wireless security sensors. There are two types of wireless sensors that we’ll be working with, door reed switches and passive infra red motion detectors. Each of these sensors transmit a broadcast radio message on the 433Mhz frequency. We’ll be expanding on earlier work with RTL_433. This post will cover how to identify a specific sensor and take appropriate action as needed, all that with a single bash script, let’s begin.<\/p>\n

\"\"<\/a><\/p>\n

The first thing will be the command to run the RTL_433 command. The path to the command is included in the bash script. CRON might be able to know the path, but it’s better to include it just in case. If the path isn’t known, type “whereis ” in a terminal window and it will display the path. RTL_433 will only need to monitor protocol 86 (“Wireless Smoke and Heat Detector GS 558”). The sensors we’ll be working with use this protocol exclusively, so we don’t need to bother detecting other devices. The output of the results will be formated in JSON, which contains all of the data on a single line. This will make it easier to parse and process the results. Since RTL_433 will be running in a loop condition, we want to interrupt it when a device is detected. Here is the command we’ll be using.<\/command><\/p>\n

\/usr\/local\/bin\/rtl_433 -R 86 -F json:\"$JsonOutput\" -E<\/pre>\n
Since the above command is saving its output to a variable, we will define all of the variables at the beginning of the script.<\/p>\n
DoorSensorEmail=\"\/home\/local\/Tasks\/DoorSensorEmail.txt\"\nJsonOutput=\"\/home\/local\/Tasks\/A_JsonOutput.txt\"\nMessage=\"\/home\/local\/Tasks\/A_Message.txt\"\nMessageOutside=\"\/home\/local\/Tasks\/A_MessageOutside.txt\"\n\nPIRCounter=\"\/home\/local\/Tasks\/BasementPIRCounter.txt\"\nCounter=$(cat \"$PIRCounter\")\n\nCactiHost='cacti.host.local'\nMate1FTPUser=''\nMate1FTPPass=''<\/pre>\n
This script will be called from CRON on bootup. I like to add a 2 minute delay before staring the rest of the script. This is done with this command.<\/p>\n
sleep 120<\/pre>\n
After this period of time, the variables will be loaded into memory and our main loop function will begin by starting RTL_433. It will continue running RTL_433 until one of a sensor transmits. When data is decoded by RTL_433, that process will end and we will enter into a series of if else conditions.<\/p>\n
The first condition will check if the JSON output contains the identifier for a door sensor. If it doesn’t, it will continue on with the next check of another identifier and so on. However, if the JSON output does contain the identifier then a series of commands will execute.<\/p>\n
# Door Sensor ID = #####\nif grep -q ##### \"$JsonOutput\" ; then\n  echo \"Door Sensor Tripped\" > $Message\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  cat \"$JsonOutput\" | \/usr\/bin\/logger -n syslog.host.local\n  rm \"$JsonOutput\"\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  \/usr\/sbin\/ssmtp admin@email.local < \"$DoorSensorEmail\" >\/dev\/null 2>&1<\/pre>\n
The above if condition will log the results to a syslog server named “syslog.host.local”. It then removes the JSON file for housekeeping. Finally, it sends an email notifying admin@email.local with a pre-formatted email message. Certain sensors merit immediate attention, while others can simply be logged to the syslog server.<\/p>\n
In the next if condition, we’ll log the JSON result to our syslog server. In addition to that, we’ll also tally a counter of the occurrence of the event. This value will then be uploaded to a FTP host that runs Cacti. I won’t cover the configuration of Cacti here, see earlier posts for that. If you have a number, Cacti will graph it.<\/p>\n
\"\"<\/a><\/p>\n
# PIR Sensor ID = #####\nelif grep -q ##### \"$JsonOutput\" ; then\n  echo \"PIR Tripped\" > $Message\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  cat \"$JsonOutput\" | \/usr\/bin\/logger -n syslog.host.local\n  Counter=$((Counter+1))\n  echo \"$Counter\" > \"$PIRCounter\"\n\n  echo \"\n  verbose\n  open $CactiHost\n  user $Mate1FTPUser $Mate1FTPPass\n  cd Tasks\n  bin\n  put \"$PIRCounter\"\n  bye\n  \" | ftp -n \n\n  rm \"$JsonOutput\"<\/pre>\n
The last condition we’ll check is a catch all. If none of our devices were found in earlier conditions, then some unknown device transmitted data. This condition will take action based on that. Since I covered email, syslog, and cacti, we could use any or all of these in this catch all condition. At the conclusion of this, we return to the start of our loop and run the RTL_433 command again.<\/p>\n
Using a single bash script and some inexpensive hardware, we can monitor security sensors and take action based on their activity. Here is the complete code for the script, names have been changed to protect the innocent.<\/p>\n
#!\/bin\/sh\n# \/home\/local\/Tasks\/DoorSensor.sh\n# Version 6.0 (12312018)\n# Purpose - Run SDR scan of Door and PIR Sensors, log readings to Syslog \/ Cacti, and send email alert\n# Author - Patrick Gilfeather - CloudACM\n\n\n# Delay the start of the script for 2 minutes so system has time to boot\nsleep 120\n\n# Set variables for work files\nDoorSensorEmail=\"\/home\/local\/Tasks\/DoorSensorEmail.txt\"\nJsonOutput=\"\/home\/local\/Tasks\/A_JsonOutput.txt\"\nMessage=\"\/home\/local\/Tasks\/A_Message.txt\"\nMessageOutside=\"\/home\/local\/Tasks\/A_MessageOutside.txt\"\n\nPIRCounter=\"\/home\/local\/Tasks\/BasementPIRCounter.txt\"\nCounter=$(cat \"$PIRCounter\")\n\nCactiHost='**********'\nMate1FTPUser='**********'\nMate1FTPPass='**********'\n\n\n# Run the process in a loop endlessly\nwhile :\ndo\n\n# Run RTL_433 process to detect door sensor with SDR and capture results to a JSON formatted file.\n# Process paths need to be included for CRON, use whereis \"command\" to find path.\n\/usr\/local\/bin\/rtl_433 -R 86 -F json:\"$JsonOutput\" -E \n\n# Door Sensor ID = **********\nif grep -q ********** \"$JsonOutput\" ; then\n  echo \"********** Sensor Tripped\" > $Message\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  cat \"$JsonOutput\" | \/usr\/bin\/logger -n **********\n  rm \"$JsonOutput\"\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  \/usr\/sbin\/ssmtp ********** < \"$DoorSensorEmail\" >\/dev\/null 2>&1\n\n# Door Sensor ID = **********\nelif grep -q ********** \"$JsonOutput\" ; then\n  echo \"********** Sensor Tripped\" > $Message\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  cat \"$JsonOutput\" | \/usr\/bin\/logger -n **********\n  rm \"$JsonOutput\"\n\n# PIR Sensor ID = **********\nelif grep -q ********** \"$JsonOutput\" ; then\n  echo \"********** Sensor Tripped\" > $Message\n  # Process paths need to be included for CRON, use whereis \"command\" to find path.\n  cat \"$JsonOutput\" | \/usr\/bin\/logger -n **********\n  Counter=$((Counter+1))\n  echo \"$Counter\" > \"$PIRCounter\"\n\n  echo \"\n  verbose\n  open $CactiHost\n  user $Mate1FTPUser $Mate1FTPPass\n  cd Tasks\n  bin\n  put \"$PIRCounter\"\n  bye\n  \" | ftp -n \n\n  rm \"$JsonOutput\"\n\n# Undefined Sensor\nelse\n  echo \"Foreign Sensor Tripped\" >> $MessageOutside\n  rm \"$JsonOutput\"\nfi\n\ndone\n\nexit<\/pre>\n","protected":false},"excerpt":{"rendered":"
In this post we’ll cover how to monitor inexpensive wireless security sensors. There are two types of wireless sensors that we’ll be working with, door reed switches and passive infra red motion detectors. Each of these sensors transmit a broadcast radio message on the 433Mhz frequency. We’ll be expanding on earlier work with RTL_433. This post will cover how to identify a specific sensor and take appropriate action as needed, all that with a single bash script, let’s begin. The…<\/p>\n
 Read More  Read More<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-3516","post","type-post","status-publish","format-standard","hentry","category-rd"],"_links":{"self":[{"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/posts\/3516","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3516"}],"version-history":[{"count":2,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/posts\/3516\/revisions"}],"predecessor-version":[{"id":3520,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=\/wp\/v2\/posts\/3516\/revisions\/3520"}],"wp:attachment":[{"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3516"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3516"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cloudacm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3516"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}