esphome / esphome/feature-requests

Option for `copy` platform not to mirror back changes to the source

Open
#1,765 1 comment 0 reactions 0 assignees View on GitHub
component: copy
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**
[Copy integration](https://esphome.io/components/copy.html) is excellent, one option is needed, to prohibit forwarding actions such as turning on back to the source.
Something like `feed_back` optional, as `true`/`false`, default `true` to keep current behavior id not specified.
Applicable only to interactive components (not applicable to sensors).

**Please describe your use case for this integration and alternatives you've tried:**
This would be very useful in more complex cases when one wants to make state changes to the source but not immediately, but on a later stage, and wants to skip intermediate changes. This could be feasible with an `on_value` action set to the copy.

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the linked Copy integration documentation and trace how interactive components forward actions back to their source. Define the behavior for an optional feed_back setting, preserving the current default and excluding sensors; no implementation files or tests are named in the request, so identify those before estimating the change.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.