-
Notifications
You must be signed in to change notification settings - Fork 32
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
Discovered entities with a name that starts with the device name #282
Comments
I am seeing an error related to this. Will it be updated? |
Yes, as soon as I am able to. |
We love you! |
Thank you for the work on this! Really appreciate it! |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Not stale |
@FunkeyFlo Can you make a release and new docker image containing this PR? |
Yeah, sorry it's taking so long. I was hoping to combine it with some other much anticipated features but we've just found out we're having twins and everything is totally bonkers right now. So I'm having trouble finding the time. I'll try and release it this weekend. But no promises! |
Congratulations! |
Congratulations and strong nerves :) |
Any update on this? Still getting the same error |
Any update on this? Feb 2024 Home Assistant update will release in a few days and I won't be able to update until this issue is addressed. |
Description of the issue
Some MQTT entities have an entity name that starts with the device name. This is not expected. To avoid a duplicate name the device name prefix is stripped of the entity name as a work-a-round. Please inform the maintainer of the software application that supplies the affected entities to fix this issue.
https://developers.home-assistant.io/blog/2023-057-21-change-naming-mqtt-entities/
List of affected entities:
Addon version
1.3.1
Platform
Core: core-2023.8.0b3
Supervisor: supervisor-2023.07.3
Operating System: Home Assistant OS 10.4
Logs of the issue (if applicable)
No response
The text was updated successfully, but these errors were encountered: