Developer Tools/States Most used screen Vote?

1

By far the most used screen I use is the Developer Tools/States to test ententes and look at the state of something of interest.
Only if I am developing new automation or modifying HA do I use the restart screen.

Why did yaml restart page get the center spot? This is going to add time to your navigation during normal usage. :frowning: Boo LOL Boo

2

Because people asked for it. The states page is the slowest Developer Tools page to load if you have many entities.

3 Likes
3

Iā€™ve asked for that exactly for the reason @tom_l described.
I loved the new tab order as I spent a fraction of the time to get to the Template, Services or Events tabs which I use way way more than the States tab. :slightly_smiling_face:

4

And I for one am very happy with the change. The states tab is not my most used, as you can search for any entity to see its state way faster. The Yaml tab is there instantly and it is the one I use most to reload stuff or check the config. And going through yaml to states is almost as fast as going directly, but going though states to get to yaml is horrible.

1 Like
5

Why is the states so horribly slow?

How do you check states faster then going to the states page?

1 Like
6

{{ states | count}}

I have ~ 2000 to load. Takes a few seconds on my local network. Now try that from a remote connection with limited bandwidth.

1 Like
7

Edwin_D mentioned how the Yaml tab is there instantlyā€¦ I agreeā€¦ If your using the yaml page often it would suck to wait for the states page to load every time before you can press the yaml page that is almost instant.

States Tab is horribly slow compared to the the yaml Tab.

What is a quicker way to check any state or list of states with a quick search like we do with the states tab? What does that mean ā€œyou can search for any entity to see its state way fasterā€?? with what?

tom_I Sorry ā€œStates tabā€ the screen under Developer Tools/ state

/developer-tools/state

8

Yes that is what I am talking about. You asked why it was slow and I told you. It is the quantity of data. I have 2000 states to load there. And then thereā€™s the multitude of additional attribute values. All this takes time to retrieve from the database. All this takes time to load in your web browser. That is why it is slow. None of these states can be cached as they could have changed since the last time the page was loaded.

9

pressing ā€˜eā€™ on pretty much any page brings up a search bar. useful for checking a single entity. If you need to see multiple at once, use the dev page.

10

99% of the time, I want the states tab, thatā€™s the only reason I click on developer tools. I know it will sound overcomplicated, but Iā€™ll suggest it anyway: canā€™t it be made optional, which tab goes first? Then the yaml tab lovers can be happy as well.

11

How can I pull that on the android app?

12

The search option in the three dot menu in the top right of the dashboard.

1 Like
13

Shouldnā€™t the last page opened when opening the dev-tools again?

14

Yes that is the behaviour now.

15

The last visit state does not work in Firefox.

16

It does for me using Ff 93.0.

Is your history set to clear on closing the browser perhaps?

17

History is for sure set to clear when all instances are closed, but it doesnā€™t even work within the time the browsers are open. That is a really positive note that it works on at least one of you guys instances, and it is a me problem. lol

18

I just did some testing. It only remembers while the tab is open (i.e. navigating away to other dashboards or parts of the frontend). Closing and re-opening the tab sets it back to the YAML page.

Same behaviour in Chrome.

1 Like
19

Thank you for verifying how it works.

20

I also really dislike the YAML tab on first tab personally.

My workaround is to add a shortcut to go directly to the States tab. I found this panel_custom tip on this forum and itā€™s really useful:

panel_custom:
  - name: server_logs
    sidebar_title: Logs
    sidebar_icon: mdi:cog-transfer
    js_url: /api/hassio/app/entrypoint.js
    url_path: "config/logs"
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: automation
    sidebar_title: Automations
    sidebar_icon: mdi:cog-transfer
    js_url: /api/hassio/app/entrypoint.js
    url_path: "config/automation/dashboard"
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator
  - name: states
    sidebar_title: States
    sidebar_icon: mdi:cog-transfer
    js_url: /api/hassio/app/entrypoint.js
    url_path: "developer-tools/state"
    embed_iframe: true
    require_admin: true
    config:
      ingress: core_configurator

image

Feel free to use different / better icons for the menu.

Documentation:

1 Like