Node Red 

On boot up the Inject node automatically runs to set a default value for the dashboard Numeric (Refresh Interval) and activate a Trigger node for the ARP node. A msg.payload  of off  is delivered to dashboard Buttons (PIR alerts and RECORD) to set their status (a delay in delivery was found to be beneficial).

The face icon is displayed by the Text node's Label 

<br><br><font color= {{color}} ><span class="material-icons">face</span></font>

 the color of which is set by msg.color in the Function node (Away/Home) depending on whether any of the mobile phones are connected to the local network, as ascertained by the ARP node. The payload from the Function node is set to either on or off which determines what happens in PIR alerts, but needs to be deleted before passing the msg.color on to Text node (Face) icon so that datestamp in the Face node is not overwritten. A Filter node limits the flow to changes in the payload message.

Function node (Away/Home)

1. msg.color =(msg.payload!="")?"limegreen":"red";

2. msg.payload = (msg.payload!="")?"off":"on";

3. return msg;

The frequency that the Address Resolution Protocol is accessed is set at initialisation. 

Whenever the lastSeen DATE is updated (msg.payload SET $now()) the flow continues through Link in nodes to towards the Link out node (to Mailer). Whether or not an email motion sensor alert is sent is dependent on the Function node (Gate control)  and the Dashboard Switch (PIR alerts). Messages arriving at the Function node from lastSeen DATE do not have a message topic, whereas those from PIR alerts have msg.topic set to "gate". If "Gate control" gets a messages with the msg.topic "gate" and a msg.payload of "on" from dashboard Switch node (PIR Alerts) then the gate is set to open to allow lastSeen Date messages to pass through to the Link out node to Mailer, otherwise its message is dropped.

1. if (msg.topic === "gate") {

2.     context.pass = (msg.payload === "on") ? "on": "off!;

3.     return null;  // exit out early as it's just the control

4. }

5. if (context.pass) {

6.     return msg; // if enabled pass msg

7. }

8. return null; // or drop it

The lastSeen DATE Change node's msg.payload of  $now()  is changed in the PIR Alert Change node with a Jsonata xpression so that the date and time are appended '☎ PIR alert HALL.... ' & $moment(payload).format("MMM-DD HH:mm") before being forwarded via the Link out node to Emailer.

An "on" msg.payload from the Switch node (switch on/off) originating from ARP passes to the Switch node (Gate: PIR off) and if flow.PIRstatus is set to "off" then msg.payload is allowed pass through and in so doing prompts a notification email of "HA PIR on". The msg.payload is also forwarded via the Link out node to Alexa Audio Alerts.

This section provides the user with two Dashboard controls. 

1. The RECORD switch which enables

• recording of PIR movement activity in the cloud to Google Sheets 

• displaying of a Table of Recent Activity

• revealing the Refresh Interval control

     The RECORD switch is also set to "on" status whenever the PIR alerts Switch is changed to "on" status.

2. The Refresh Interval (minutes) Numeric control which sets an interval of 1 to 10 minutes between the registering of PIR movement activity in order to reduce multiple notifications.

The Inject  node (Default Alert) sets an initial editable default message in the dashboard Audio Alert on startup. Whenever there is a PIR alert it is forwarded on to the ALEXA Audio Alerts group via the Link in node. Depending on whether the flow.LOCstatus is "away" or "home" the msg payload is set to flow.Audioalert (as set by the dashboard Audio Alert) or "Welcome Home" before being directed towards the MQTT node (Shout) on the raspberry pi paired with the Amazon Echo Dot bluetooth speaker. If the latter, the msg.payload is then set to "off" and forwarded to the PIR alert switch thereby stopping any further alerts. Whether the msg.payload gets through the Gate Function node  depends on the ui Switch which can set the gate to be open or closed.

The piCam's Motion Detection mirrors the pirAlert status and so is automatically switched on when all mobiles are away from home. The Filter only allows pirAlert status.text to pass in the event of a change in the status "on" or "off" to trigger the piCam Switch automatically. The piCam Switch can also be set manually in the dashboard. A URL instruction is sent to the piCam via the HTTP GET Request to Start or Pause Motion Detection in MotionEYE and a UTF-8 string is returned indicating completion of the instruction, this is used in the Function node (Color Mapping) to set the msg.color of the Switch (piCam Alert) dashboard text. Green indicates that MotionEYE has responded to the instruction and Motion Detection is active.

1. //First need to remove all line feeds

2. msg.payload = msg.payload.replace(/[\r\n]/gm, ' ');

3. 
   

4. //then trim any spaces from end

5. msg.payload = msg.payload.trim();

6. switch (msg.payload) {

7. 
   

8. case "Camera 1 Detection paused Done": 

9.     msg.color = "grey";

10.     break;

11.     

12. case "Camera 1 Detection resumed Done": 

13.     msg.color = "limegreen";

14.     break;

15.     

16. default : 

17.     msg.color = "red";

18.     break;

19. }

20. 
    

21. return msg;

The Change node (extract URL) sets msg.url as described above for e.g. the Static image of initial movement. An Http Request (set to: GET, and payload as Send as request body, with Return as a binary buffer) is processed by Base64 (Action : Encode as Base64) and output in a ui Template (set to: Reload last value on refresh - so that the image persists in the dashboard on refresh). Using the following Template 

1. <style>

2.     img{

3.         object-fit:contain;

4.     }

5. </style>

6. 
   

7. <img src="data:image/png;base64,{{msg.payload}}" />

the image fills the desired grid pattern set by Size.

While this technique is useful for accessing individual images and videos through the Web Control Interface as and when notified by the Webhook it does not lend itself to accessing prior recordings but can be useful for providing TensorFlow with the motion file image for recognition analysis.

SSH into your Pi runing MotionEYE WITHOUT a Password with SSH Keys

In rpi 1 terminal hosting Node Red type and enter

ssh-keygen

Accept default file in which to save key

then asked whether you want a pass phrase so ENTER and again for verification.

Copy over the RSA key to the other rpi 2 runing MotionEYE by entering into the terminal

ssh-copy-id pi@[ip address]

you will asked for the password for the rpi 2, so authenticate with password for rpi 2

Then it is possible to SSH into rpi2 from rpi 1 without having to enter a password.

SSH access will allow full access of files on rpi2 from rpi.

ssh Find Motion mp4

While the Webhook in the piCam Alert section alerts when movement has been detected in MotionEYE, the Webhook Img notifes whenever a Motion File has been saved by MotionEYE, and causes the Exec node to run a bash script 

ssh pi@192.168.n.n 'find  /var/lib/motioneye/Camera1/*/  -type f -name "*.mp4"' | sort -r

which finds all the MotionEYE mp4 files on the Pi running MotionEYE and orders them with the most recent first in a msg.payload string. The Function node (Motion Files Array Collation)  fragments the msg.payload string into an array consisting of just the date and time with the mp4 extension.

const myarray = msg.payload.split('/var/lib/motioneye/Camera1/');

msg.payload = myarray.slice(1);

return msg;

The array is the Split and the individual elements are prepended with the Webview information for the Static image of initial movement in Video

msg.payload = "http://192.168.n.n:8765/movie/1/preview/"+msg.payload;

return msg;

before rejoining the elements back into an array and saving the msg.payload array as a flow.MotionFiles.

Here the image is analysed by the tf coco ssd node. If the node returns a msg.class.person then the switch node passes it on to the set msg.payload node which sets msg.payload to true. The message is returned to the Alert Restrict node group via the mqtt nodes (sensor/kitchen/person). In the Switch node msg.trigger is set to the returned msg.payload value of True, which releases the alert from the hold node. The alert is sent to mailer. 

Mailer