Features Wishlist

input_text keyboard popup

Mattias314Suggested this wish ·

Hey! I have a use case where I need a popup keyboard in order to edit an input_text entity. I believe LVGL already has a keyboard built in.

Would it be possible to add this as well?? Thank you!!

Discussion 5

Add a comment
MaxGramser

Can you explain a big more how you use this with an example entity or use case? Thanks!

Original on GitHub

Mattias314

I currently have a touchscreen with custom made esphome code that has a text field, if I tap on the field a keyboard pops up. I can then edit this text and clear the keyboard. This is configured so that from the touch screen, I can update and display the code elsewhere.

I have this text just showing as a device sensor in Home Assistant. However, it may be better to have it directly edit and update a Home Assistant input_text entity instead.

Image

Original on GitHub

lainol

· Edited

Can you explain a big more how you use this with an example entity or use case? Thanks!

Alarm control panel. To enter code to arm/disarm.

Original on GitHub

MaxGramser

A progress note for the alarm use case mentioned above: version 0.3.8 of the app (screen firmware 0.3.3) adds an alarm panel. That release is going through its last tests now and will be out later today. An alarm_control_panel entity can now be a tile on any screen. A tap opens a card with the modes your panel supports (home, away, night, vacation, custom bypass) and a key to disarm. When the panel needs a code, the screen shows a number keypad first, the way Home Assistant's own code dialog does, and sends the code with the action. A default code stored with the entity in Home Assistant means the screen asks for none. When someone comes in (pending) or the alarm goes off (triggered), the screen wakes up with the keypad open. Three wrong codes lock the keypad for 30 seconds, doubling up to 15 minutes, and every wrong code fires an esphome.screen_alarm_code_refused event you can use in an automation.

Number codes only for now. A full keyboard for text, which is what this issue asks for with input_text, is not in this release, so I'm leaving the issue open for that part. Update the app, then the screen's firmware, before you add the alarm tile.


Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.

Like my work? Consider buying me a coffee, much appreciated!

Original on GitHub

MaxGramser

Thanks @Mattias314! This is better suited to a discussion than an issue, so I moved it here: https://github.com/MaxGramser/homeassistant_espscreen/discussions/112

Please continue the conversation there. I'm closing this issue to keep the tracker for bugs and concrete board requests.


Got a screen running? Tell others which board you have and what works on the Tessera website. It helps everyone pick a screen that works.

Like my work? Consider buying me a coffee, much appreciated!

Original on GitHub

Add your thoughts, a screenshot or a useful link.

Markdown & basic HTML
Paste or drop images · URLs on their own line become previews0 / 10,000
Sign in with GitHub to commentYour draft stays in this browser tab.