There are other posts about openhome in this very thread.
yes dont see it, thanks you are right.
But with one fifference: no one is using Linn / Openhomeā¦
I need it.
I hope it is supported anymore, all other are only dirturbed because of the error messageā¦
i am afraid of losing this funtionality because its only installed 62 times.
unfortunately this has happened many times before.
I did use Linn Kazoo/Openhome, but changed that recently for Volumioā¦
Even after long time no more Openhome use, is get this error after every restart.
Logger: homeassistant.setup
Source: setup.py:298
First occurred: 11:45:17 (1 occurrences)
Last logged: 11:45:17
Unable to prepare setup for platform openhome.media_player: Platform not found (cannot import name 'UpnpFactory' from 'async_upnp_client' (/usr/local/lib/python3.9/site-packages/async_upnp_client/__init__.py)).
So there definitely is something wrong with openhome, started with 2022.4.0
@petro We already have the core-2022.4.2 version. When can we expect the implementation of Tuya correct scaling by starkillerOG Ā· Pull Request #69348?
Whenever it passes review after the reviewed changes are made. Just watch the PR and see when itās merged and itāll most likely show up in a version after itās merged. There are no time tables for things like this, so thereās no reason to ask in the future. You just have to wait until the work is finished.
That behavior still exists in groups in the group domain. Binary_sensor groups never existed prior to this release, this is a new feature. They act the same was as light groups do, but they are for binary_sensors. Light groups also never had this functionality.
If you want that functionality, keep your group thatās in the group domain (in yaml).
You just have to wait until the work is finished.
only that the job is already done and the only obstacle to implementation is that the person who caused the bug doesnāt want to admit it.
Why does that matter? Mistakes happen. Thatās life. Wait for a fix or downgrade.
4 Likes
I guess I donāt understand the turmoil here. Directly below that box has a similar filter that gets you the entity_id. When you click on an entity from that list it populates the field and you can copy/paste from there (or just copy from the listview like I do).
BTW: I do agree that it should always show entity_id. Iām just not sure why this is a pressing issue when you can get around it really easily.
my latest post was on the automation/scene/script/helper pages, not so much the dev tools.
we can only enter names, not entity_idās, nor search for them (except for the helpers, so it should be possible anywhere I hope)
But itās not only in developer tools this change is.
As I posted elsewhere before:
I have two entities that I named exactly the same since they are both used in templates.
selecting one give me this mess:
I canāt see what Iām doing in the UI. That means I have to go to yaml mode to read what the automation/script is doing.
1 Like
I understand that, but that issue is related to the dev tool page, not to mention that search box has always had this behavior.
As I can see people will take this out of context, let me just say:
What youāre highlighting should be considered a separate issue and not related to the dev tool ā set state search.
Each of these search box issues should be brought into a āMake the searches more consistentā issue or treated separately as each individual item.
All generic cameras fails to load after update.
Probably because you didnāt set them up in the UI
what did change was the Entity box, which now also shows the friendly_name, so it is listed twice now:
which is just pretty uselessā¦
and to be honest, thereās a pretty involved issue, and thereās no response at all from the frontend dev team, explaining or fixing
1 Like
Yes, the helper searches only search the individual helper/script/automation page that youāre on. They are filtered down to what you see in that list. The filters button on the side allows you to filter based on what entity the script/automation is using. So they have different behavior than the other search boxes.
click on the entity you want in the bottom list, it will populate the top area with the unaltered entity_id.
these boxes have different behavior between them, and imho they shouldnāt.
sure, for a brief time (click the entity box and its gone), and after that, it changes to the name, itās really odd. Itās what I did in the screenshot
1 Like
Iām closely following these discussions about naming. This has been an area of some confusion for me. For example, I have a lot of templates, and switching to the ānewā format removed the friendly_name option, which I had been using extensively.
Iām a big fan of naming conventions. I think itās good to start with one and stick with it. But it seems thereās not a lot of consistency across all the different ways names or identifiers are created, used and displayed in HA. They seem to be changed without a lot of forethought. Yes, itās a minor annoyance, but an unnecessary one. Maybe thereās a grand plan for the future that Iām just not seeing.
1 Like
Iām not disagreeing with you. Iām trying to let you guys understand that the way youāre going about this should be alittle different.
I recommend creating a single issue or discussion (in the discussion area on github) about unifying the search boxes and ending result.
Right now, you have a single issue pointing directly at 1 control and youāre using other controls as arguments about why everything is bad. This just leads to arguments, and no one has provided a solution that will solve the problem properly. I.e. Show the enity_id, keep it selectable, and provide the name of the entity for the people who arenāt power users using yaml.
My recommendation is to do the following for a discussion:
- Make all searches behave the same way. I.e. filter based on name or entity_id.
- When the result is selected from the searched list. It will show both the name and entity_id. Just like it does in the dropdown list when selecting.
- The visible name will continue to be the searchbox, where the entity_id will be static text that is not alterable. However you can highlight and select it.
2 Likes