makeict / mcp-client

Clients for the Master Control Program

Master Control Program

This system is used to secure spaces with an electronic door latch.

Dependencies:

• Node + NPM
• PostgreSQL
• Arduino 1.6.5

Hardware requirements:

• Server protocol RS-485 for the server/client communication.
• Arduino Nano for the door client (This is required for the matching footprint).
• NFC reader. This is the one that we are using for our version of the door lock.

---

Todo

• Server

  • Super admins vs group admins
  • Make plugins respect disabled mode
  • When unlocking from web ui, display user in log

• Client

  • New NFC reader
  • Add doorbell input (capacitive?)
  • Design/build case for front
  • Build 2nd client for testing & back door

License

Copyright (C) 2014-2016 MakeICT

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see The GNU licenses page

---

This is a work in progress. For more information, please visit the MakeICT Wiki.

---

mcp-client's Issues

GPIO 36 and 39 constantly trigger interrupts

espressif/esp-idf#1096
espressif/esp-idf#4585

Ethernet Hardware

Add hardware for ethernet connection.

Log to SD card

Add an option to write logs to SD for debugging. Will need to be considerate of write frequency.

OTA Updates

OTA updates will be necessary to reduce update workload as the number of active clients increases.

Hostnames and static IPs

Add the ability to set hostname and static IP for better network management. Should probably be a configuration option, but hostname could default to mcp_client_<client_id> or something along those lines.

WS2812 Support

Add support for WS2812 RGB LEDS for client status display.

Client features for alarm system

• Alarm arm button
• Arm countdown/warning
• Delayed arm

Alarm arm button

Need to re-add the button that arms the alarm system. Ideally this would be via a dedicated module connected to the alarmsystem that handles all arm/disarm requests for MCP.

Arming via Keyswitch

• all zones (doors and motions) are immediately armed.
• the last discussed plan was to have a button push in MCP have a delay of maybe a minute before arming via keyswitch. Some kind of countdown or warning is needed.
• MCP would wait up to 3 minutes, check system is armed and if not attempt arming again.
• MCP would wait another duration, check system and attempt another re-arm
• MCP would check a final time and send notification at arm failed.