The > is painful to get to on my android keyboard, but thanks for the extra explanation.
1 Like
Now I got it. Didn’t realise that I have to type > at first. Thank you and @petro for clarification.
I’ll open a pull request for you if I can work out the unittests for frontend, as long as it’s not opposed by the team that is
1 Like
Yeah, you have to train yourself, but it does make it pretty easy.
1 Like
Thank you very much for the link.
Unfortunately, I am not qualified enough to create a build… Will keep waiting for any changes in UI on the official rev.
For anyone using these shortcuts in the side menu
They require a small update:
panel_custom:
- name: panel-redirect
url_path: redirect-server-controls
sidebar_title: Server Controls
sidebar_icon: mdi:server
module_url: /local/panel-redirect.js
config:
target: /developer-tools/yaml
- name: panel-redirect
url_path: redirect-logs
sidebar_title: Logs
sidebar_icon: mdi:math-log
module_url: /local/panel-redirect.js
config:
target: /config/logs
- name: panel-redirect
url_path: redirect-devices
sidebar_title: Devices
sidebar_icon: mdi:devices
module_url: /local/panel-redirect.js
config:
target: /config/integrations
- name: panel-redirect
url_path: redirect-addons
sidebar_title: Addons
sidebar_icon: mdi:home-assistant
module_url: /local/panel-redirect.js
config:
target: /hassio/dashboard
9 Likes
Add `entity_id` to states panel in developer tools by TheHolyRoger · Pull Request #12588 · home-assistant/frontend · GitHub feel free to comment on the PR to show you want it!
1 Like
Since 2021.3!
Proof that I don’t read the release notes 
2 Likes
Found this change:
Very glad to to get this!
7 Likes
This has been rather disastrous for me. My ZwaveJS2MQTT integration stopped working, because the server isn’t new enough. Yet, it is on the latest version available with HassOS. So, went to restore a backup, but now that has changed, too. It says I need to go to some new place, but it shows no backups available, although there are 5 on the RPi itself, 5 on NextCloud and 2 on Google Drive.
Secondarily, with the new menu I cannot find how to check configuration, or update just Automations, say.
1 Like
Now in dev tools, as the release notes say.
1 Like
Thanks. The backups are now starting to populate the new page, so restoring now.
Just have to figure out how to get the new ZwaveJS2MQTT server, since the option to update doesn’t show up yet.
It’s not showing up because you or the system erroneously removed the community addons repo.
I don’t have zwave2js because I don’r have any zwave gear, but in my addons it says if I were to install it I would get 0.1.58
What are you on?
See this thread, it highlights what happened and how to fix it
2 Likes
I wonder if my case is a bug or a feature.
Trying to set a state or just check an entity.
If a part of the entity_id “er.life360_iphone_6” is inputted in the “Set state” panel, I get a list of entities where only ONE of them meets the inputted string:
If the same string is inputted in the grid below, I see only ONE entity - as it is expected:
And the same is with an Entities list - again the table contains entities which do not meet the inputted string:
I am 100% sure that in the previous HA rev it was working properly.
Possibly this is a BUG.
But it could be a someone’s logics, that is why I am asking…
3 Likes
Configuring SQL via YAML configuration has been deprecated and will be removed in a future Home Assistant release.
Why do we continue to remove YAML definitions for integrations? This makes versioning and sharing configuration harder, but it also reduces the ability to organise related config (e.g. into YAML packages), spreading related code across different parts of the UI.
It makes the management of a series of interdependent sensors incredibly awkward and frustrating to work on.
Pleeeeeaaaase stop deprecating YAML definitions for integrations. It’s debilitating for large/complex configs.
15 Likes
Feature.
The top one finds anything that contains all of the things you type in that order but with anything llowed in between each character. This is how the entity search behaves everywhere.
The second one is looking for exact matches of whatever segment you type.
but shouldn’t the top one be the most exact match? e.g. in those screenshots it should be the device tracker entity