Buttonless boards have no way to reopen the pairing window once a phone is bonded
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- embedded-iot, security
调研方向
Read docs/ble.md and the changes discussed in #9, #18, and #46 to understand the current pairing-window behavior. The issue proposes several possible recovery paths, including a new system command, a physical action, authenticated pairing, or app guidance, but does not choose one. Done means a buttonless board can add, replace, or remove phones without erasing flash while preventing strangers from opening the pairing window.
由索引模型根据 Issue 内容生成。
描述
Part of #9. Follow-up to #18 / #46.
Problem
- Since #46, a board without a pairing button (e.g. the WiCAN) opens the pairing window at boot only while no phone is bonded. Once a phone is bonded, nothing can open it again.
RemovePairedPhone/ClearPairedPhonesalso need an open window, so a buttonless board can't manage its phones at all after first setup.- If the owner's phone loses its bond (forgotten in Android's Bluetooth settings, app reinstalled, new phone), it's locked out. With the window closed the device advertises without its name or service UUID, so the app doesn't even find it. Tested on a WiCAN with #46: the phone reconnects as a known identity but never re-encrypts, and no bond is stored.
- The only recovery today is erasing the flash over USB.
Ideas
- A deliberate action that opens the window:
- a system command from a bonded phone (needs a new message in contracts);
- a physical action, such as unplugging and replugging the device a set number of times within a short time.
- Use authenticated pairing (passkey or numeric comparison) where the hardware allows it, e.g. a code shown in the app and confirmed with a pattern on the device's LED. This was an idea in #18 and goes away when it closes.
- In the app, when a previously paired device isn't found, explain the recovery instead of scanning forever (mobile-app side, like OpenCarControls/mobile-app#42 for the reverse case).
- Update
docs/ble.md, which currently says "such a board is reset by erasing its flash".
Done when
The owner of a buttonless board can add, replace or remove a phone without erasing the flash, and a stranger near the car still can't open the window.
- 主要语言
- Rust
- 星标
- 1
- 派生
- 0
- 平均合并
- 11 小时 26 分钟
- 30 天内合并 PR
- 18
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenCarControls/firmware 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 51/100
OpenCarControls/firmware#68 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
OpenCarControls/firmware#55 ·
维护者通常 1 天内回复
-
First-setup pairing window is too short and stays open after the first bond可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 55/100
OpenCarControls/firmware#53 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
OpenCarControls/firmware#51 ·
维护者通常 1 天内回复
-
e-gmp
难度 3/5 1-2 天 新手友好度 55/100
OpenCarControls/firmware#43 ·
维护者通常 1 天内回复
查看 OpenCarControls/firmware 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
farion1231/cc-switch#8829 ·
维护者通常 1 天内回复
-
bug ci good first issue
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
longbridge/gpui-kit#3677 ·
维护者通常 1 天内回复
-
E-pr-welcome
难度 2/5 1-3 小时 新手友好度 77/100
seanmonstar/reqwest#3121 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
ilya-zlobintsev/LACT#1235 ·
维护者通常 1 天内回复