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:
MarceloSalazar
Date:
Fri Jul 13 08:24:42 2018 +0000
Revision:
7:816e19453a7f
Parent:
6:e0e1e1b93099
Child:
9:265744785d33
Add _RTE_ workaround for issue #7422 in 5.9.2

Who changed what in which revision?

UserRevisionLine numberNew contents of line
adustm 1:e86b1cffc402 1 {
adustm 1:e86b1cffc402 2 "macros": [
adustm 1:e86b1cffc402 3 "MBEDTLS_USER_CONFIG_FILE=\"mbedTLSConfig_mbedOS.h\"",
adustm 4:cf7342047b4d 4 "PAL_USER_DEFINED_CONFIGURATION=\"sotp_fs_config_MbedOS.h\"",
adustm 1:e86b1cffc402 5 "MBED_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
adustm 1:e86b1cffc402 6 "MBED_CLOUD_CLIENT_USER_CONFIG_FILE=\"mbed_cloud_client_user_config.h\"",
adustm 1:e86b1cffc402 7 "PAL_DTLS_PEER_MIN_TIMEOUT=5000",
adustm 5:8d7b1da4f6fa 8 "MBED_CONF_APP_MAIN_STACK_SIZE=6000",
adustm 4:cf7342047b4d 9 "ARM_UC_USE_PAL_BLOCKDEVICE=1",
MarceloSalazar 7:816e19453a7f 10 "MBED_CLOUD_CLIENT_UPDATE_STORAGE=ARM_UCP_FLASHIAP_BLOCKDEVICE",
MarceloSalazar 7:816e19453a7f 11 "_RTE_"
adustm 1:e86b1cffc402 12 ],
adustm 1:e86b1cffc402 13 "target_overrides": {
adustm 1:e86b1cffc402 14 "*": {
adustm 1:e86b1cffc402 15 "platform.stdio-baud-rate": 115200,
adustm 1:e86b1cffc402 16 "platform.stdio-convert-newlines": true,
adustm 4:cf7342047b4d 17 "update-client.storage-address" : "(1024*1024*64)",
adustm 4:cf7342047b4d 18 "update-client.storage-size" : "(1024*1024*2)",
adustm 4:cf7342047b4d 19 "update-client.storage-locations": "1",
adustm 1:e86b1cffc402 20 "mbed-trace.enable": null
adustm 4:cf7342047b4d 21 },
adustm 4:cf7342047b4d 22 "DISCO_L475VG_IOT01A": {
adustm 4:cf7342047b4d 23 "sotp-section-1-address" : "(0x08000000+((1024-32)*1024))",
adustm 4:cf7342047b4d 24 "sotp-section-1-size" : "(16*1024)",
adustm 4:cf7342047b4d 25 "sotp-section-2-address" : "(0x08000000+((1024-16)*1024))",
adustm 4:cf7342047b4d 26 "sotp-section-2-size" : "(16*1024)",
adustm 4:cf7342047b4d 27 "sotp-num-sections" : 2
adustm 6:e0e1e1b93099 28 },
adustm 6:e0e1e1b93099 29 "DISCO_F413ZH": {
adustm 6:e0e1e1b93099 30 "sotp-section-1-address" : "(0x08000000+((1536-256)*1024))",
adustm 6:e0e1e1b93099 31 "sotp-section-1-size" : "(128*1024)",
adustm 6:e0e1e1b93099 32 "sotp-section-2-address" : "(0x08000000+((1536-128)*1024))",
adustm 6:e0e1e1b93099 33 "sotp-section-2-size" : "(128*1024)",
adustm 6:e0e1e1b93099 34 "sotp-num-sections" : 2
adustm 1:e86b1cffc402 35 }
adustm 4:cf7342047b4d 36
adustm 1:e86b1cffc402 37 },
adustm 1:e86b1cffc402 38 "config": {
adustm 4:cf7342047b4d 39 "format-storage-layer-on-error": {
adustm 4:cf7342047b4d 40 "help": "Whether to format the storage layer when it cannot be read - always disable for production devices!",
adustm 4:cf7342047b4d 41 "value": 1
adustm 4:cf7342047b4d 42 },
adustm 1:e86b1cffc402 43 "developer-mode": {
adustm 1:e86b1cffc402 44 "help": "Enable Developer mode to skip Factory enrollment",
adustm 1:e86b1cffc402 45 "value": 1
adustm 1:e86b1cffc402 46 },
adustm 1:e86b1cffc402 47 "wifi-ssid": {
adustm 1:e86b1cffc402 48 "help": "WiFi SSID",
adustm 1:e86b1cffc402 49 "value": "\"SSID\""
adustm 1:e86b1cffc402 50 },
adustm 1:e86b1cffc402 51 "wifi-password": {
adustm 1:e86b1cffc402 52 "help": "WiFi Password",
adustm 1:e86b1cffc402 53 "value": "\"PASSWORD\""
adustm 1:e86b1cffc402 54 },
adustm 4:cf7342047b4d 55 "sotp-section-1-address": {
adustm 4:cf7342047b4d 56 "help": "Flash sector address for SOTP sector 1",
adustm 4:cf7342047b4d 57 "macro_name": "PAL_INTERNAL_FLASH_SECTION_1_ADDRESS",
adustm 4:cf7342047b4d 58 "value": null
adustm 1:e86b1cffc402 59 },
adustm 4:cf7342047b4d 60 "sotp-section-1-size": {
adustm 4:cf7342047b4d 61 "help": "Flash sector size for SOTP sector 1",
adustm 4:cf7342047b4d 62 "macro_name": "PAL_INTERNAL_FLASH_SECTION_1_SIZE",
adustm 4:cf7342047b4d 63 "value": null
adustm 1:e86b1cffc402 64 },
adustm 4:cf7342047b4d 65 "sotp-section-2-address": {
adustm 4:cf7342047b4d 66 "help": "Flash sector address for SOTP sector 2",
adustm 4:cf7342047b4d 67 "macro_name": "PAL_INTERNAL_FLASH_SECTION_2_ADDRESS",
adustm 4:cf7342047b4d 68 "value": null
adustm 1:e86b1cffc402 69 },
adustm 4:cf7342047b4d 70 "sotp-section-2-size": {
adustm 4:cf7342047b4d 71 "help": "Flash sector size for SOTP sector 2",
adustm 4:cf7342047b4d 72 "macro_name": "PAL_INTERNAL_FLASH_SECTION_2_SIZE",
adustm 4:cf7342047b4d 73 "value": null
adustm 1:e86b1cffc402 74 },
adustm 4:cf7342047b4d 75 "sotp-num-sections": {
adustm 4:cf7342047b4d 76 "help": "Number of SOTP sections",
adustm 4:cf7342047b4d 77 "macro_name": "PAL_INT_FLASH_NUM_SECTIONS",
adustm 4:cf7342047b4d 78 "value": null
adustm 1:e86b1cffc402 79 }
adustm 1:e86b1cffc402 80 }
adustm 1:e86b1cffc402 81 }