esphome / esphome/feature-requests
Always update wirelessly from the editor? Present other options later.
- 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**
When creating a new device, I often play around with the config and often have to send it to the device to try it out. With the new dialog "Pick Install Target" there is an annying extra step, since in most of the cases you'd update wirelessly.
I could imagine two solutions:
1. Adding an extra button in the editor (or add a dropdown for the other options)
2. Always try to upload wirelessly and only if it can't connect to the device, present the other options to the user.
Option 2 would be the most user friendly way, because it doesn't overwhelm the user with these many options if it's not necessary.
Mockup:

**Please describe your use case for this integration and alternatives you've tried:**
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the editor's “Pick Install Target” flow and how wireless updates are initiated. Compare the two proposed behaviors in the issue and define which fallback experience is intended; done means the common wireless-update path avoids the extra target-selection step while other install options remain available when needed.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100