Feature Request: Hardware screen wake-up and message display on RX (LILYGO T-LoRa V2.1-1.6)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- c
- 领域
- embedded-iot
调研方向
Start by locating the RX packet handling and OLED sleep or wake entry points for the LILYGO T-LoRa V2.1-1.6 and similar boards; the issue does not name source files or tests. Check how decrypted message text reaches the display and whether a configurable timeout can fit the existing hardware configuration. Done means an RX message wakes the screen, shows its text, and turns the display off after the configured interval.
由索引模型根据 Issue 内容生成。
描述
Is your feature request related to a problem? Please describe.
Currently, on the LILYGO T-LoRa V2.1-1.6 (and similar nodes with built-in OLEDs), the screen acts primarily as a static telemetry panel. When a new message arrives, the physical display does not wake up to show the content. Users are forced to rely on the connected mobile app or CLI terminal to read the incoming text.
Describe the solution you'd like
I would like to request a hardware configuration parameter that wakes up the physical OLED screen (SSD1306) upon receiving a new RX packet and displays the decrypted message text for a configurable amount of time (e.g., 20 seconds).
Proposed functionality:
- Introduce a parameter accessible via the node's internal CLI (e.g.,
cli config set display.screenOnSecs 20). - When an RX packet is processed, trigger an interrupt to wake the screen from sleep, show the message, and then automatically turn off the display after the configured timeout to save battery.
Describe alternatives you've considered
Currently, the display: parameters in meshcli (like print_timestamp or color) only manage the local terminal output formatting on the host machine, not the physical hardware screen. The only alternative is keeping a smartphone connected via Bluetooth at all times or building external GPIO-triggered LED notifications via custom Python scripts listening to the CLI output.
Additional context
Hardware details:
- Board: LILYGO T-LoRa V2.1-1.6
- Screen: 0.96" OLED (SSD1306)
Adding this feature would allow Companion/Repeater nodes with small displays to function as true standalone pagers, greatly improving usability in the field without relying on a smartphone.
- 主要语言
- C
- 星标
- 3.9k
- 派生
- 1.5k
- 平均合并
- 19 小时 9 分钟
- 30 天内合并 PR
- 27
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
meshcore-dev/MeshCore 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
meshcore-dev/MeshCore#3622 ·
维护者通常 1 天内回复
-
[Feature Request] Set Australia (Mid) Preset to automatically enable 2 byte default path hash size未关闭
难度 2/5 1-3 小时 新手友好度 62/100
meshcore-dev/MeshCore#3571 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
meshcore-dev/MeshCore#3567 · 1 条评论 ·
维护者通常 1 天内回复
-
RTC_RX8130CE writes and reads the one-hot WEEK register as a number可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
meshcore-dev/MeshCore#3549 ·
维护者通常 1 天内回复
-
Repeater: CLI reply to 'setperm <key> 0' is lost when the removed ACL entry sits before the requester (stale ClientInfo* after array shift)可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 77/100
meshcore-dev/MeshCore#3513 ·
维护者通常 1 天内回复
查看 meshcore-dev/MeshCore 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
quickjs-ng/quickjs#1836 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
open-quantum-safe/liboqs#2637 ·
维护者通常 1 天内回复
-
Go device SDK: Whisper transcriber keeps buffering and transcribing audio appended after Stop()可能已有人在做 @apoorvdarshan 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
BasedHardware/omi#22770 ·
维护者通常 1 天内回复
-
fido_do_ecdh() reports any getKeyAgreement failure as FIDO_ERR_INTERNAL可能已有人在做 @brlumen 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
joncampbell123/dosbox-x#6698 ·
维护者通常 1 天内回复