esphome / esphome/feature-requests
I2C qwerty keyboards as pin pads or as additionary buttons to trigger automations
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
It could be fun and maybe useful to have a phisical pad or keyboard attached to the ESP32 board, to use to unlock pin-locked home assistant components, password-protected garage doors, or just as phisical buttons to trigger automations.
The following two are examples of small and cheap qwerty keyboards, both integrable via I2C.
https://m5stack.com/collections/m5-unit/products/cardkb-hat
https://m5stack.com/products/cardkb-mini-keyboard
**Please describe your use case for this integration and alternatives you've tried:**
Password-locked doors or armed alarms could be opened typing the correct password / OTP by a person that have no access at all to home assistant and/or network.
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are mentioned. Start by reviewing the ESPHome feature-request process and existing I2C component support, then determine the scope for supporting the linked M5Stack keyboards and their password or button automation use cases. Done should include an agreed integration design and validated behavior for the requested keyboard input.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100