Editing complex automations in UI gets slow and messy quickly

Configuration Frontend
1

Screenshot_2024-10-10-16-01-04-034-edit_io.homeassistant.companion.android
Screenshot_2024-10-10-16-01-04-034-edit_io.homeassistant.companion.android1080×1875 188 KB

I am now unable to edit all but the most simple automations in the UI. Opening embedded if-then and choice actions seems to be the thing that makes my UI freeze up, but it also has a problem on embedded not, and, or conditions.

I’m using a proxmox server on a HP elitedesk with an i7 processor and 16gb of ram running off a 500gb SSD drive. The attached screenshot is from the companion app. I will upload examples from a separate and fully juiced up pc running chrome which should demonstrate that the problem is not due to my hardware.

If anyone has encountered this problem and found a solution, I would really appreciate some guidance.

2

This has nothing to do with your server specs and is all about your display size. It could also be something to do with your custom theme.

Try using the default theme.

Or try using a desktop PC.

3

Or learn YAML config. Well-structured YAML code is much easier to read than a bunch of collapsing boxes.

2 Likes
4

And this is a good tip…
Why and how to avoid device_ids in automations and scripts.

5

I am experiencing the same hangs and expansion errors on my PC. I am using the default theme

7

I don’t use device triggers in any of my automations

8

Or use Node Red

9

I use VSCode, it goes just fine. syncs with GitHub. Checks my syntax. Life is good. And I have A LOT of yaml… (24, 532 lines of live, lots more that’s parked and not counted)

image
image510×628 34.6 KB

And that’s 1 of 3 HA instances…

10

I wonder how you count number of lines?
Cannot say that number of lines (and number of packages) is a useful info - just interesting.
(using packages myself)

11

it’s in there…
None of it’s useful, just use it for this kind of thing.

12

I reconsidered my pov. It IS useful and shows growing your project.
Will check your code, thanks a LOT.

Found it:

command: 'find . -name "*.yaml" -not -path "*/custom_components/*" -not -path "*/Purgatory/*" | xargs wc -l | grep "total" | grep "[0-9]*" -o'
1 Like
13

@Sir_Goodenough
Mind sharing where this screenshot comes from? I also use VS Code Studio and would love to see this info for my system. I too, have a ton of YAML code, with over 300 automation and scripts (600+ total). Thanks!!

14

This could be achieved by auto-entities with using a “template” option (or even with a simple “include” option with “entity” filter) to show an Entity card inside a Grid card for some defined set of sensors (here - sensors containing number of smth).

15

Auto entities won’t count lines of code. I understand that I could do it like that, but I am really interested in how he counted the lines of code. I assumed it was some sort of VS Code add in. Hopefully he can elaborate.

16

If you asked about lines of code - that was exactly my question and I posted an answer , scroll up a bit.

17

Look for yaml files , ignore dead paths that you don’t want to count, count the lines…
I didn’t come up with it, but it’s there.

1 Like
19

I have the same issue with the Automations UI editor being completely unusable. With 101 lines (including empty ones) of Yaml (turning on/off 5 lights to specific states based on time and sun elevation), the opening of the Automation Editor UI takes about 1 second, but every subsequent UI operation takes a lot longer. Opening the menu for Yaml editor takes 5-10 seconds, as well as opening any of the condition/operation expanders.

I ran profiler on opening the editor and expanding two conditions. Most of the time is spent doing QuickSort and positioning items.

Browser used is MS Edge Version 131.0.2903.51 (Official build) (64-bit)
HA

  • Core 2024.11.2
  • Supervisor 2024.11.2
  • Operating System 13.2
  • Käyttöliittymä 20241106.2

Browser resolution does affect a bit. In a smaller window, about 1080p equivalent the initial render was faster, but did not improve overall as a UX.

Almost full-screen 4K:

image
image858×568 41.7 KB

The tab takes about 1 CPU core and memory consumption keeps increasing steadily with no network traffic. It becomes completely unresponsive in about 1 minute.

As a result you basically cannot open any menu in editor or even exit reliably, as the left-arrow and save-button do not seem to react for several, even tens of seconds.

1 Like