Olympus

SHED grants access to the space when locked, entry for members when opening the space at the start of the day, or late at night.

Intro

• Problem: Needs to fulfill a few purposes. First in the order people might think about them, or naturally state them, before we decompose them into functional requirements, or simple solutions that aim to satisfy multiple naive user specifications (in a creative and minimal way if possible, instead of via extensive requirments).
  • Grant entry to members. When a valid key is presented, only when a valid key is presented, unlock. Grant entry to some users only during open hours.
  • Make addition of new temporary members easy. Make auditing list of people (/keys) with access possible. Make revocation possible.
  • (Possibly report (live)/record (for later review) entry attempts, failed (or also successful).)
  • (no others named, challenge)

• Solution:
  • Outside
    • RFID Scanner: RFID-RC522. Vsrc, Gnd, 5 pins in use. (1 ethernet cable. 7/8 wires.)
    • Screen. Vsrc, Gnd, +~2 pins in use.
    • Switches, 2. 2 pins indicator, share Vsrc, Gnd. Switch "add user" mode, push-button "member" modifier.
  • Inside
    • RPi. 40 pin. https://pinout.xyz/
    • Secured: in wall-mounted box, or in lockable mailbox "suite 1", or not locked, "suite 2".
  • Connection: 2 ethernet cables.
    • Serve power/ground over both (to support smaller standalone components for testing & debugging).

Software

• Daniel wrote.

Using

Instructions appear on the screen within 1-5 seconds, explains itself, mostly.

• Scan RFID, access granted (/denied), door unlocks.
• Add user: admin user enables "new user" switch, scans admin RFID, scans new user id (with or without "member" intensifier). Added users have immediate access.
  • New members must scan QR code, add name/contact info to google form, and submit for approval.

Managing

• Firebase database manages the UID, raw from RFID.
• New users via google form. QR code link, with RFID UID, shown on screen for enrollment.

Wants & Future Directions

• Blind RFID values read, stored, & shared. Hash (with salt), or HMAC. In database, and uploaded in gForm. (Prevent snooping & spoofing "credentials" - RFID is just ID, no secret / password / challenge.
• Report additions (blinded / without UIDs) to Discord & Slack (via RSS?).
• Look into self-hosting database. https://nocodb.com, self-hosting (self-hosted ~Airtable + APIs. Auth handled.)
• Integrate User:Mcint/Projects/Member system.