Cannot set `unique_id` option for `input_*` integrations

[DDvO]

The problem

For some reason, for all input integrations (https://www.home-assistant.io/integrations/#search/input_) it is not possible to set a unique_id (like it can be done for basically anything else that can be shown in the overview/dashboard).

When trying to do so, one gets for instance

Invalid config for [input_boolean]: [unique_id] is an invalid option for [input_boolean]. 
Check: > input_boolean->input_boolean->sunshine_period->unique_id. (See /config/configuration.yaml, line 546). 

This implies that the inputs cannot be managed on the UI (for instance, to set/change their icon).

What version of Home Assistant Core has the issue?

core-2023.11.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

input_boolean:
  charge_enabled:
    name: Charge enabled
    unique_id: charge_enabled_id
    initial: "on"

### Anything in the logs that might be useful for us?

_No response_

### Additional information

_No response_

[mib1185]

https://www.home-assistant.io/integrations/input_boolean/#configuration Just setup the helper via the UI, so they get unique ids

[DDvO]

Thanks for this hint - indeed it is possible this way to define inputs. Yet still I see no reason why this is not supported at YAML level, which is the fundamental way of defining entities. Moreover, the GUI way of defining them is not suitable when sharing a configuration with others - there YAML makes most sense, where also any automations etc. are defined that use such inputs.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.