bzzzzzt
Go to file
2023-05-30 19:06:14 -06:00
cmd db migrations, push notification test 2023-04-16 15:17:36 -06:00
internal add webmanifest for public app, make timezone configurable to fix schedule hours comparison 2023-05-30 19:06:14 -06:00
.editorconfig some user rest crud, refactor middleware, start admin 2023-01-02 00:57:17 -06:00
.gitignore redirect on /admin, push tweaks 2023-04-16 16:00:21 -06:00
.tool-versions db migrations, push notification test 2023-04-16 15:17:36 -06:00
config.template.yaml add webmanifest for public app, make timezone configurable to fix schedule hours comparison 2023-05-30 19:06:14 -06:00
go.mod db migrations, push notification test 2023-04-16 15:17:36 -06:00
go.sum db migrations, push notification test 2023-04-16 15:17:36 -06:00
LICENSE.txt knock knock 2022-12-31 00:06:39 -06:00
main.go db migrations, push notification test 2023-04-16 15:17:36 -06:00
README.md refactor and nice stuff 2023-01-03 22:21:49 -06:00
schema.sql db migrations, push notification test 2023-04-16 15:17:36 -06:00

la puerta de mi casa

A ridiculously elaborate rubegoldbergian contraption to exchange my guests' biometric data for my front door going bzzzz, built with go, css, html and javascript.

This project is:

  • highly insecure: you should not run this at home,
  • very alpha: to put it mildly,
  • poorly tested by my guests and myself, so barely—if at all, and
  • truly magical to see in action, when it does work.

Web App

This is what my guests see. It's basically a login page where they enter credentials, and then a big button to open the door. My guests are required to authenticate with a passkeys before opening the door, usually backed by a yubikey, TouchID or whatever android does.

A very simple admin page allows me to manage guests and see the entry log. Built with pochjs (plain-old css, html and js).

API

The API runs on my homelab, serves the web app and interacts with my front door's buzzer. It's built with go and backed by SQLite.

Adapters

Since the buzzer electrical setup is still not something i completely understand, I went around the issue by connecting the buzzer's power supply to a "smart" plug. Originally built it to control a wemo mini smart plug, but have since switched into using a hue one for no good reason other than the wemo's API is annoying.

CLI

There's a small CLI tool to start the API, setup and test the Hue connection, and to add users (helpful during bootstrap).