Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand error msg on why yaml defined entities can't be changed from UI #6689

Merged
merged 7 commits into from
Sep 30, 2020
Merged

Conversation

mrand
Copy link
Contributor

@mrand mrand commented Aug 24, 2020

Proposed change

Many users find the "This entity does not have a unique ID, therefore its settings cannot be managed from the UI" message too cryptic.
Here is one of several threads: https://community.home-assistant.io/t/this-entity-does-not-have-a-unique-id-therefore-its-settings-cannot-be-managed-from-the-ui/182307

I know my proposed wording might not be ideal, so open to other wording!

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

@bramkragten bramkragten merged commit 2616281 into home-assistant:dev Sep 30, 2020
@mrand mrand deleted the patch-1 branch September 30, 2020 13:45
@bramkragten bramkragten mentioned this pull request Sep 30, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jul 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants