Garage Door Monitor and Opener

Dependencies:   X_NUCLEO_COMMON ST_INTERFACES

Introduction

This system implements a simple garage door opener and environmental monitor. The hardware connects to the internet using Wi-Fi then on to the Pelion Device Management Platform which provides device monitoring and secure firmware updates over the air (FOTA). Pelion Device Management provides a flexible set of REST APIs which we will use to communicate to a web application running on an EC-2 instance in AWS. The web application will serve a web page where we can monitor and control our garage..

This project is intended to work on the DISCO-L475VG-IOT01A from ST Microelectronics It implements a simple actuator to drive a relay to simulate pushing the "open" button on older style garage doors which do not use a rolling code interface.

The system is designed to be mounted over the door so that the on board time of flight sensor can be used to detect if the door is open or closed.

The system also monitors temperature, humidity and barometric pressure.

https://os.mbed.com/media/uploads/JimCarver/garageopener.jpg

Hardware Requirements:

DISCO-L475G-IOT01A https://os.mbed.com/platforms/ST-Discovery-L475E-IOT01A/

Seeed Studio Grove Relay module https://www.seeedstudio.com/Grove-Relay.html

Seeed Studio Grove cable, I used this one: https://www.seeedstudio.com/Grove-4-pin-Male-Jumper-to-Grove-4-pin-Conversion-Cable-5-PCs-per-Pack.html

Connect to the PMOD connector like this:

https://os.mbed.com/media/uploads/JimCarver/opener.jpg

This shows how I installed so that the time of flight sensor can detect when the door is open

https://os.mbed.com/media/uploads/JimCarver/opener1.jpg https://os.mbed.com/media/uploads/JimCarver/opener2.jpg

To use the project:

You will also need a Pelion developers account.

I suggest you first use the Pelion quick state to become familiar with Pelion Device Management. https://os.mbed.com/guides/connect-device-to-pelion/1/?board=ST-Discovery-L475E-IOT01A

Web Interface

For my web interface I am running node-red under Ubuntu in an EC2 instance on AWS. This can run for 12 month within the constraints of their free tier. Here is a tutorial: https://nodered.org/docs/getting-started/aws

You will also need to install several node-red add ons:

sudo npm install -g node-red-dashboard

sudo npm install -g node-red-contrib-mbed-cloud

sudo npm istall -g node-red-contrib-moment

After starting node-red import the contents of GarageFlow.txt from the project, pin the flow into the page.

To enable your web app to access your Pelion account you need an API key.

First you will neet to use your Pelion account to create an API key.

https://os.mbed.com/media/uploads/JimCarver/api_portal.jpg

Now we need to apply that API key to your Node-Red flow.

https://os.mbed.com/media/uploads/JimCarver/api_node-red.jpg

Committer:
JimCarver
Date:
Thu Dec 05 19:03:48 2019 +0000
Revision:
37:ec1124e5ec1f
Parent:
28:0e774865873d
Bug fix

Who changed what in which revision?

UserRevisionLine numberNew contents of line
screamer 28:0e774865873d 1 /* mbed Microcontroller Library
screamer 28:0e774865873d 2 * A generic CMSIS include header
screamer 28:0e774865873d 3 *******************************************************************************
screamer 28:0e774865873d 4 * Copyright (c) 2017, STMicroelectronics
screamer 28:0e774865873d 5 * All rights reserved.
screamer 28:0e774865873d 6 *
screamer 28:0e774865873d 7 * Redistribution and use in source and binary forms, with or without
screamer 28:0e774865873d 8 * modification, are permitted provided that the following conditions are met:
screamer 28:0e774865873d 9 *
screamer 28:0e774865873d 10 * 1. Redistributions of source code must retain the above copyright notice,
screamer 28:0e774865873d 11 * this list of conditions and the following disclaimer.
screamer 28:0e774865873d 12 * 2. Redistributions in binary form must reproduce the above copyright notice,
screamer 28:0e774865873d 13 * this list of conditions and the following disclaimer in the documentation
screamer 28:0e774865873d 14 * and/or other materials provided with the distribution.
screamer 28:0e774865873d 15 * 3. Neither the name of STMicroelectronics nor the names of its contributors
screamer 28:0e774865873d 16 * may be used to endorse or promote products derived from this software
screamer 28:0e774865873d 17 * without specific prior written permission.
screamer 28:0e774865873d 18 *
screamer 28:0e774865873d 19 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
screamer 28:0e774865873d 20 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
screamer 28:0e774865873d 21 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
screamer 28:0e774865873d 22 * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
screamer 28:0e774865873d 23 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
screamer 28:0e774865873d 24 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
screamer 28:0e774865873d 25 * SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
screamer 28:0e774865873d 26 * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
screamer 28:0e774865873d 27 * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
screamer 28:0e774865873d 28 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
screamer 28:0e774865873d 29 *******************************************************************************
screamer 28:0e774865873d 30 */
screamer 28:0e774865873d 31
screamer 28:0e774865873d 32 #ifndef MBED_CMSIS_H
screamer 28:0e774865873d 33 #define MBED_CMSIS_H
screamer 28:0e774865873d 34
screamer 28:0e774865873d 35 #include "stm32l4xx.h"
screamer 28:0e774865873d 36 #include "cmsis_nvic.h"
screamer 28:0e774865873d 37
screamer 28:0e774865873d 38 #endif