Looking for doors location or access/keycards? → Wiki homepage
¶ Components
¶ inventory.k-space.ee (Open doors)
Slack commands operate as a webhook to its API endpoint. WebUI for remotely opening doors, editing keycards, and displaying logs.
On opening a door:
- Checks ACL against (Passmower CRD) Kube API.
- Writes a log entry to mongo and Slack #door-log.
Deployed from kube:hackerspace
¶ doorboy-proxy
Server for door Pi-s. Monitors mongo logs for opens, and actions on them. Logs swipe opens to mongo.
Deployed from kube:hackerpsace/doorboy.yml
¶ godoor
Software on the Pi-s. 'Remotes in to doorboy-proxy'
Maintains an (offline) list of allowed card hashes for the current door.
Deployed from kube:ansible/doors.yml
¶ Upgrades
(planning; todo)
- smartasses for https://wiki.k-space.ee/en/utilities/lights
- Upper door upgrades (3x):
-
PIR outside(ordered) 'laser'-gate sensor: doorbell (datasheet) -
(Rasmus-provided) Door sensor: count leaves
-
(depo) 1-button switch (impulsslüliti) for 'turn off all' / server room panik
-
Proper box with photoelectric/microswitch sensor
- Software integration/automation yay
- (extra) streaming setup power automation + a-la streamdeck 'start recording'
- (extra) retro unified power switch (electrically decoupled) + physical power disconnect (DOS machines are fine to insta-power-off)
¶ Doors infrastructure
Currently door system contains 3 services 
- MongoDB that stores events and backing store
- members.k-space.ee has the UI
- doorboy-proxy - API
- godoor- New door controller code (GoLang)
- mjpg-streamer - Camera
- kdoorpi - Old door controller code (Python)
(Ping Arti for more info)
Old system used upgrid.
¶ Hardware
¶ Raspberry Pi Shield
Takes 12V and has a MOSFET for door solenoid and inputs for Wiegand data pins
¶ Card Reader
We use AY-H6255 NFC Card Reader in Wiegand mode. There are 4 spare: https://inventory.k-space.ee/m/inventory/66d1c2f40f807b50c4e1293e/view
- Reader manual: ay-x6255.pdf
- back_door_wiegand.jpg
| Wire Color | Function |
|---|---|
| Red | Power |
| Black | Ground |
| Green | Data 0 / Data |
| White | Data 1 / Clock |
| Orange | Green LED Control* |
| Brown | Red LED Control* |
| Purple | Tamper Output |
| Yellow | Buzzer Control* |
| Blue | RS-485 – A / OSDP** |
| Gray | RS-485 – B / OSDP** |
* These wires have programmable functions that may be adjusted by presenting
a configuration card within 10 seconds upon powering on the unit. See the
CS-CCT Configuration Card Tool for the DR-6255 Software Manual for how
you can create a configuration card.
** RS-485 is used for firmware update
¶ USB card reader
Previously used for adding cards by UID. It spits out UID in reverse. Python 2 script to normalize the output:
import struct
import sys
while True:
buf = sys.stdin.readline().decode("ascii")
print(" ".join([j.encode("hex") for j in struct.pack("I",int(buf))]).upper())