lost connection
- Dominant language
- JavaScript
- Stars
- 20
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
followed instructions on flash.comma.ai
port 1 cable is my Comma 3X's OBD-C.
## Bug Report - flash.comma.ai
**Device:** comma four
**Serial:** N/A
**Error:** LOST_CONNECTION
**Step:** CONNECTING
**Last Message:** N/A
**OS:** Linux
**Sandbox:** None detected
**Browser:** Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36
**URL:** https://flash.comma.ai/
**Time:** 2026-08-08T00:24:01.285Z
Console Logs
```
[2026-08-08T00:23:45.605Z] [info] flash.comma.ai version: 2a2da7f
[2026-08-08T00:23:45.947Z] [info] [ImageManager] Initialized
[2026-08-08T00:23:55.238Z] [error] [Flash] Connection error {}
[2026-08-08T00:23:55.240Z] [debug] [Flash] error 4
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the flash.comma.ai connection flow and reproduce the reported LOST_CONNECTION error at CONNECTING with the Comma device on Linux. Use the supplied console logs, including the [Flash] connection error and error 4, to trace the failure; done means the connection succeeds or the failure is diagnosed with a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux
- Domain
- embedded-iot, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100