esphome / esphome/feature-requests
I2C discovery timeout
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
I want the I2C discovery to time out after a few minutes if the I2C lines don't clear and the firmware continue to run, and preferably an error message to be shown in the logs.
**Please describe your use case for this integration and alternatives you've tried:**
Currently if the I2C discovery is on and something (eg. faulty sensor as was in my case) pulls either line low the firmware never reaches the point where it's accesible via the api. Luckily it's still flashable over the air.
When the sensor failed, and I tried reflashing the esp, it was unreachable through the api. After trying renaming, debugging DNS, I removed the faulty sensor. ESP was reflashed and working once again.
**Additional context**
If there is a timeout, it's too long for me to wait out...
Contributor guide
No contributing guide indexed for this repository
Research direction
No source file, test, or entry point is named in the request. Start by locating the I2C discovery flow and how stuck lines are handled, then trace firmware logging and API startup behavior. Done means discovery stops after a bounded timeout, an error appears in the logs, and the firmware remains accessible.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100