-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Remove naming warnings and work-a-rounds for incorrectly configured MQTT entities #107188
Conversation
Hey there @emontnemery, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
The link to the blogpost doesn't work anymore 🤔 |
It didn't work because we don't have 57 months. I edited the link :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @jbouwh 👍
CI failures are not related to this PR. |
Link was updated |
Breaking change
When an MQTT entity has a device name that is equal to the entity name, or starts with the device name, this will no longer be corrected. When entities like these are created they will have both device and entity name in the friendly name. If the device name is to be omitted because it is the same as the entity name, then the entity
name
attribute sould be set tonull
in the JSON payload or YAML config.Related blogpost: https://developers.home-assistant.io/blog/2023/07/21/change-naming-mqtt-entities
Proposed change
Remove work-arounds, warnings and issue registrations for temporary fixing naming issues with MQTT entities.
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: