No edit summary |
No edit summary |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
|Name=Door lock | |Name=Door lock | ||
|Skills=Electronics, | |Skills=Electronics, | ||
|Status= | |Status=Archived | ||
|Niche=Electronics | |Niche=Electronics | ||
|Purpose=Infra | |Purpose=Infra | ||
| Line 9: | Line 9: | ||
|Category=Electronics | |Category=Electronics | ||
}} | }} | ||
== Next generation == | |||
The next generation of the software is documented [[Network/Roadmap/DoorLock|here]]. The content below is kept for historical purposes | |||
== Introduction == | == Introduction == | ||
This page describes the hardware used to create the new door lock of the space. Basically there is a RFID-reader that can read blue keychain tokens and some types of RFID-cards (like OV-chipkaart and WUR-cards). The code of the token/card needs to be read once to match it to a user and then grants access to the front door. Zarya can do this for you when needed. | This page describes the hardware used to create the new door lock of the space. Basically there is a RFID-reader that can read blue keychain tokens and some types of RFID-cards (like OV-chipkaart and WUR-cards). The code of the token/card needs to be read once to match it to a user and then grants access to the front door. Zarya can do this for you when needed. | ||
| Line 31: | Line 35: | ||
{{:Doordaemon}} | {{:Doordaemon}} | ||
=== Requirements === | === Requirements === | ||
* Must be contained in a single device | * Must be contained in a single device | ||
* Must have a power backup (UPS) at least 12 hours of runtime | * Must have a power backup (UPS) at least 12 hours of runtime | ||
* Must provide support for the current cards to be able to migrate to new cards/tokens | * Must provide support for the current cards to be able to migrate to new cards/tokens | ||
** 125kc is support but requires extra hardware | |||
* New tokens should be of a secure type and not use the card id as credential | * New tokens should be of a secure type and not use the card id as credential | ||
=== Nice to have === | === Nice to have === | ||
* Tokens on mobile | * Tokens on mobile | ||
=== Hardware === | === Hardware === | ||
| Line 47: | Line 49: | ||
=== Software === | === Software === | ||
https://gitea.vm.nurd.space/zarya/door-controller | |||
[[File:door_lock_flow_chart.png|400px]] | |||
==== old software ==== | |||
* Write our own? | * Write our own? | ||
** https://github.com/ArPIHomeSecurity/pywiegand | ** https://github.com/ArPIHomeSecurity/pywiegand | ||
| Line 52: | Line 57: | ||
** https://github.com/leosac/leosac | ** https://github.com/leosac/leosac | ||
** https://github.com/leosac/leosac-web | ** https://github.com/leosac/leosac-web | ||
Latest revision as of 20:53, 6 September 2024
| Door lock | |
|---|---|
 | |
| Participants | |
| Skills | Electronics |
| Status | Archived |
| Niche | Electronics |
| Purpose | Infra |
| Tool | No |
| Location | Front Door |
| Cost | |
| Tool category | Electronics |
Door lock Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{#if:No | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:No | [[Tool Cost::{{{Cost}}} | }}
Next generation
The next generation of the software is documented here. The content below is kept for historical purposes
Introduction
This page describes the hardware used to create the new door lock of the space. Basically there is a RFID-reader that can read blue keychain tokens and some types of RFID-cards (like OV-chipkaart and WUR-cards). The code of the token/card needs to be read once to match it to a user and then grants access to the front door. Zarya can do this for you when needed.
Hardware used
Pics
Doordaemon script
- doordaemon
- responds to offering a RFID tag (mifare and others) at the doorsensor
Now running in a docker container on docker.vm.nurd.space
Seeing the logs: docker logs -f doordeamon
Restarting: docker restart doordeamon
** runs on the nurdbot VM
- reads an imap box
- sends metrics to mqtt
- Installed under /home/nurdbot/doordaemon
- configured via /home/nurdbot/doordaemon/config.json
- Management via /etc/init.d/doordaemon
- Logging in /var/log/doordaemon.log
Restarting:
/etc/init.d/doordaemon restart
Requirements
- Must be contained in a single device
- Must have a power backup (UPS) at least 12 hours of runtime
- Must provide support for the current cards to be able to migrate to new cards/tokens
- 125kc is support but requires extra hardware
- New tokens should be of a secure type and not use the card id as credential
Nice to have
- Tokens on mobile
Hardware
- Must support wiegand
Software
https://gitea.vm.nurd.space/zarya/door-controller
old software
- Write our own?
- https://github.com/leosac Not to usefull, hard to compile, hard to modify (c++)
Reader and WEMOS have been ordered, will make a test setup with this software: https://github.com/esprfid/esp-rfid when it's all in the reader supports MiFare and 125khz tags.
Running
- Wemos D1 reachable via d00rl0ck.local (Needs update due to MQTT BROKER ISSUES)
Pin out of reader to CAT5
12v+ RED > ORANGE | 12-(Ground) BLACK > BROWN/WHITE | D0/RX/4AR+(wiegand) GREEN > GREEN | D1/TX/4AR- WHITE > GREEN/WHITE | LED BLUE > BLUE| BEEP YELLOW > BROWN | WG26/34 GRAY > BLUE>WHITE | Door Bell > PURPLE > ? | ORANGE/WHITE isn't used
ToDo
- Upgrade ESP-RFID to 1.3.3 HOTFIX [1]
- Test out the scanner
- Hack that SBOARD?
- Maybe rewrite ESP-RFID to python to run on space nanny