1 / 10
Guardian interior portal — ESP32-S3 keypad, RFID, display, door IMU — zdjęcie 1
1 / 10

Guardian interior portal — ESP32-S3 keypad, RFID, display, door IMU

Zamów wydruk tego modelu

Obliczymy ostateczną cenę na podstawie wybranego pliku. Sprawdzisz ją i zaakceptujesz przed płatnością.

Zapisane na tym urządzeniu.

Interior door station in PETG: main body, wall plate, keypad and display frames, speaker and more. Hand-soldered PCB.

Ocena
0 / 5
Polubienia
2
Pobrania
2
Wydruki
0
Wyświetlenia
32
Oceny
0

Aktualizacja u źródła:

Informacje o modelu

Źródło
Printables
Kategoria
Electronics
Licencja
Creative Commons — Attribution — Noncommercial — Share Alike

Wall portal for a custom ESP32-S3 board: 4×3 keypad, 240×135 IPS, RC522, speaker, reed contact, and a handle-mounted MPU6050. PETG profile; Gerbers and firmware come with the full system.

The inside of the door is where Guardian actually decides.

This PETG set is the Interior Portal from Guardian System: a Home Assistant tree plus two ESP32 devices. Every card scan — here or at the outdoor doorbell — goes through one decision path. A valid tap opens a timed passage window; a door that opens inside it is intentional, outside it is not. Direction is classified from the lever IMU first, reader intent second, confirmed door swing third. Cloned cards are caught with a rolling counter on NTAG21x. Elevated mode can ask for card and master PIN before a siren, instead of waking the house for a forgotten scan.

This listing is the printed portal: keypad, 240×135 status display, RFID, spoken prompts and siren through a DFPlayer, a reed on the leaf, and an IMU that clips onto the handle so a lever twitch is not the same event as the door moving. It is designed around a hand-soldered custom PCB and an ESP32-S3 DevKit. Firmware is built for 8 MB flash / octal PSRAM. A 32 MB Waveshare module still runs that build; do not change the firmware flash size to 32 MB if the chip is 8 MB.

There is no pick-and-place / CPL. Send the Guardian Interior Portal Gerbers to a proto fab, or hand-solder from the KiCad project. GPIO comes from ESPHome (portal-unit.yaml), not from silkscreen connector numbers.

In this profile (Internal-Portal-Final.3mf)

Main-Body, Wall-Mounting, Display-Cover, Display-Housing, Keyboard-Housing, Speaker-Housing, Top-Screw-Cover, Door-Sensor-Housing1, Door-Sensor-Housing2, MPU-6050-Housing, MPU-6050-Housing-Cover.

There is no separate Top-Cover. The cosmetic cap that hides the front screws is Top-Screw-Cover. Print as supplied, PETG. Supports are already in the models.

Github Repository: https://github.com/AntonisPsarras/guardian-system

Also in this upload: the assembly PDF — PCB populate order, keypad pin table, display and speaker frames, RFID in the body, wall-plate sequence, reed and IMU, DFPlayer track names.

What you still buy

Qty

Part

Notes

1

ESP32-S3 DevKit

8 MB flash / octal PSRAM in firmware. USB-C toward the keypad header.

1

MFRC522 (RC522)

13.56 MHz. Use NTAG21x; Classic is clonable.

1

MPU6050 / GY-521

Clips on the lever. May need CAD tweaks for your handle.

1

DFPlayer Mini + FAT32 microSD + small speaker

Card is wired to the DFPlayer, not the ESP32. Changing a sound means opening the portal.

1

4×3 matrix keypad

7-pin harness. Firmware rows GPIO4 / 7 / 6 / 5, columns GPIO1 / 2 / 15.

1

1.14" 240×135 ST7789 IPS (SPI)

Status UI.

1

Reed switch + magnet

Frame half and leaf half in this same profile.

3 + 2

220 Ω and 1 kΩ axial THT

Plus 1000 µF 10 V radial, polarised, + marked on the board.

~20

M3 inserts 5.7 × 4.6 mm

Main body and wall plate.

—

Headers

2× 1×22 female (ESP32), 4×1 male (keypad), 3× 1×2, 3× 1×4, 2× 1×8 female (DFPlayer), 2.54 mm. Or solder modules down.

1

5 V supply

Sized for S3 + DFPlayer + display.

optional

5 mm RGB, common anode

Status / bring-up.

Build order that actually works

  1. Solder headers, resistors, and the capacitor (polarity). DFPlayer SD slot toward the capacitor; ESP32 USB-C toward the keypad header.

  2. Speaker: two wires through the printed grille, tape the driver in.

  3. Display: the printed top panel goes on before the module is screwed into its shell; reuse the module’s standoff screws.

  4. Keypad: solder from the back. Slide it in the printed frame so pins emerge for the harness. Optional M2 screws to stop it walking.

  5. If keys read wrong after a flash, the harness is swapped — do not edit firmware to match a miswired cable.

  6. Melt inserts in the main body and wall plate. RFID screws to the side inserts. Reed and IMU cables leave through their holes; MPU 3V3 is the top pin on that header. Reed orientation does not matter.

  7. Mount the wall plate first (screws or tape). Screw the body to the plate, then screw the PCB down. Add keypad, display, and speaker modules. Friction or tape holds Top-Screw-Cover.

Fit. Most of the set fits a typical door. The MPU housing and reed pair are the parts that may need a CAD tweak for your hardware. This listing is the print profile; there are no STEP sources here.

Sound card (FAT32, folder MP3 at the root, four-digit names)

File

What it is

/MP3/0001.mp3

Doorbell

/MP3/0002.mp3

Access denied

/MP3/0003.mp3

MFA / PIN challenge

/MP3/0004.mp3

Alarm (networked and local siren)

/MP3/0005.mp3

Welcome / granted

Firmware uses play_mp3 by filename. Dumping files in the card root and using plain play is how an earlier card played the alarm as a chime. Volume is set to 30 (module max) on boot. MP3s are not in this upload.

Siblings in this collection: Doorbell (second RFID, outside, XIAO ESP32-C6) and Door lantern (Tapo C110 + L530E, no PCB). GPIO, Gerbers, and Home Assistant logic live with Guardian System, not inside the .3mf. Print files and CAD; the software tree is MIT.

This is not a finished commercial alarm, a pick-and-place board, or a reader you flash with random ESPHome YAML. The portal’s local siren is firmware on this hardware; treat Wi-Fi and power as part of the design, not as optional extras.

Tagi