[Feature request] Optional BLE repeater observer transport with bounded queues
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- c, github
- 领域
- embedded-iot
调研方向
Read the proposed implementation at https://github.com/throny/meshcore-ble-observer and its source/provenance tooling, then review MeshCore's CONTRIBUTING guidance for the maintainer discussion. The request leaves API boundaries and PR split undecided, and validation is incomplete across long duration, RF, energy, recovery, security and other hardware. Done means maintainer agreement on scope and boundaries before a feature PR.
由索引模型根据 Issue 内容生成。
描述
Problem
A repeater observer normally needs a permanent USB connection to forward the
repeater's own packet observations to a host. A nearby Companion observes its
own RF reception, not the repeater's internal observations. An opt-in BLE export
would support installations where a permanent USB data cable is impractical.
Proposed approach
- Default-off repeater observer feature selected through a separate custom build
target; no automatic replacement or update of stock firmware. - Physical enrollment, bonded/encrypted BLE, one pinned observer peer and explicit
revocation. No automatic or open enrollment after reboot. - Bounded packet/log callbacks, record queues and fragmentation with session and
sequence identifiers, complete-record ACKs and explicit loss counters. - ACK means host RAM reassembly, not MQTT delivery; no lossless/durable replay
claim. RF forwarding must remain the primary responsibility. - Shared protocol/queue primitives, with an initial nRF52/SenseCAP Solar P1-Pro
binding. Other boards need reviewed transport bindings and actual validation;
no generic cross-board compatibility claim.
An experimental implementation, source/provenance tooling and independently
maintained optional meshcoretomqtt BLE adapter are at:
https://github.com/throny/meshcore-ble-observer
Validation and limits
The current implementation cleanly replays against official repeater-v1.18.0.
Hosted CI builds the custom image and runs native/exact-source tests. Initial
P1-Pro/Linux-host checks exercised identity-preserving application updates,
bonded BLE packet reception, parsing and MQTT connections. Long-duration,
matched RF, energy, recovery and full interruption/security acceptance remain
incomplete; other hardware is unvalidated. This is not an official release or
an unattended/solar-readiness claim.
Following CONTRIBUTING, this issue seeks maintainer agreement before a large
feature PR. Would you consider this as a default-off repeater capability, and
what API boundaries/PR split would you prefer before a port to dev?
- 主要语言
- C
- 星标
- 3.9k
- 派生
- 1.5k
- 平均合并
- 1 天 3 小时
- 30 天内合并 PR
- 24
环境准备
这个项目没有提供开发容器、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 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
meshcore-dev/MeshCore#3513 ·
维护者通常 1 天内回复
查看 meshcore-dev/MeshCore 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 67/100
espressif/esp-vision#16 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
libsdl-org/SDL#16577 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
halt_error adds a trailing newline for non-string input, contrary to the manual可能已有人在做 @Huang-404-Q 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
MerginMaps/geodiff#272 ·