esphome / esphome/feature-requests

Group esphome configuration in HA

Open
#2,622 1 comment 0 reactions 0 assignees View on GitHub
Project: Dashboard
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**

Having a lot of ESPHome devices can create problems when mass updating.
It would be nice to be able to group them in folders (for example Sensors, Switches, etc) so that I can update a category at a time.
Also, finding a specific configuration file that i have to update or change is annoying as i have to go thru all or search for it.
Having this feature means that i can also put all of the unused config files in a folder that i don`t need to see them, but also not lose the configuration for them.

**Please describe your use case for this integration and alternatives you've tried:**

use-case is when i update my esphome nodes, it takes a really long time, and the window starts lagging as it has to be opened for about 30 minutes and gets slow as time passes.
Would like to have a folder called Switches where all my switches configurations are and another one for sensors when all the sensor configurations are. I would also like to be able to enter the switches folder and just update all of them and then go to the sensors folder and be able to update them as well.
As a current workaround i have imposed a naming convention so that the names are descriptive and also keeps the switches and sensors together. The nodes that do not support easy OTA (like my sonoff rfbridge with not enough flash) have a DO NOT COMPILE on the first line so that it cannot generate code and be flashed.

**Additional context**

having folders or groups where we can enter and see only a part of the config files would be awesome.

Contributor guide

No contributing guide indexed for this repository

Research direction

The request concerns grouping ESPHome configuration files and updating groups of nodes, but it names no source files, tests, or entry points. Begin by locating how configurations are listed and mass updates are initiated, then define folder behavior and update scope. Done means users can organize configurations, hide unused ones, and update a selected group.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.