I apologise. The wording in my previous message was not clear enough. I have no issue with the name. The problems I see are with entity ids:
light.0xa4c13813d36a0ff5)69505d59e417ebdfa5be4316822b10f9) even though elsewhere HA claims the entity id is light.garage_energy.That just seems odd to me.
Yes, that is not a normal sort of entity id, which is usually in the form of domain.instance (like light.front_door)
I’ve been reading for about an hour and confused by this: I use esphome for a lot of sensors created by the non-API MQTT connection.
Is it my responsibility to fix something (and if so any hints?) or is there going to be a new esphome? All the discussion is about z2m and “other” software, but I can’t figure out if I need to change my code or esphome will get a new version?
Here’s a typical entity that it complains about (if I should be changing something):
light:
- platform: "tuya"
name: "master_bedroom_hall"
switch_datapoint: 1
Then this change isn’t impacting you, and you need to start a fresh topic and share the errors.
Just updated to 2023.8.1 and I have already duplicated names shown without any manual or automatic fixing.
So both the warning and the message in the OP of the topic is incorrect. And I am not talking about devices which I just installed, but devices which I use for years.
This change is as nonsense and confusing as much the last renaming round was with the Fronius integration, which caused human readable Entity names to turn to be 256 character long ones which cannot even be displayed normally. The same story with this…
That’s normal and unrelated to this change. That was a change in device triggered, conditions, and actions. You can use entity_id or it’s config entry id.
See my comment above, it’s normal (as of a few versions ago) for device based triggers, actions, and conditions.
Can you post images of the device page please?
@petro, device page and the entity page:
Device page show without Device name, Entity page shows with Device name added…
I have an old Tasmota as well which did the same, but I changed the name already. It was a duplicate name of the Device/Entity.
It is just generally crazy to create these extremely long Entity names which cannot be displayed anywhere correctly.
This is how it looks on a dashboard:
It was exactly the same with the Fronius integration. Long Entity names, which cannot be displayed and read, and all were updated even it was told, that previous naming will not change.
Yes, this is normal behavior. It’s not a duplicate name. A duplicate name would be XYZ XYZ abc where XYZ is the device name and abc is the entity name. Your device name in this instance is Layzspa Wifi Controller and your entity name is Layzspa airbubbles. So the resulting name you’ll see on the dashboard is Layzspa Wifi Controller Layzspa airbubbles. In the devices page and autogenerated UI’s the device names are hidden from the entity names. This behavior is across all of HA and was recently introduced to MQTT.
And lastly, this did not affect your entity_ids. Meaning my last statement is still correct, your devices, automations, and scripts are still working.
But why has it had to update all the displayed names, which was already in use? Everybody is talking about newly discovered devices. This one is in use for a year, already discovered. It just makes hours of work to update names to be able to display them nicely in a readable format on any dashboard.
This is not user friendly at all that every other release you have to redo all the dashboards, even without using any customisation.
This is not increasing the WAF, the most important user friendliness factor. It just takes away more and more time and pisses off the wife…
Again, I didn’t make the change, so quit bitching at me. If you want to make decisions in HA, you’re more than welcome to join the discussions on github, just don’t go into the discussions with the attitude that you have because you will be ignored.
It was not bitching at you, as you always feel offended when one has a different opinion.
This whole process is worse then ever regarding communication.
I avoid discord, because you get the least amount of help. Even for a simple question, when you cannot find a straight answer on the forum.
And unfortunately that lack of help, and attitude of “this is an open source project, you can make a PR/write your code/join the beta” brings people to try to solve problems with ChatGPT, etc…
I came here as everyone else who had those warnings and read through the whole topic.
It is lovely to read the warning with an uncurated list of entities which cannot be reproduced elsewhere. (I have 103 devices with 867 entities)…
It is great that you made a PSA, but things are not communicated clearly. Two admins trying to firefight the miscommunication, meanwhile this should be already a blog post and the warning message should have been updated in the latest release.
Name changes should not happen at any level, without user interaction if they have been already in use.
And if NabuCasa is trying to be more user friendly and streamline thing then it shouldn’t make a change which causes that a PSA topic is created with more than 200+ posts.
But please complain about my attitude and do not discuss these things on the next NabuCasa meeting, because it would be too hard in the subject of user friendly changes…
And this shows you didn’t even read the thread. Nabucasa didn’t make the change. And the discussions on github are open to everyone. The only persons you can blame here are volunteers, because yes, this is open source. Shocker.
You want change?
Thanks, I will do so, though “this change isn’t impacting you” seems a bit at odds with the big warnings that pop up now after restarts. But everything is working (other than warnings) and I will post a separate topic, thanks.
The Tasmota alternative ESPxx firmware moved away from HASS Discovery to Tasmota Discovery as the alternative significantly reduces memory usage with a single config string payload (and nice stuff like set the device location in Tasmota for auto-discovery - i.e. set up the device; not HASS).
Tasmota discovery works well and includes units for long term stats (e.g. DS18x20 temperature sensors).
SetOption19 0 (default for all recent releases)Now, the status of the HASS Tasmota integration and the new Entity Naming Standards is a different issue which I’ve not tested in detail (an initial look on a minimal install suggests the core is OK, but additional custom sensors / switches might need tweaks).
EDIT: After some more testing, current Tasmota v13.0.0 and HASS 2023.8 using Tasmota Discovery names entities by concatenating Device Name + Friendly Name 1. If you have several endpoints (e.g. multiple relays, switches, sensors) there can be several Friendly Name x which makes more sense than with only one where it’s not as clear which is which.
TL;DR - Try setting Device Name = “S26” (hardware device or blank), Friendly Name = “Kettle” (thing controlled) and you’ll likely see “S26 Kettle” in HASS.
Thanks for the clear communication about this! Saw the warnings, freaked out a little, searched the problem and landed here. Will be waiting until zigbee2mqtt updates later this year before worrying again.
I mentioned esphome and someone said open a new topic, but I figured out a solution and I think it speaks to the warnings maybe being over-stated so hope this is on point.
In my esphome setup I would have a device like hall_light (in that case with underscope) and would put the name attribute the same, hall_light. The warning appears.
The fix in this case was to make the name “Hall Light” which resulted in the same entity name (it downcases and unscores it, not sure what “it” is that does it).
Other devices I had specifically added the device name to the entity name, e.g. hall_light_led and got a different warning about name prefixed by devices - but that was on purpose. I had to make a similar change (Hall Light LED) to get the warning to go away.
I’m not certain, but I think maybe the naming checks are capturing some false positives from other integrations. Maybe. I fixed all mine, I’m happy and moving on, but adding this note in the hopes it helps someone since this seems the main naming thread.
When will this be fixed? The device name is the name of the manufacturer, not the name of the entity
@Daw34, your posts are getting hidden because you aren’t using english. Please translate your comments to english before posting.