Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Buttonless boards have no way to reopen the pairing window once a phone is bonded

Abierto
  • ¿Algo no está bien?
#54 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
embedded-iot, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement

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 / ClearPairedPhones also 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.

Lenguaje dominante
Rust
Estrellas
1
Forks
0
Merge medio
14 h 32 min
PR fusionados (30 d)
21

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenCarControls/firmware

Todos los issues de OpenCarControls/firmware

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.