FLchs
December 9, 2024, 5:30pm
1
Where the heck are those lights
Would be awesome to have a way to know the area of devices, it forces me to add the area in the device name but then if I move it I’m lost (I had the kitchen light in my living room for a while before I finally decided to change its name…).
potelux
December 9, 2024, 5:31pm
2
Be sure to vote for your own post
1 Like
petro
December 9, 2024, 5:58pm
3
edigorn
December 12, 2024, 10:50am
4
Great point about making it easier to identify the location of a device! Taking this idea a step further, I’ve proposed a WTH: Entity Name Templates with Automatic Updates that allows users to include room names (and much more!) directly in entity names. This way, you can define a consistent naming template once and let Home Assistant handle the rest automatically.
Imagine names like “Living Room - Climate - Thermostat - Netatmo - 1” being generated seamlessly for all your devices, while also offering tools to update existing entities to match your template. It’s a dream come true for organizing large setups!
Check out the full proposal and cast your vote here: WTH: Entity Name Templates with Automatic Updates
Let’s make naming and managing entities in Home Assistant a breeze!
Thankfully this is been worked on
home-assistant:dev ← home-assistant:entity_name_more_info_dialogs
opened 01:59PM - 11 Sep 24 UTC
## Proposed change
An attempt to improve more info dialog for entities.
For … now it uses the backward compatibility with `friendly_name`. We should use entry registry for that but `has_entity_name` should be exposed in `EntityRegistryDisplayEntry` for that.
Needs https://github.com/home-assistant/core/pull/125832
### More info dialog
With device and area
Using device name as entity name (or empty entity name)
No device, no area
### Entity picker
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] 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
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] 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:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
## Summary by CodeRabbit
- **New Features**
- Introduced utility functions for computing area, device, and entity names, enhancing clarity and usability in the application.
- Updated the `MoreInfoDialog` to display more structured information, including device and area names alongside the main entity name.
- **Bug Fixes**
- Improved error handling for name retrieval, ensuring robustness when accessing area and device names.
- **Style**
- Enhanced visual layout of the `MoreInfoDialog` with updated styling for title and subtitle presentation.
