esphome / esphome/feature-requests

Default substitutions when using dashboard_import

Open
#1,726 0 comments 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**
I've created a custom firmware project in the recommended way, and I'm using `dashboard_import` to allow devices running it to easily show up in the dashboard. However, the only substitution that shows up in the file esphome creates in the dashboard is `name:`. I've got quite a few configuration options for the project stored in substitutions. It seems like there should be some way for these substitutions to be imported into the file esphome creates, or at the very least some way to hint that more configuration options exist.

**Please describe your use case for this integration and alternatives you've tried:**
Allow a way for projects to specify which substitutions should be created by default in imported device files.

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how `dashboard_import` generates the ESPHome device file and how project substitutions are currently handled. Determine the intended way to declare default substitutions or signal additional configuration, then add coverage for the generated imported file and verify the requested defaults appear.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.