{`FHEM IPCAM Module for INSTAR Cameras`}
\n {/* TOC */}\n- \n
- {`FHEM Installation`} \n
- {`Make FHEM look Pretty(ier)`} \n
- {`The IPCAM Module`}\n \n \n
- {`Adding your Cameras Live Video`} \n
- {`Tablet UI`} \n
- {`Automate Camera Functions`}\n \n \n
- {`Motion Detection and Notification`}\n \n \n
- {`MQTT Integration`}\n \n \n
{`This is an overview over the FHEM user interface. We are going to install the house automation system in `}{`Raspbian`}{` on a Raspberry Pi 2 - if you are using a different operating system, please take a look at the official `}{`installation guide`}{`.`}
\n{`FHEM Installation`}
\n- \n
- \n
{`Import the repository gpg key: `}
\n{`sudo wget http://debian.fhem.de/archive.key | apt-key add -`}\n - \n
{`Add the repository to `}
\n{`sudo nano /etc/apt/sources.list`}{`: `}{`deb http://debian.fhem.de/nightly/ /`}\n - \n
{`Update your package manager: `}
\n{`sudo apt-get update`}\n - \n
{`Install fhem: `}
\n{`sudo apt-get install fhem`}\n - \n
{`Access the web user interface over the IP of your FHEM server - e.g. `}{`192.168.2.64`}{` : `}
\n{`http://192.168.2.64:8083/fhem`}\n
{`Make FHEM look Pretty(ier)`}
\n{`The FHEM UI does not look so good. Fortunately, it is fully customizable - you can even download ready-to-use themes like the `}{`haus-automatisierung.com`}{` skin, that I modified slightly for this tutorial. Skins don't change the button layout of the user interface and everything is purely cosmetic - so there is no need to install it. But if you want to follow along, download the either the `}{`original skin`}{` or the `}{`INSTAR modified version`}{`:`}
\n- \n
- {`Copy the content of the `}
{`www`}{` directory from the is repository to the `}{`www`}{` directory inside your FHEM installation `}{`/opt/fhem/www/`}{`.`} \n - {`Access your FHEM user interface, click on `}{`Unsorted`}{` and select the `}{`FHEMWEB`}{` / Web device:`} \n
{`\n `}{`\n `}{`\n `}{`\n `}
- \n
- {`Select the `}
{`stylesheetPrefix Attribute`}{` and type in `}{`instar_theme`}{` (or `}{`hausautomatisierung_com`}{`) and confirm. Reload the website to see the result:`} \n
{`\n `}{`\n `}{`) and gave it the name `}{`OfficeCam`}
{`define OfficeCam IPCAM `}{`192.168`}{`.2.116:80`}{`We can refer to the `}{`Command Reference`}{` for available attributes that we can assign to our camera.`}
\n{`To access our camera we can create a credentials file `}{`ipcams.conf`}{` located in `}{`/opt/fhem/credentials`}{` (make sure to `}{`sudo chown fhem:dialout`}{` and `}{`sudo chmod 664`}{` the folder and the config file !):`}
{`$credentials`}{`{`}{`OfficeCam`}{`}`}{`{`}{`username`}{`}`}{` `}{`=`}{` `}{`\"admin\"`}{`;`}{`\n`}{`$credentials`}{`{`}{`OfficeCam`}{`}`}{`{`}{`password`}{`}`}{` `}{`=`}{` `}{`\"instar\"`}{`;`}{`In this example we have an administrator account with the login admin/instar on our camera - please change these values according to your camera setup. In the following steps we now don't have to use the login anymore. We will just have to reference the credentials file.`}
\n{`\n `}{`\n `}{`\n `}{`\n `}
{`Camera Control`}
\n{`Now with everything set up we can start using the IPCAM Module. The first thing we can add is a collection of up to 15 `}{`CGI commands`}{` that help us to take control over the camera functions through the FHEM web interface and allow us to later set up time schedules or event listeners to automatically trigger a certain command and automate our camera. For this example, we picked the following commands (`}{`you can, of course, replace every one of them - check out our`}{` `}{`CGI documentation for all VGA, HD and Full HD cameras`}{`):`}
\n| {`Command`} | \n{`Function`} | \n
|---|---|
| {`cmd01`} | \n{`Trigger an Alarm on our camera`} | \n
| {`cmd02`} | \n{`Set IR LEDs to automatic`} | \n
| {`cmd03`} | \n{`Deactivate IR LEDs`} | \n
| {`cmd04`} | \n{`Disable all Detection Areas + internal PIR Sensor`} | \n
| {`cmd05`} | \n{`Enable all Detection Areas + internal PIR Sensor`} | \n
| {`cmd06`} | \n{`Go to stored position 1`} | \n
| {`cmd07`} | \n{`Go to stored position 2`} | \n
| {`cmd08`} | \n{`Go to stored position 3`} | \n
| {`cmd09`} | \n{`Start horizontal scan`} | \n
| {`cmd10`} | \n{`Deactivate Alarm Schedule`} | \n
| {`cmd11`} | \n{`Activate Alarm Schedule`} | \n
| {`cmd12`} | \n{`Activate Alarm Area 1 & 2`} | \n
| {`cmd13`} | \n{`Deactivate Alarm Area 1 & 2`} | \n
| {`cmd14`} | \n{`Activate Alarm Area 3 & 4`} | \n
| {`cmd15`} | \n{`Deactivate Alarm Area 3 & 4`} | \n
{`You can copy and paste the following commands into the FHEM command line. Please change the name `}{`OfficeCam`}{` if you have chosen a different name for your camera in the step above:`}
{`attr OfficeCam basicauth `}{`{`}{`USERNAME`}{`}`}{`:`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam credentials /opt/fhem/credentials/ipcams.conf\nattr OfficeCam pathCmd param.cgi?\nattr OfficeCam cmd01 `}{`cmd`}{`=`}{`pushhostalarm`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd02 `}{`cmd`}{`=`}{`setinfrared`}{`&`}{`-infraredstat`}{`=`}{`auto`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd03 `}{`cmd`}{`=`}{`setinfrared`}{`&`}{`-infraredstat`}{`=`}{`close`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd04 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`1`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`2`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`3`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`4`}{`&`}{`-enable`}{`=`}{`0`}{`?cmd`}{`=`}{`setpirattr`}{`&`}{`-pir_enable`}{`=`}{`0`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd05 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`1`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`2`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`3`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`4`}{`&`}{`-enable`}{`=`}{`1`}{`?cmd`}{`=`}{`setpirattr`}{`&`}{`-pir_enable`}{`=`}{`1`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd06 `}{`cmd`}{`=`}{`preset`}{`&`}{`-act`}{`=`}{`goto`}{`&`}{`-number`}{`=`}{`0`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd07 `}{`cmd`}{`=`}{`preset`}{`&`}{`-act`}{`=`}{`goto`}{`&`}{`-number`}{`=`}{`1`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd08 `}{`cmd`}{`=`}{`preset`}{`&`}{`-act`}{`=`}{`goto`}{`&`}{`-number`}{`=`}{`2`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd09 `}{`cmd`}{`=`}{`ptzctrl`}{`&`}{`-step`}{`=`}{`0`}{`&`}{`-act`}{`=`}{`hscan`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd10 `}{`cmd`}{`=`}{`setscheduleex`}{`&`}{`-ename`}{`=`}{`md`}{`&`}{`-week0`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week1`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week2`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week3`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week4`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week5`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-week6`}{`=`}{`NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd11 `}{`cmd`}{`=`}{`setscheduleex`}{`&`}{`-ename`}{`=`}{`md`}{`&`}{`-week0`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week1`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week2`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week3`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week4`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week5`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-week6`}{`=`}{`PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd12 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`1`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`2`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd13 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`1`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`2`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd14 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`3`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`4`}{`&`}{`-enable`}{`=`}{`1`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\nattr OfficeCam cmd15 `}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`3`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`cmd`}{`=`}{`setmdattr`}{`&`}{`-name`}{`=`}{`4`}{`&`}{`-enable`}{`=`}{`0`}{`&`}{`-usr`}{`=`}{`{`}{`USERNAME`}{`}`}{`&`}{`-pwd`}{`=`}{`{`}{`PASSWORD`}{`}`}{`\n `}{`\n `}{`\n `}{`\n `}
{`We will come back to our command list when we start setting up the `}{`FHEM Tablet UI`}{` below.`}
\n{`Timed snapshots`}
\n{`The IPCAM module also allows us to record a number snapshots in an adjustable interval (photo series). Those snapshots will always have the same file name and be overwritten once a new recording is triggered. This is a useful function to embed an always up-to-date screenshot of a location inside a website.`}
\n{`The following commands will point FHEM to the snapshot URL on our camera `}{`tmpfs/snap.jpg`}{`, limit the amount of snapshots to 1 and set a path on our LINUX host system where we want to files to be stored `}{`/opt/fhem/www/snapshots`}{` (`}{`make sure to `}{`sudo chown fhem:dialout`}{` and `}{`sudo chmod 664`}{` the folder to allow FHEM to use it after you created it with `}{`sudo mkdir /opt/fhem/www/snapshots`}{`):`}
{`attr OfficeCam path tmpfs/snap.jpg\nattr OfficeCam snapshots `}{`1`}{`\nattr OfficeCam storage /opt/fhem/www/snapshots\nattr OfficeCam event-on-update-reading snapshots\nattr OfficeCam `}{`alias`}{` IN-8015 Full HD\nattr OfficeCam group Surveillance\nattr OfficeCam icon it_camera\nattr OfficeCam room Office\nattr OfficeCam verbose `}{`5`}{`\n `}{`\n `}{`\n `}{`\n `}
{`The attribute `}{`snapshot`}{` defines the number of snapshots that should be taken (we choose `}{`1`}{`) when our IPCAM device is triggered by an event. If you choose more than 1 snapshot, you can also define a `}{`attr OfficeCam delay 10`}{` in seconds between each shot. We also set the storage path on our Raspberry Pi to `}{`/opt/fhem/www/snapshots`}{` (make sure that directory exist and can be written to by the FHEM user) and told the IPCAM module that those snapshots can be found under `}{`tmpfs/snap.jpg`}{` - the 1080p snapshot path of every INSTAR HD and Full HD camera.`}
{`Note:`}{` In most cases it won't be necessary to load the 1920x1080 pixel image - that is why your INSTAR Full HD camera offers 3 resolutions that you can pick from:`}
\n- \n
{`/tmpfs/snap.jpg?usr=admin&pwd=instar`}{` Snapshot (1080p)`} \n {`/tmpfs/auto.jpg?usr=admin&pwd=instar`}{` Snapshot (320p)`} \n {`/tmpfs/auto2.jpg?usr=admin&pwd=instar`}{` Snapshot (160p)`} \n
{`To be able to access those snapshots we can use the integrated webserver inside FHEM called HTTPSRV and tell it to serve the content of the storage directory `}{`define {`:`}
- \n
{`name`}{` is a custom name for the device used by the FHEM UI.`} \n {`infix`}{` a prefix for the FHEMWEB-Base-URL under which the content of the directory will be served.`} \n {`directory`}{` the absolute path to the public directory on your RaspPi.`} \n {`friendlyname`}{` the name that is used in the FHEM side navigation.`} \n
{`define SnapServer HTTPSRV snaps /opt/fhem/www/snapshots OfficeCam-Snapshots`}{`\n `}{`\n `}{`\n `}{`\n `}
{`The timelapse job should now trigger the IPCAM module every minute, which will then upload images to our storage path on the RaspberryPi. Via the HTTPSRV module we are now able to load the latest snapshot with the following URL: `}{`http://192.168.2.64:8083/fhem/snaps/OfficeCam_snapshot.jpg`}{`.`}
{`\n `}{`\n `}{`\n `}{`\n `}
{`This image can be embedded inside a website. You can `}{`download this HTML code`}{` and unzip it to `}{`/opt/fhem/www/snapshots`}{` as an example. This page will be hosted under `}{`http://192.168.2.64:8083/fhem/snaps`}{` and show you the latest snapshot inside a jQuery lightbox:`}
{`Adding your Cameras Live Video`}
\n{`You can use the `}{`IFRAME`}{` module to add the cameras live video:`}
\n{`define OfficeCamView weblink iframe http://192.168.2.116:80/mjpegstream.cgi?-chn`}{`=`}{`12`}{`&`}{`-usr`}{`=`}{`admin`}{`&`}{`-pwd`}{`=`}{`instar\nattr OfficeCamView htmlattr `}{`width`}{`=`}{`\"640\"`}{` `}{`height`}{`=`}{`\"352\"`}{` `}{`frameborder`}{`=`}{`\"0\"`}{` `}{`marginheight`}{`=`}{`\"0\"`}{` `}{`marginwidth`}{`=`}{`\"0\"`}{`\nattr OfficeCamView group Surveillance\nattr OfficeCamView room Office\nattr OfficeCamView verbose `}{`5`}{`Just as it was the case with the snapshots, you can pick for 3 different resolutions for the live video stream - just substitute the channel number in the MJPEG path above:`}
\n- \n
{`/mjpegstream.cgi?-chn=11`}{` (1080p)`} \n {`/mjpegstream.cgi?-chn=12`}{` (320p)`} \n {`/mjpegstream.cgi?-chn=13`}{` (160p)`} \n
\n\n{`To edit this view once added, use the following URL `}
\n{`http://192.168.2.64:8083/fhem?detail=OfficeCamView`}{` where you have to replace the `}{`OfficeCamView`}{` with the name you choose in the commands above.`}
{`\n `}{`\n `}{`\n `}{`\n `}
{`Tablet UI`}
\n{`FHEM Tablet UI`}{` is a lightweight but feature-rich front-end framework for controlling and monitoring FHEM-integrated devices. It is based on HTML / CSS / JavaScript.`}
\n- \n
- {`First, all files from FHEM Tablet UI must be copied to the FHEM directory `}
{`/opt/fhem/www`}{`. This is done with the following update command via the FHEM command line:`} \n
{`update all https://raw.githubusercontent.com/knowthelist/fhem-tablet-ui/master/controls_fhemtabletui.txt`}{`\n `}{`\n `}{`\n `}{`\n `}
{`\n `}{`\n `}{`\n `}{`\n `}
- \n
- {`Then create a new `}{`HTTPSRV-Device`}{` in FHEM, which points to the folder with the files just downloaded.`} \n
{`define TABLETUI HTTPSRV ftui/ ./www/tablet/ Tablet-UI`}{`\n `}{`\n `}{`\n `}{`\n `}
- \n
- {`So that FHEM Tablet UI can communicate with FHEM, the longpoll setting in the FHEMWEB device has to be defined.`} \n
{`attr WEB longpoll websocket`}{`\n `}{`\n `}{`\n `}{`\n `}
- \n
- {`Finally, FHEM has to be restarted (`}
{`shutdown restart`}{`) because the attribute longpoll has been changed.`} \n
{`FHEM Tablet UI is now ready for use and can be accessed through the URL `}{`http://{` or open the link in the FHEM menu:`}
{`\n `}{`\n `}{`\n `}{`\n `}
{`We can now start with creating our own UI by first making a backup of the HTML file:`}
\n{`sudo`}{` `}{`cp`}{` /opt/fhem/www/tablet/index.html /opt/fhem/www/tablet/index-bak.html`}{`We can then delete all the example widgets from the original `}{`index.html`}{` file:`}
\n{`{`DOCTYPE`}{` `}{`html`}{`>`}{`\n`}{`<`}{`html`}{`>`}{`\n\n`}{`<`}{`head`}{`>`}{`\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`icon`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`favicon.ico`}{`\"`}{` `}{`type`}{`=`}{`\"`}{`image/x-icon`}{`\"`}{` `}{`/>`}{`\n\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`viewport`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no`}{`\"`}{` `}{`/>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`widget_base_width`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`116`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`widget_base_height`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`131`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`mobile-web-app-capable`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`yes`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`apple-mobile-web-app-capable`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`yes`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`http-equiv`}{`=`}{`\"`}{`X-UA-Compatible`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`IE=edge`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`longpoll`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`1`}{`\"`}{`>`}{`\n `}{`<`}{`meta`}{` `}{`name`}{`=`}{`\"`}{`debug`}{`\"`}{` `}{`content`}{`=`}{`\"`}{`0`}{`\"`}{`>`}{`\n\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`stylesheet`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`/fhem/tablet/lib/jquery.gridster.min.css`}{`\"`}{` `}{`/>`}{`\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`stylesheet`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`/fhem/tablet/css/fhem-tablet-ui.css`}{`\"`}{` `}{`/>`}{`\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`stylesheet`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`/fhem/tablet/lib/font-awesome.min.css`}{`\"`}{` `}{`/>`}{`\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`stylesheet`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`/fhem/tablet/lib/jquery.toast.min.css`}{`\"`}{` `}{`/>`}{`\n `}{`<`}{`link`}{` `}{`rel`}{`=`}{`\"`}{`stylesheet`}{`\"`}{` `}{`href`}{`=`}{`\"`}{`/fhem/tablet/css/fhem-tablet-ui-user.css`}{`\"`}{` `}{`/>`}{`\n\n `}{`<`}{`script`}{` `}{`src`}{`=`}{`\"`}{`js/fhem-tablet-ui.js`}{`\"`}{` `}{`defer`}{`>`}{`{`script`}{`>`}{`\n\n `}{`<`}{`title`}{`>`}{`FHEM-Tablet-UI`}{`{`title`}{`>`}{`\n`}{`{`head`}{`>`}{`\n\n`}{`<`}{`body`}{`>`}{`\n\n `}{`<`}{`div`}{` `}{`class`}{`=`}{`\"`}{`gridster`}{`\"`}{`>`}{`\n `}{`<`}{`ul`}{`>`}{`\n `}{`<`}{`li`}{` `}{`data-row`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-col`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-sizey`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-sizex`}{`=`}{`\"`}{`1`}{`\"`}{`>`}{`\n `}{``}{`\n `}{`{`li`}{`>`}{`\n `}{`{`ul`}{`>`}{`\n `}{`{`div`}{`>`}{`\n`}{`{`body`}{`>`}{`\n\n`}{`{`html`}{`>`}{`This reduced our user interface to an empty canvas that we can now start to populate with our own widgets:`}
\n{`\n `}{`\n `}{`\n `}{`\n `}
{`We can start with a widget that displays our cameras medium (`}{`/12`}{`) live video constantly and gives us a lightbox view of the Full HD stream (`}{`11`}{`) when we click on it:`}
{`<`}{`li`}{` `}{`data-row`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-col`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-sizey`}{`=`}{`\"`}{`2`}{`\"`}{` `}{`data-sizex`}{`=`}{`\"`}{`4`}{`\"`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`popup`}{`\"`}{` `}{`data-height`}{`=`}{`\"`}{`560px`}{`\"`}{` `}{`data-width`}{`=`}{`\"`}{`960px`}{`\"`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`image`}{`\"`}{`\n `}{`data-url`}{`=`}{`\"`}{`http://192.168.2.116:80/mjpegstream.cgi?-chn=12&-usr=admin&-pwd=instar`}{`\"`}{` `}{`width`}{`=`}{`\"`}{`100%`}{`\"`}{`\n `}{`height`}{`=`}{`\"`}{`100%`}{`\"`}{` `}{`class`}{`=`}{`\"`}{`nocache`}{`\"`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`<`}{`div`}{` `}{`class`}{`=`}{`\"`}{`dialog`}{`\"`}{`>`}{`\n `}{`<`}{`header`}{`>`}{`IN-8015 Full HD`}{`{`header`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`image`}{`\"`}{`\n `}{`data-url`}{`=`}{`\"`}{`http://192.168.2.116:80/mjpegstream.cgi?-chn=11&-usr=admin&-pwd=instar`}{`\"`}{`\n `}{`width`}{`=`}{`\"`}{`100%`}{`\"`}{` `}{`height`}{`=`}{`\"`}{`100%`}{`\"`}{` `}{`class`}{`=`}{`\"`}{`nocache`}{`\"`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`{`div`}{`>`}{`\n`}{`{`li`}{`>`}{`If we keep the Table UI open over long periods of time, it might be better to hide the live video unless we click on the widget to save valuable network bandwidth:`}
\n{`<`}{`li`}{` `}{`data-row`}{`=`}{`\"`}{`3`}{`\"`}{` `}{`data-col`}{`=`}{`\"`}{`4`}{`\"`}{` `}{`data-sizex`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-sizey`}{`=`}{`\"`}{`1`}{`\"`}{`>`}{`\n `}{`<`}{`header`}{`>`}{`IN-9008 Full HD`}{`{`header`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`popup`}{`\"`}{` `}{`data-height`}{`=`}{`\"`}{`545px`}{`\"`}{` `}{`data-width`}{`=`}{`\"`}{`960px`}{`\"`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`button`}{`\"`}{` `}{`data-get`}{`=`}{`\"`}{`STATE`}{`\"`}{` `}{`data-icon`}{`=`}{`\"`}{`fa-video-camera`}{`\"`}{` `}{`data-get-on`}{`=`}{`\"`}{`on`}{`\"`}{`\n `}{`class`}{`=`}{`\"`}{`big top-space`}{`\"`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`<`}{`div`}{` `}{`class`}{`=`}{`\"`}{`dialog`}{`\"`}{`>`}{`\n `}{`<`}{`header`}{`>`}{`IN-9008 Full HD`}{`{`header`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`image`}{`\"`}{`\n `}{`data-url`}{`=`}{`\"`}{`http://192.168.2.115:80/mjpegstream.cgi?-chn=12&-usr=admin&-pwd=instar`}{`\"`}{`\n `}{`data-size`}{`=`}{`\"`}{`100%`}{`\"`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`{`div`}{`>`}{`\n `}{`{`div`}{`>`}{`\n`}{`{`li`}{`>`}{`We can also add all the CGI functions we `}{`added to our IPCAM device`}{` earlier. The following will create a push button with the `}{`Material UI Icon`}{` `}{`looks_one`}{`. When pressed the button will emit a trigger for the `}{`cmd6`}{` for our `}{`OfficeCam`}{`. We used two `}{`CSS Classes`}{` to get a big icon that has a little margin to the top of the button:`}
{`<`}{`li`}{` `}{`data-row`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-col`}{`=`}{`\"`}{`3`}{`\"`}{` `}{`data-sizey`}{`=`}{`\"`}{`1`}{`\"`}{` `}{`data-sizex`}{`=`}{`\"`}{`1`}{`\"`}{`>`}{`\n `}{`<`}{`Header`}{`>`}{`Go to Pos 1`}{`{`header`}{`>`}{`\n `}{`<`}{`div`}{`>`}{`\n `}{`<`}{`div`}{` `}{`data-type`}{`=`}{`\"`}{`push`}{`\"`}{` `}{`data-icon`}{`=`}{`\"`}{`mi-looks_one`}{`\"`}{` `}{`data-device`}{`=`}{`\"`}{`OfficeCam`}{`\"`}{` `}{`data-set-on`}{`=`}{`\"`}{`cmd06`}{`\"`}{` `}{`class`}{`=`}{`\"`}{`big top-space`}{`\"`}{`>`}{`{`div`}{`>`}{`\n `}{`{`div`}{`>`}{`\n`}{`{`li`}{`>`}{`The complete file for all our function buttons `}{`can be copied from here`}{` to `}{`/opt/fhem/www/tablet/index.html`}{` and your Tablet-UI under `}{`http://{` should now look something like this:`}
{`Automate Camera Functions`}
\n{`FHEM offers a scheduler (`}{`automation timer`}{`) `}{`at`}{` that enables us to set up a time controlled triggers for those camera `}{`commands we set up earlier`}{`. The command structure for the scheduler is:`}
{`define `}{`<`}{`name`}{`>`}{` at `}{`<`}{`timespec`}{`>`}{` `}{`<`}{`command`}{`>`}{`\\\\
{`Variants of time specifications for `}{`at`}{`:`}
| {`Notation`} | \n{`Explanation`} | \n
|---|---|
| {`+00:02:00`} | \n{`In two minutes; single execution`} | \n
| {`00:02:00`} | \n{`At two minutes past midnight, i.e. at 00:02 and 0 seconds; one-time execution`} | \n
| {`*00:02:00`} | \n{`Daily at 00:02`} | \n
| {`+*00:02:00`} | \n{`Every 2 minutes`} | \n
| {`+*{3}00:02`} | \n{`Three times, every two minutes`} | \n
| {`*{3}00:02`} | \n{`Three times at 00:02`} | \n
| {`*{sunset_rel()}`} | \n{`Daily at sunset`} | \n
| {`*{sunrise(+120)}`} | \n{`2 minutes (120 seconds) daily after sunrise`} | \n
- \n
- {`By specifying * a permanent repetition is defined. The repetitions continue until the at is deleted or disabled.`} \n
- {`By specifying + the specified time is no longer interpreted as an absolute time, but as a timer, after how many hours:minutes:seconds the command is executed.`} \n
- {`By specifying {n} the at will only be run n times.`} \n
- {`The functions {sunset_rel()} and {sunrise()} return the appropriate time. This is repeated daily by specifying *. The curly braces indicate that FHEM directly executes the contents of these braces as perl functions.`} \n
{`For example, to pan our camera into the position we want to keep an eye on during the day, we can trigger the `}{`cmd 6`}{`, that `}{`we created to let our camera move to stored position 1`}{` every morning at sunrise. And then at sunset we want to move back to the night position with `}{`cmd 8`}{`:`}
{`define go_to_day_position at *`}{`{`}{`sunrise`}{`(`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`6`}{`\ndefine go_to_night_position at *`}{`{`}{`sunset_rel`}{`(`}{`)`}{`}`}{` `}{`set`}{` `}{`set`}{` OfficeCam cmd `}{`8`}{`Since we now automatically move our camera, we possibly also need to change the alarm areas that the motion detection is using. During the day we want to use the small detection areas 1&2 with a high sensitivity. But during the night we need `}{`increase the size of our areas and also decrease the sensitivity`}{`, because the detection is more sensitive in night vision mode and we want to reduce false alerts - so we will switch to area 3&4 that are set up accordingly. For good measures we also automate the IR nightvision by switching it from automatic to off during the day. Due to our camera position we might need to adjust the timing a little bit - 10 minutes (600s) after sunset and 20min after sunrise seems to be a good value (adjust this to your needs):`}
\n{`define enable_are_one_two at *`}{`{`}{`sunrise`}{`(`}{`+10`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`12`}{`\ndefine disable_are_three_four at *`}{`{`}{`sunrise`}{`(`}{`+15`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`15`}{`\ndefine disable_nightvision at *`}{`{`}{`sunrise`}{`(`}{`+1200`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`3`}{`\n\ndefine disable_are_one_two at *`}{`{`}{`sunset_rel`}{`(`}{`+10`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`13`}{`\ndefine enable_are_three_four at *`}{`{`}{`sunset_rel`}{`(`}{`+15`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`14`}{`\ndefine enable_nightvision at *`}{`{`}{`sunset_rel`}{`(`}{`+600`}{`)`}{`}`}{` `}{`set`}{` OfficeCam cmd `}{`2`}{`We are also adding small delays to the two area commands, so that not all commands are triggered at the same time and might get dropped by the camera.`}
\n{`\n `}{`\n `}{`\n `}{`\n `}
{`For event driven automation please check the `}{`official documentation`}{`. An example would be to start a photo series recording when the motion detection was triggered in FHEM.`}
\n{`Adding your Geo Location`}
\n{`If you haven't done so before, you will have to add your latitude and longitude to FHEM for it to be able to calculate your sunset and sunrise times. You can use `}{`Google Maps`}{` to find out your geo location by right-clicking the map and choosing `}{`What is here?`}{`. Your Longitude and Latitude will be displayed at the bottom of the screen:`}
\n{`\n `}{`\n `}{`\n `}{`\n `}
{`Open the FHEM configuration file `}{`nano /opt/fhem/fhem.cfg`}{` or from the FHEM interface under `}{`Edit files`}{`:`}
{`\n `}{`\n `}{`\n `}{`\n `}
{`And add your Longitude and Latitude as a global attribute:`}
\n{`attr global latitude 50.274297\nattr global longitude 8.189495`}{`\n `}{`\n `}{`\n `}{`\n `}
{`You might have been asked to choose between a `}{`standalone server mode`}{` or `}{`from inetd`}{` during the installation - choose the standalone mode. To configure `}{`ProFTPD`}{` manually open the configuration file in Nano:`}
\n{`sudo`}{` `}{`nano`}{` /etc/proftpd/proftpd.conf`}{`We are deactivating IPv6 - that we don't need, renaming our server to FHEM and making sure that the `}{`standalone server type`}{` is active.`}
\n{`\n `}{`\n `}{`<`}{`Global`}{`>`}{`\n RequireValidShell off\n`}{`{`Global`}{`>`}{`\n \n# Default directory is ftpusers home\nDefaultRoot ~ ftpuser\n \n# Limit login to the ftpuser group\n`}{`<`}{`Limit`}{` `}{`LOGIN`}{`>`}{`\n DenyGroup !ftpuser\n`}{`{`Limit`}{`>`}\n {`\n `}{`\n `}{`\n `} {`In this example I have chosen the UNIX password to be `} {`Now with everything set we just have to restart the FTP service:`} {`We can use our browser to test that the FTP server is running by accessing the IP address of our Raspberry Pi prefixed by an `}{`ftp://`}{`: `} {`\n `}{`\n `}{`\n `} {`You should now be able to login with `}{`username = ftpuser`}{` and `}{`password = instar`}{` - of course we only see an empty directory here for now.`} {`Right now only the `} {`\n `}{`\n `}{`\n `} {`We can change the rights recursively for the directory with the following command:`} {`\n `}{`\n `}{`rw-`} {`We can now create a folder that we want to use as upload folder for our office camera:`} {`\n `}{`\n `}{`\n `} {`Now all we have to do is to activate the alarm FTP upload in case of an alarm inside the `}{`Alarm Actions`}{`:`} {`\n `}{`\n `}{`\n `} {`We now can use the `} {`\n `}{`\n `}{`\n `} {`The variable our device is now watching is `} {`\n `}{`\n `}{`\n `} {`But FHEM also allows us to send commands by HTTP through our web browser (or by a curl command on your Linux terminal). The corresponding URL looks like this `} {`\n `}{`\n `}{`\n `} {`Note`}{` if calling the URL does not work and results in an `}{`HTTP ERROR 400`}{`, run the following command in the FHEM command line `} {`\n `}{`\n `}{`\n `} {`In the next step we will have to write a shell script that runs in the background on RasPi that watches for new file uploads in the FTP upload folder and updates the variable `} {`To notify FHEM when a snapshot is uploaded we need to install the `}{`inotify tools`}{` and create a shell script inside the FHEM directory `} {`The script contains the following:`} {`If you have chosen something different for any of those - please adjust the script accordingly:`} {`To be able to execute the script we need to change the owner from `} {`\n `}{`\n `}{`\n `} {`We can now start `} {`We now have to create a background service that automatically starts our script as a system daemon. This can be done with `}{`SystemD`}{` - `} {`\n `}{`\n `}{`\n `} {`Now we can reload `}{`SystemD`}{` and start our service:`} {`The background service is now running and FHEM should be notified every time an alarm is triggered and a snapshot is uploaded by our camera:`} {`We can now use FHEM to send us a push notification with the URL to the latest alarm image with the help of an app like the Android/iOS/Windows App `}{`Pushsafer`}{`. `}{`Note`}{` that there are a few other apps for Android iOS and Windows that can also be used for this:`} {`To able to use the push notification we first have to download the `}{`Pushsafer App`}{` for `}{`Android`}{`, `}{`iOS`}{` or `}{`Windows`}{` and register an account on the `}{`Pushsafer Website`}{`. Once you start the Pushsafer app you will be asked to login with your account credentials and register the device that you are using as the recipient of future push notifications. You can find the API documentation both on the `}{`FHEM Wiki`}{` and the `}{`Pushsafer FAQ Page`}{`.`} {`The `}{`Pushover Dashboard`}{` now lists your private key as well as the device you just registered:`} {`\n `}{`\n `}{`\n `} {`To prepare FHEM to be able to send Push Notifications make sure you have the following package installed on your RasPi:`} {`To define a Pushsafer device in FHEM we can use the following command:`} {`The parameter `} {`Example`}{`:`} {`\n `}{`\n `}{`\n `} {`Our connection to Pushsafer is ready and we can continue creating a `}{`Notify Device`}{` in FHEM that will trigger the push notification for us every time a new alarm snapshot is uploaded. We will call this device `} {`\n `}{`\n `}{`\n `} {`We can now trigger an alarm on our camera and check the FHEM event log - you should see that the URL was completed correctly `} {`\n `}{`\n `}{`\n `} {`You can find an extended introduction on how to integrate your INSTAR Full HD (with integrated MATT Broker) into FHEM in the `}{`INSTAR MQTT Broker`}{` section. But the FHEM Installation there was based on the Windows version. There isn't much of a difference once you have FHEM up and running. But installing FHEM (`}{`as described above`}{`) as well as it's dependencies (`}{`see below`}{`) obviously differs.`} {`\n `}{`\n `}{`\n `} {`\n `}{`\n `}{`\n `} {`You can now access the Node-RED interface through the following URL `} {`\n `}{`\n `}{`\n `}{`\n `}
{`instar`}{` - if you choose a different password you will have to substitute `}{`instar`}{` with it in the following steps.`}{`sudo`}{` `}{`service`}{` proftpd restart`}{`ftp://192.168.2.64:21/`}{`:`}{`\n `}
{`ftpuser `}{` can `}{`read and write`}{` files to the ProFTPd home directory - which can be a little bit frustrating some times when we need to add a file via the `}{`fhem`}{` or default `}{`pi`}{` user (that only have the right to `}{`read`}{`).`}{`\n `}
\n
\n {`sudo`}{` `}{`chmod`}{` -R `}{`666`}{` /var/www/upload/`}\n \n
\n \n \n \n \n {`Binary`} \n {`Octal`} \n {`Permission`} \n \n \n {`000`} \n {`0`} \n {`—`} \n \n \n {`001`} \n {`1`} \n {`–x`} \n \n \n {`010`} \n {`2`} \n {`-w-`} \n \n \n {`011`} \n {`3`} \n {`-wx`} \n \n \n {`100`} \n {`4`} \n {`r–`} \n \n \n {`101`} \n {`5`} \n {`r-x`} \n \n \n {`110`} \n {`6`} \n {`rw-`} \n \n \n \n {`111`} \n {`7`} \n {`rwx`} \n {`sudo mkdir officecam\nsudo chown ftpuser:ftpuser officecam/\nsudo chmod -R 666 /var/www/upload/officecam/`}{`Camera FTP Upload`}
\n {`\n `}
{`\n `}
{`event-on-update-reading`}{` attribute to trigger an event every time a new snapshot is uploaded by our camera:`}{`\n `}
{`new_snapshot`}{` which we can set by the following command: `}{`setreading OfficeCam.Alarm new_snapshot test`}{`:`}{`\n `}
{`http://192.168.2.64:8083/fhem?cmd=setreading%20OfficeCam.Alarm%20new_snapshot%20test2&XHR=1`}{`:`}{`\n `}
\n
\n {`attr WEB csrfToken none`}{` and try again. See the `}{`FHEM Forum`}{` for more details.`}{`\n `}
{`new_snapshot`}{` with the name of the newest file that was written. We need this service because alarm snapshots from our cameras are named with a time stamp - so we do not know what the name is going to be in advanced and need to forward this information to FHEM.`}{`Creating a Watch Daemon`}
\n {`alarmwatch.sh`}{`. This script should run as a background service, always checking if a new file was created inside the watch folder and call the URL above with the name of the file as value (instead of test or test2 as we tested it before):`}{`sudo`}{` `}{`apt`}{` `}{`install`}{` inotify-tools\n`}{`sudo`}{` `}{`nano`}{` /opt/fhem/alarmwatch.sh\n`}{`sudo`}{` `}{`chmod`}{` `}{`744`}{` /opt/fhem/alarmwatch.sh`}{`#!/bin/bash`}{`\n\n`}{`cd`}{` /var/www/upload/officecam\n\n`}{`# use inotify to watch multiple create events inside the camera upload folder`}{`\ninotifywait -m -e create /var/www/upload/officecam `}{`|`}{`\n`}{`while`}{` `}{`true`}{`;`}{` `}{`do`}{`\n `}{`while`}{` `}{`read`}{` `}{`$T`}{` path action `}{`file`}{`;`}{` `}{`do`}{`\n `}{`# cleanUp delete oldest file when 100 files are reached`}{`\n `}{`rm`}{` -f `}{`\\``}{`ls`}{` -td -1 /var/www/upload/officecam/** `}{`|`}{` `}{`awk`}{` `}{`'NR>100'`}{`\\``}{`\n `}{`echo`}{` `}{`\"'`}{`$file`}{`' was created in directory '`}{`$path`}{`' via '`}{`$action`}{`'\"`}{`\n `}{`# Get FHEM Command URL to set new_snapshot to current file name`}{`\n `}{`curl`}{` `}{`\"http://admin:instar@localhost:8083/fhem?cmd=setreading%20OfficeCam.Alarm%20new_snapshot%20`}{`$file`}{`&XHR=1\"`}{`\n `}{`done`}{`\n`}{`done`}\n
\n {`/var/www/upload/officecam`}{`admin`}{`instar`}{`8083`}{`OfficeCam.Alarm`}{`new_snapshot`}{`root`}{` to `}{`fhem`}{`:`}{`sudo`}{` `}{`chmod`}{` `}{`744`}{` /opt/fhem/alarmwatch.sh\n`}{`sudo`}{` `}{`chown`}{` fhem:dialout alarmwatch.sh`}{`\n `}
{`sh /opt/fhem/alarmwatch.sh`}{` the script manually and test if it is working by triggering an alarm on our camera:`}\n
\n {`officecam`}{` directory`}{`new_snapshot`}{` is set to the filename of the most current upload`}{`sudo nano /etc/systemd/system/OfficeCamWatch.service`}{`:`}{`[`}{`Unit`}{`]`}{`\n`}{`Description`}{`=`}{`OfficeCam Alarm Watch\n\n`}{`[`}{`Service`}{`]`}{`\n`}{`Type`}{`=`}{`oneshot\n`}{`ExecStart`}{`=`}{`/opt/fhem/alarmwatch.sh\n\n`}{`[`}{`Install`}{`]`}{`\n`}{`WantedBy`}{`=`}{`multi-user.target`}{`\n `}
{`sudo systemctl daemon-reload\nsudo systemctl enable OfficeCamWatch.service\nsudo systemctl start OfficeCamWatch.service`}\n
\n {`Push Notifications with Pushsafer`}
\n {`\n `}
{`sudo`}{` `}{`apt`}{` update\n`}{`sudo`}{` `}{`apt`}{` `}{`install`}{` libio-socket-ssl-perl`}{`define `}{`<`}{`name`}{`>`}{` Pushsafer `}{`<`}{`key`}{`>`}{`{` is the private key you can find on your `}{`Pushover Dashboard`}{`. A alphanumeric string (20 digits) from your Pushsafer account.`}\n
\n {`\n `}
{`AlarmPush`}{` and it will receive a notification every time `}{`OfficeCam.Alarm`}{` is triggered. To get the URL for the latest alarm image, we can use `}{`$EVENT`}{` which will give us access to the event reading `}{`new_snapshot: A19050121330310.jpg`}{`. We can specify here that we only want the value of this pair by using `}{`$EVTPART1`}{` (`}{`$EVTPART0`}{` would give us `}{`new_snapshot`}{` instead):`}{`define AlarmPush notify OfficeCam.Alarm `}{`set`}{` PushsaferLogin message `}{`'Motion Detection was triggered'`}{` `}{`title`}{`=`}{`'Office Cam Alarm'`}{` `}{`picture`}{`=`}{`'/var/www/upload/officecam/`}{`$EVTPART1`}{`'`}{`\n `}
{`picture='/var/www/upload/officecam/A19050121330310.jpg'`}{` and the image was successfully forwarded to Pushsafer.`}{`\n `}
{`2019`}{`-05-01 `}{`21`}{`:33:12 dummy OfficeCam.Alarm new_snapshot: A19050121330310.jpg\nPushsafer PushsaferLogin message `}{`'Motion Detection was triggered'`}{` `}{`title`}{`=`}{`'Office Cam Alarm'`}{` `}{`picture`}{`=`}{`'/var/www/upload/officecam/A19050121330310.jpg'`}{`\n`}{`2019`}{`-05-01 `}{`21`}{`:33:18 Pushsafer PushsaferLogin lastSuccess: message transmitted`}{`MQTT Integration`}
\n {`MQTT Prerequisite`}
\n {`sudo apt-get install libmodule-pluggable-perl\nsudo cpan install Net::MQTT:Simple\nsudo cpan install Net::MQTT:Constants`}{`Installation of Node-Red`}
\n {`sudo apt-get install build-essential\n\nwget https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered\n\n\n\nbash update-nodejs-and-nodered`}{`\n `}
{`node-red-start\nnode-red-stop\n\nsudo systemctl enable nodered.service\nsudo systemctl disable nodered.service\n\nsudo systemctl start nodered.service\nsudo systemctl stop nodered.service`}{`\n `}
{`http://192.168.2.64:1880/`}{` - where `}{`192.168.2.64`}{` has to be substituted by your server address (Raspberry Pi):`}{`\n `}